- Wed Jul 06, 2016 8:46 pm
#786047
Am I right in saying the system is really built around the inbox, i.e. it doesn't matter whether the next task is also assigned to the same user, that user will have to go back to the inbox each time, find the next task in that process and initiate it manually.
So for a process with three tasks that the user needs to perform, the steps would be:
1) New Case: ABC Process
2) Perform Task 1 in process
3) Go to inbox find task and start it
4) Perform Task 2 in process
5) Go to inbox find task and start it
6) Perform task 3 in process
7) Process complete
Is this right? Is there no way to check whether the next task is also assigned to the user and if so continue with the process?
This seems to really make it easier to start lots of things and not necessarily finish them before starting other things.
As a workaround you could combine all the tasks into one task (as lots of steps), but this really goes away from the BPMN modelling concept.
Am I missing something?
So for a process with three tasks that the user needs to perform, the steps would be:
1) New Case: ABC Process
2) Perform Task 1 in process
3) Go to inbox find task and start it
4) Perform Task 2 in process
5) Go to inbox find task and start it
6) Perform task 3 in process
7) Process complete
Is this right? Is there no way to check whether the next task is also assigned to the user and if so continue with the process?
This seems to really make it easier to start lots of things and not necessarily finish them before starting other things.
As a workaround you could combine all the tasks into one task (as lots of steps), but this really goes away from the BPMN modelling concept.
Am I missing something?