Cant add 'completed' stage at the end of a flow in flow designer

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-04-2022 04:18 AM
I'm adding stages to my (very simple) flow in flow designer.
There are only 2 spots where it allows me to add a stage though. I want to at least have the stage 'completed' at the end, but it wont let me add it, nor at the parallel task creation I do right before. Are there any tricks to add stages on other places?
- Labels:
-
Request Management
-
Service Catalog
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-23-2025 09:24 AM - edited ‎06-23-2025 09:25 AM
See my reply to the original poster - I wasn't able to add the END flow logic either until I added an unneeded IF statement that would always be true at the beginning of my flow - I was then able to add the END flow logic so that I could add the completed stage before it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-23-2025 09:16 AM
I've just run into this issue myself and would love to hear if anyone found a better way of adding the completed stage.
My original flow was very simple, only three steps:
Trigger = Service Catalog
1- Get Catalog Variables
** Fulfillment Stage **
2 - Update Requested Item Record
3 - Create Catalog Task
My solution was to add an IF Flow Logic as my first step that would always be true (If Requested Item Number is not empty). This allowed me to add an END Flow Logic after the Create Catalog Task and the Completed stage in between.
My new flow logic looks like this (see screen capture):
Trigger: Service Catalog
1 - {Flow Logic IF} RITM Number is not empty
2 - {then} Get Catalog Variables
** Fulfillment Stage **
3 - Update Requested Item Record
4 - Create Catalog Task
** Completed Stage **
5 - {Flow Logic END}
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a week ago
So far, the most straightforward way I've found to deal with this issue is to create a "no-op" Action—literally just an empty Action that does nothing. Make that Action the last step in your Flow, and then you can set a stage between it and your last "real" step.
I hope it's somewhere on ServiceNow's to-do list to address the issue, though. Allow using End Flow in the "main" sequence of steps, or allow setting a stage after the last step, or something.