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?
