- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-06-2020 04:46 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-06-2020 08:43 AM
Correct,
in order for this to be done with flow designer you'd need to divide the logic into a series of subflows which allow for input / outputs.
However I personally believe the complexity of change management flow(s) and even some request flows mean Flow designer shouldn't be used. It's just not ready for that level of intensity yet.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-06-2020 01:36 PM
Hi,
There isn't OOB as there isn't a direct tie between the records like with workflow as flows' can be triggered in multiple ways. There is the below on the ServiceNow share which comes close.
https://developer.servicenow.com/connect.do#!/share/contents/7600783_flowdesigner_flows_ui_action?v=1.5&t=PRODUCT_DETAILS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-23-2021 06:15 AM
this is discouraging, as with Quebec they pushed the availability and seemingly the move forward with Flows instead of workflows.
While prepping for the Quebec upgrade i looked and looked but found no official docs about migrating from Workflows to Flows.
maybe your observation is also observed by ServiceNow? 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-23-2021 07:52 AM
With the paris release this somewhat changed as they released Change Management flows to be used that simplified the process greatly to not require any custom actions or steps. I've not personally used these yet, but it's definitely on the cards to investigate as well as the change models now available.
I think the issue that is going to hit a lot of customers will be similar to the problem migration where customers have (rightfully) made configuration changes to meet desired outcomes to which ServiceNow are now offering an OOB solution. Just the adoption process is going to be hard.
In terms of the discouraging aspect, I do have to agree that flow designer is lacking in some key areas in an effort to drive performance...but it's sort of a net gain as the effort is causing a deficit elsewhere? As a recent example, I started using flow for a solution and after needing 3+ support cases for defects, the straw that broke the camels back was a basic function of the now legacy workflow tool not being available in flow and pointed to raise an idea on the idea portal....
