What I’m trying to do is, if there are approvers then it should go to the next approver, if not End the flow and send the document to a Folder. Can I’ve a generic template or I should pre-defined each step of the workflow?
How are you defining list of approvers? Is this an attribute on document or group?
Requirement is that there will only be 15 user to the Repository and everyone will have Read/Write access.
There could be different approval process
For example in one process might be USER A & USER C & USER D > END or USER C, USER D and USER A > END
Second one USER H & USER X & USER X > END
and so son
I cannot really put anyone in one group, because they change their process very often and they do not want to pre-define groups and workflow process yet.
Can it be done?
I have pre-defined groups and workflow templates and I'm familiar with that processes.
If the list of approvers is available in any attribute, you can develop a custom task to set the performers of the next activity in the workflow, so you could have:
establish approvers -> auto task to set performers -> approval task -> finish
We are trying to avoid customization. What are the other options?
Without customization the only way I think it could work is by implementing some kind of loop in the workflow where a review task is sent individually to each one of the reviewers and then using a wait task triggered when all the review activities are finished
I still think the custom activity is the easiest way...
Hello,
Emphasizing on Alvaro' suggestion, building one custom activity, where you will form the list of approvers dynamically would be the right choice. This approach would meet both of your requirements,
1. generic process template
2. the order in which approvers will get their respective workitems can also be decided programatically.
Also,In case you want all the approvers to work in parallel, that choice is still there.
Let me know in case you have found out any other approach.
Many thanks,
Arindam
If it is just a single manual activity, you can go for 'Quickflow'. Quickflow has feature to select performers and to decide on how to send the tasks - parallel/sequential, to all the performers.
