How do we update the Requested For in the Order Confirmation Pop Up?

[scottneeb]

As part of the Kingston upgrade it now displays an Order Confirmation dialog after you click Order Now.  The problem we're having is it doesn't pull the Requested For from the catalog item we're ordering, so if the user changes the Requested For it doesn't update the Requested For in the Order Confirmation window.  As you can see in this screenshot they are different.

[Colin Webster]

Unfortunately my personal dev instance is currently on Jakarta due to a project I am working on so I am unable to dig into this one too much, but wanted to at least offer some thoughts. I believe this screen is configured from the Maintain Cart Layouts module in the Catalog Definitions group under the Service Catalog application. As far as the Request for being different, I think that is because the 'Request for' comes from the Request, where as the 'Requested for' comes from the Requested Item.

3 options I can think of then:- 

• Configure the catalog item to use the 'Request for' value from the Request 
• Set a client script to change the 'Request for' on the Request whenever the 'Requested for' is changed on the item
• Modify the Cart Layout to show/change the 'Requested for' instead of the 'Request for'

[ericjackson]

Colin is correct. The 'Request for' in the popup is at the Request level and the 'Requested for' is on you Request Item.

One thing you could do is disable the Order confirmation pop-up entirely by creating a new system property:

glide.sc.sp.twostep = false

That may prevent any confusion and then you can create a catalog script or business rule to set the Request level 'Request for' to what the user chooses as the 'Requested for'.

[Ashley]

I'm searching for the same answers, would expect this to be OOB functionality 

[peter_cawdron_p]

The documentation highlights how the "Order Now" modal dialog has a "requested for" field that can be changed using options, but if you do what they suggest it will change the default (which dynamically looks at the current user) to a single static value that is ALWAYS applied. I cannot understand why they did this as it really doesn't make sense. Ideally, you want to map from a catalog item variable, which is what I've done below.

If you clone the widget-cat-item-v2 and add the following code at the very start of your widget AND you have a field called requested_for in your catalog item, it's value will be mapped to the "Order Now" requested for field 

////////////////////////////////////////////////////////////////////////
//
// added to pick up the requested for field & pass to order now
if(input.itemDetails.fields.hasOwnProperty('requested_for')){
  var getRequestor = new GlideRecord('sys_user');
  if(getRequestor.get(input.itemDetails.fields.requested_for)){
    options.requested_for_id = getRequestor.sys_id.toString();
    options.requested_for_display = getRequestor.name.toString();}
}
//
/////////////////////////////////////////////////////////////////////////