Hi everyone... regarding approvals... I would like...
# general
e
Hi everyone... regarding approvals... I would like to keep this Approval Workflow in a single Workflow, but I have a lot of approvers that depend on some conditions... everything works fine, but the transitions are a nightmare to visualize in this spider Do you have another solution to keep the transitions to the Rejected state more... clean?
m
Do you not like the multiple transitions into rejected state? This diagram looks pretty clean considering some workflows I’ve seen
I think the only way to “clean up” the rejected state would be to eliminate the multiple approved at each level. Ive done something close to this using a custom child record that stores Approver, join to transaction and any other information needed The approver approves the custom record which then approves the transaction. This way you can setup multiple approvers and whoever “gets there first” approves it and the others no longer need to
e
Do you not like the multiple transitions into rejected state?
Yep, that my issue. Because (not pictured) are the multiple transitions to "Return to User" and "Approved"
m
You could use my child record idea. Make one pending approval state and create child records based on all your conditions. Then everytime you return to the one state it would make the necessary child records