Restructuring Flow Design
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-28-2024 06:04 AM
Hi All,
I have a flow design for a particular catalog item which has 140 steps.
I have to restructure the flow like the way so that the number of steps should be decreased but the logic remains the same.
Can anyone please help me out with this, it is urgent.
Thanks in advance.
Regards,
Abhisek Chattaraj.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-28-2024 07:11 AM
Hi @abhisek
It depends on your use case. Are 140 steps for a task or like having conditions or something? If you provide more details As- Is flow, easy for us to guide better.
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-02-2024 06:42 AM
Thanks for your reply and time.
This flow is creating tasks and sending emails parallelly based on different conditions by using the 'do the following in parallel' activity after using the 'look up requested item record' activity. Under this 'do the following in parallel' activity we have total 53 steps. Then we have 'wait for condition step' then based on a 'if condition' step it is again creating tasks and sending emails parallelly based on different conditions by using the 'do the following in parallel' activity. Under this 2nd 'do the following in parallel' activity we have total 64 steps. Then at the end of the flow we have task incomplete logic implemented (if all the tasks are closed complete then only RITM would be closed completed, in case any 1 task is closed incomplete then RITM would be closed incomplete.
Could you please let me know how I can restructure this flow so that no of steps should be decreased and logic remains same.
Thanks&Regards,
Abhisek Chattaraj.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-02-2024 11:32 AM
HI @abhisek
I am not a dev but as per the process
- See or get the common steps in these 2 major steps, can we club or can we remove or it is like redundant.
- You are already using if and parrell which is I can say good, but the overall you need run Lean process in this catalog item also, see can we automate few steps.
Also @Sandeep Rajput mentioned, getting common in all is key here.
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-02-2024 07:32 AM
@abhisek I came across the similar situation where in I had more than 100 steps in one of my flows which was triggering different API calls based on several if blocks.
The best way to restructure such flows is as follows.
1. Identify the common steps: As a first step, you need to identify what all steps are common across different blocks within your flow. Once identified, you can group these common steps and create a sub flow around these steps. Define appropriate inputs and outputs for these sub-flows and instead of repeating these common steps, you can replace them with the sub-flow.
2. Custom Action: Identify if a lot of common steps can be reduced by using a custom action which uses a script to process the common inputs and outputs.
By following these two suggestions you can greatly reduce the size of your flow.
Hope this helps.