Service Portal - Requested For on Checkout page

[sunil_m_l10]

how to change the configuration on a catalog item/order guide's checkout page, where the requested for field should reflect the user we have selected on the order guide/catalog item form instead of the current logged in user

[Ankur Bawiskar]

@sunil_m_l10 

not very sure then how it's done

[sunil_m_l10]

@Ankur Bawiskar  Thank you no issues,

[Josh Pirozzi]

Hi @sunil_m_l10,

We have come to a point of ignoring the checkout page because we couldn't get consistent updates by our customers. We went with setting the Opened By and/or Requested For accordingly in the associated Flow based on the Variable(s) updated before Request Submission. 

This ensures accurate data in the Record Fields and gives us a consistent way to trigger Approvals, route to specific team(s) based on location, etc...

[sunil_m_l10]

@Josh Pirozzi  
yeah but we have this business requirement 
is there any way to make it empty instead of logged in user default value

[Josh Pirozzi]

@sunil_m_l10,

It might be possible to update the scripting on the Checkout Portal Widget, but then you run the risk of tech debt for patching/upgrades. If you have a single variable set for your order guides/catalog items for your 'Requested For' selection, then maybe you can map the variable to that field, but everything we had researched a couple of years ago led us to just adding a step into the Flows associated to Catalog Items/Record Producers to look at the 'Requested For' Variable on the submitted form and then update the corresponding Field on the RITM. 

It gave us a semi-simple solution after going the routes of research and attempting to educate end-users on updating the Checkout screen, and not having a consistent solution.