To Setup Business Rules for Collaborative Handling by multiple Persons on One Task

Normally, a task will be processed by 'one person who is allocated'. But there are necessity of collaborative working environment to process tasks such as 'Team reviewing' which several people might advise, and 'preparation for multiple application documents'(ad-hoc tasks) which the order of processing is not fixed. To process a task by multiple persons, we define "Team Task" in Questetra.

To Setup 'Team Task'

As you see looking at the items in pallet of Process Modeler screen, there is only one type of 'Task'. What is the 'Team Task'?
'Team Task' means a task placed in a 'Team Swimlane'.
'Team Swimlane' icon is in the Advanced tab of the pallet.

TeamSwimlane-en.png
 

 

Configuration of allocation rule for Team Swimlane is the same as normal Swimlane.
A Task on a Team Swimlane will not be 'offered' but will be 'allocated' to the users who specified in the allocation rule.

Characteristics of Team Tasks

  • Different from normal tasks, it won't be offered. It will be allocated to the users who fit the allocation rule. That is, will be displayed in [My Tasks] of multiple users.
     
  • Any allocated user can enter data until someone 'finished' the task.
     
  • When someone clicked 'Finish' button, the process goes to the next task.
    When you want to enter data, but don't to finish the process (Don't let it go to next), click [Save and Quit].
MyTask-en.png
 

 

How to Setup for Convenient Usage

  1. Using in Conjunction with Discussion Type Data Item.
    They might lose who have entered the comment, because multiple persons are co-working on a task. For such a case, define 'Discussion type data item' which automatically records who entered.  
  2. Repeat in Self-loop
    When other person might enter, the user would use [Save and Quit] instead of [Finish]. But in this case, the entry might not be noticed.
    To avoid such a case, make a flow that goes back to the same task (Self-loop), and use [finish] on each time entering. Do not forget to set a Split Condition to let it go to next task. It is also possible to share by email by setting a 'Message throwing Intermediate Event' in the middle of the Self-loop.
SelfLoop-en.png