Rethinking an Approval Workflow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi community,
I'm looking for your input on a workflow I've designed and how to improve it. I'm trying to create a subflow to handle an approval process, but I've run into a design issue.
My Current Workflow Logic
The core logic of my current process is simple, but it's causing me some scalability problems. It works like this:
The user fills out a request form.
The workflow then checks a condition:
If the user has checked a box for "Attaching Approval Email" (meaning a pre-approved reference is uploaded), the flow continues to the next step.
Else, the workflow triggers a request for approval. Once approved, it proceeds to the exact same flow as the first option.
The main problem with this is that I have to build the same "next steps" twice, which makes maintenance difficult. My goal is to use a single subflow that handles the "next steps" so I only have to build it once.
My Goal and Question to the Community
I want to create a more efficient and reusable process, ideally by using a single subflow for the post-approval logic.
How would you handle a requirement like this? I'm open to different approaches that could make this process better for my team.
What do you think is a better way to structure this to avoid duplicating code? Are there any design patterns or best practices I should consider?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
1. Create a subflow and move the 4 actions repeated in both the conditions viz., Package Software, Policy Request, Add/Remove Existing Policy and Add/Remove users
2. Create a IF condition in the flow to check whether Approval email is attached. If it evaluates to true, call the subflow
3. Create Else condition in the flow and request ask for approval and once approved, call the subflow
Below is a sample Flow -> Subflow logic to make you visually imagine the steps, update based on your requirements
I hope you appreciate the efforts to provide you with detailed information. If my response helped to guide you or answer your query, please mark it helpful & accept the solution.
Thanks,
Bhuvan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Did you get a chance to review this ?
I hope you appreciate the efforts to provide you with detailed information. If my response helped to guide you or answer your query, please mark it helpful & accept the solution.
Thanks,
Bhuvan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hey Bhuvan, thanks for taking the time to look into this. What I’d like to implement here is a subflow that I can reuse across different flows, since we already have quite a number of catalog items and I’m just thinking it won’t be very manageable in the future. Sorry if I wasn’t clear earlier about what I’m aiming for
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Please try the following approach:
Create a subflow that includes all the actions you want to perform. Then, call this subflow as shown below: