- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-22-2020 02:57 AM
FLOW Designer, “Do the following in parallel” flow-logic cannot be inside another “Do the following in parallel”
Is this a limitation in the FLOW designer?
Solved! Go to Solution.
- Labels:
-
Integrations
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-22-2020 03:01 AM
Hi,
If it is not shown then that might be OOB behavior.
Possibly to avoid looping it has been kept away
Regards
Ankur
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-22-2020 11:47 PM
Is this the better summarised answer to this? Please comment.
Branch from the Flow-Logic “do-the-following-in-parallel” does not allows to create another “do-the-following-in-parallel” Flow-Logic by its design, does not matter the root of the flow is a main flow or even the sub-flow.
Whenever we need a parallel actions to execute from branch of another parallel branch(Flow-Logic “do-the-following-in-parallel”) , we must need to create another sub-flow.
In other word, to transition from one parallel branch to another parallel executions, we must need to create them as sub-flows. Will it be Kind of sub-flows hell :). This will kill the the visibility of the flow logic at the design time is I feel.
So far I have experience this restriction only on the Flow-Logic “do-the-following-in-parallel” . However the Flow-Logic like “IF” allows to have any numbers of next “IF” Flow-Logic branches on and on from the same flow. So we have the If logic visibility at the design level too.
This is the reason I always feel the FLOW designer is like (Story stepping flow) more of a linear flow designing … whereas the WORKFLOWS designer is more of flow charting in nature …
End of the day the workflows is the one providing the orchestration capabilities for advance/complex use cases .
Or… maybe my lack of knowledge yet on the SNOW platform … Right now I’m in kind of a knowledge hunting mode and I’m sure I have to start it from the beginning in some structured way after few weeks.
I appreciate the support from this community and they are really strong and prompt. Good to have a strong community support :). Tax

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-23-2020 12:30 AM
Personally, I find it easier to write script for something complex. It's possible to create custom action with script steps which I can code.
Flow Designer is more of event based rather than sequential based. Managing visibility is on the event rather than on the connection between steps. Steps in each event should be made short. It's necessary to change the design and mindset when using Flow Designer.
It's still necessary to use Workflow to maintain existing apps but I've been able to develop all new flows using Flow Designer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-23-2020 01:02 AM
Sorry, I'm still new to using the community forum too. What happen was that i access it from mobile and mark all answers .. never new that i can select only one.
Anyway all the answers are correct and helpful to the community.
Appreciate all prompt support from all of you