Hi Everyone,
I would like to ask for guidance and best practice recommendations regarding a legacy Workflow Editor implementation that I am currently reworking.
Current Behavior:
* The workflow currently generates approvals sequentially.
* Each approval has a corresponding SCTASK.
* When an approval gets approved, its related SCTASK changes from "Pending" to "Open".
* The SCTASK then triggers a separate automation flow for provisioning/access activities.
New Requirement:
* All predefined approvals and SCTASK definitions should be generated upfront (simultaneously).
* Approvals should run in parallel instead of sequentially.
* Each SCTASK should remain in "Pending" state initially.
* Once a specific approval is approved, only its corresponding SCTASK should transition from "Pending" to "Open".
* The existing automation flow triggered by SCTASK state change should remain unchanged.
Additional Notes:
* This is implemented in Legacy Workflow Editor (not Flow Designer).
* I am exploring approaches using either workflow.scratchpad or approval/task correlation logic without introducing too many additional custom fields.
* One issue encountered is that when one approval is approved, the remaining approvals sometimes become "No longer required."
I would like to ask:
1. What is the recommended design pattern for handling parallel approvals with individually linked SCTASKs in Legacy Workflow?
2. How do you prevent sibling approvals from being automatically marked as "No longer required"?
3. What is the best way to correlate each approval to its corresponding SCTASK?
4. Has anyone implemented a similar approach successfully in Legacy Workflow Editor?
Any guidance, workflow design suggestions, or implementation examples would be greatly appreciated.
Thank you!
