We're reclaiming inactive PDIs to keep them available for active builders. Learn what's changing, who's affected, and how to protect your work. Read More

Issue with "Request Approved" State When Creating Multiple RITMs

shine17802
Tera Contributor

Hi everyone,

I have a Catalog Item that allows multiple users to be selected in a List Collector. When the item is submitted, a separate RITM is created for each user under the same REQ, with each selected user set as the Requested For user.

During RITM creation, I need to set the state to Request Approved. However, Request Approved is not available as a choice in the sc_req_item state field.

The issue I'm facing is:

  • The first RITM displays the state as Request Approved.
  • The remaining RITMs display the backend/internal value instead of the display label.

Has anyone come across this behavior? Is there a recommended approach to ensure all RITMs display the correct state label instead of the backend value?

Any suggestions or guidance would be greatly appreciated. Thanks!

 

5 REPLIES 5

Ehab Pilloor
Mega Sage

Hi @shine17802,

 

You can use Stage in RITM for showing Request Approved on RITM, but you need to set Approval as Approved too for it to work. Change Approval field to Approved instead of Requested.

 

Please Accept this response as Solution if it assisted you with your question & Mark this response as Helpful.

 

Kind Regards,

Ehab Pilloor

Ankur Bawiskar
Tera Patron

@shine17802 

you should create separate RITM using "Submit Catalog Item Request" flow action

Why are you using Create Record flow action?

💡 If my response helped, please mark it as correct and close the thread 🔒— this helps future readers find the solution faster! 🙏

Regards,
Ankur
Certified Technical Architect  ||  10x ServiceNow MVP  ||  ServiceNow Community Leader

shine17802
Tera Contributor

If we use "Submit Catalog Item Request", it will create a new Request (REQ), right? But I want use only one request.

 

@shine17802 

yes that's correct

But I won't recommend using Create Record

let new REQ be created, you can always update the new RITMs REQ with the older one and the new REQ can be marked as cancelled

This way you are sticking to OOTB catalog process and if in future each RITM creation wants to have separate flow or workflow linked to it, then no issue.

💡 If my response helped, please mark it as correct and close the thread 🔒— this helps future readers find the solution faster! 🙏

Regards,
Ankur
Certified Technical Architect  ||  10x ServiceNow MVP  ||  ServiceNow Community Leader