Stage Not showing in flow designer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2025 03:17 AM
Hi Team,
I am facing a problem where I've created choices for the Request item stage field. It shows the choices in the back end, but whenever I set the stage value through Flow Designer, the choice doesn't appear for selection.
After i tried created Flow stage in flow designer its showed but after set the Stage value its showing the requets_decliend
I created choice for the stage field in RITM table its not showing in the flow if any one knows pls help me on this i tried different to many methods but i couldn't find the solution
Advance thanks team🙂

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2025 05:41 AM
Stage is a special field. You don't add choices to the field itself like you do with other fields. It is strictly handled through the Flow/workflow. So whatever stages you need for that particular Flow, you need to set those up within your Flow.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2025 06:02 AM
Thanks for Your reply @JenniferRah By flow i did but its showing back end name only
Front end name -Request declined
Back end name-request_decliend
after set the value in stage filed is filled by back end name
It should be filled by front end right? or else is this OOB behavior

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2025 06:07 AM
Are you setting the stage within the Flow? If not, that explains why it is doing this. We used to set stage with a UI action, and it worked fine. Starting in Washington, we noticed that it started showing the back-end value instead of the display value. We opened a ticket with SN support and they essentially said we shouldn't be setting the stage anywhere except in the Flow. 😞
The only "fix" we could come up with was to have the back end value be the same as the display value. I will say, it seems to have corrected itself in Xanadu, but I haven't looked closely to see if that's anecdotal or a fix across the board.