cancel
Showing results for 
Search instead for 
Did you mean: 

Open two tasks and forbid one of the tasks to complete until the other task has been completed

xman-berlin
Champ in-the-making
Champ in-the-making
Hi guys,

I've got a strange requirement in my company. They want to implement the following scenario and I don't know how to achieve this. Here's the scenario:
  • User A claims a task from his/her tasklist.
  •  
  • User A decides to start a subprocess that must be completed before he's able to complete his/her task.
  •  
  • User A's tasklist still contains his/her claimed task.
  •  
  • User B claims and completes the subprocess.
  •  
  • User A is now able to complete his/her task.
Question:
  1. Is this possible at all?
  2.  
  3. Is it possible to model such a scenario (optionally starting a subprocess)?
  4.  
  5. It is possible to create subtasks in activiti-explorer. What is it? Subprocesses? Call activities?
Thanks,
Torsten
2 REPLIES 2

martin_grofcik
Confirmed Champ
Confirmed Champ
Hi Torsten,

Is this possible at all?
Not now. I thing this requirement goes against task definition (as activiti defined it). From business point of view I would model the requirement differently.
  1. There is a "Case" under which process is running. (Process just changes state of the case).
  2. Task is task. Use the task to assign work to the user. (Waiting for work is not a task.  To get user now that something is going on - use the case)
This scenario is supported in case engines. (we have such a product in edorasware, which integrates process and case management together.)

Is it possible to model such a scenario (optionally starting a subprocess)?
Yes, but I would omit the pending task.

It is possible to create subtasks in activiti-explorer. What is it? Subprocesses? Call activities?
yes, it is a task.


Regards
Martin

Hi Martin,

thanks for clarification, especially for "waiting for a task is not a task".

Best regards,
Torsten