Allocation Rule that Not Always The Same Personnel to Be Allocated

In the default setting, a task once has been handled by Mr. KATO in 'Employee lane', the task would be his duty when it came back to 'Employee lane' again. It would not be offered to all employees. If you want a task to be offered according to the allocation rule without the restriction of "the same user handling the task in the lane", check the "All subsequent Tasks are allocated or offered by the same rule as the first task" option.

The Basic Allocation Rules

In Questetra BPM Suite, a personnel is decided as the handler of each task according to the "Allocation Rule" that have been defined in property of each swimlane.

process-model-loop

As standard setting, every tasks in the swimlane will be allocated to a user who have been once decided by the 'Allocation Rule'. In concrete case as the Workflow chart above, when Mr. KATO in the first swimlane processed the first Task, both of

  • the Task of [1. Application] that rejected and sent back from [2. Approval],
  • the task of [4. Confirmation] came through [2. Approval] and [3. Payment],

will be allocated to him. That is, since after Mr. KATO processed the first task in the firsts wimlane, every task that arrives at the first swimlane will be processed by Mr. KATO. It will never be offered to other employees.

The policy such as 'Personnel who is familiar with the matter (who once involved in that issue) will be responsible the subsequent Tasks' is called "Retain Familiar"

 

To Setup "Who Can Handle Now" Would Handle, Instead of "Who Is Familiar to It"

In other hand, there are some cases it might be rational to decide who will handle each time the task arrives at the swimlane. For example, when Mr. SUZUKI of Accounting section processed the task of [3. Payment] in the Accounting swimlane, and he send it back to [2. Approval] task according to the 'Regulations of Accounting Section', there is no reason for Mr. SUZUKI that he must handle

  • the Task [3. Payment] after sent back and re-approved at the task [2. Approval], or,
  • the Task [3. Payment] after sent back to the task [2. Approval], and went around the Task of [1. Application] and the task [2. Approval].

It doesn't matter whether Mr. SUZUKI who sent it back at first or other personnel handles because to pay or not is handled with 'the Regulations of Accounting Section' .

To make setting like this, select "All subsequent Tasks are allocated or offered by the same rule as the first task". In a swimlane which have been set up this selection, tasks will be offered (or allocated automatically in cases) each time along the allocation rule without the restriction of 'a Task will be handled by the same personnel'.

setting-allocation-rules