- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-11-2022 11:51 AM
Instance Version: Rome Patch 5
Instead of stage display label, flow designer sets stage value to requested item. This issue is identified when update record action is used to set stage field option on requested item.
Flow:
Solved! Go to Solution.
- Labels:
-
flow designer
-
Service Catalog
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2022 01:43 PM
ServiceNow suggested to use FLOW Stages only to set stage values to Requested Item(RITM) to see expected results, instead of update record action.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-11-2022 11:57 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-11-2022 02:21 PM
No specific reason, we have lot of users who works on flow designer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2022 01:43 PM
ServiceNow suggested to use FLOW Stages only to set stage values to Requested Item(RITM) to see expected results, instead of update record action.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-23-2023 06:11 AM
Using the flow stages to set the stage values for RITM works perfectly. The stage appears properly in the RITM form, RITM list view and also, when the requesters open their RITM from 'My Requests' in the portal.
However, it is bit of an inconvenience not being able to update the stage via 'Update record' action in sub flows. While we update the stage via 'Update record' action in sub flow, then the stage is appearing only in RITM form but not in RITM list view or under 'My Requests' in portal.
Has anyone found a workaround or a solution for this?