I have a large, complex form which needs to go back and forth between different approvers until everyone signs off. I figure I could either:
- build the workflow with a task for each approver (in a state machine), each task having:
- a link to the form which folks review and revise
- options in the task to approve or send the form back to a previous approver
or
- build the workflow with emails for each approver (in a state machine), with:
- the email having a link to the form
- the form having buttons for approve or send back to a previous approver
- after the send email action, the workflow waits for a field update, which is updated by any button action on the form
I prefer the 2nd method because it's more user friendly than receiving a task, following a link, updating the form, returning to the task and submitting it, but I would use the 1st method if there was any possibility that waiting on a field change had any associated risk - i.e. if the workflow sat at a Wait for Field Change action for weeks, is there a possiblity that this could fail and/ or be less reliable than a workflow which sits at Task action for weeks?
