How to intelligently select a user in a group to assign task to, based on certain considerations

 Browse Space
Version 5 by Kendy Yus
on Sep 03, 2007 17:03.
<< Changes from 4 to 5
compared with
Current by David Glen
on Oct 18, 2007 18:27.
Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (23)

View page history
...
h3. Scenario
It is likely when come to assign a task to a user, there is a group of user in a particular department that the task can be assigned to anyone of them.&nbsp; One way of achieving this is to assign the task to the group and everyone in the group can go and claim the task, or alternatively the task is assigned to a randomly picked user from the group.
When it&nbsp;comes to assigning a task to a user, there&nbsp;can be&nbsp;a group of users in a particular department where&nbsp;the task could be assigned to any one of them.&nbsp; One way of achieving this is to assign the task to the group and everyone in the group can go and claim the task, or alternatively the task is assigned to a randomly picked user from the group.
 
However, if we would like to have more control to whom the task should be assigned to, based on the current workloads of each individual in the group, the current User "assignTask" operation provides no assistance with this regard.&nbsp; For example, we would like to make sure each employee in a particular department (group) to have a fair amount of works(tasks) to do, not over-stretching one particular employee while the other is waiting for tasks to do. On the other possible scenario, for critical task, we would like to give it to the user who is the most experienced and has handled the same task numerous time in the past, to ensure the task is carried out successfully.
However, if we would like to have more control to whom the task should be assigned to, based on the current workloads of each individual in the group, the current User "assignTask" operation provides no assistance&nbsp;in this regard.&nbsp; For example, we would like to ensure each employee in a particular department (group) has a fair amount of work (tasks) to do, by not over-stretching one particular employee while&nbsp;others&nbsp;are waiting for tasks to do. Another possible scenario, for a&nbsp;critical task,&nbsp;would&nbsp;be to give it to the user who is the most experienced and has handled the same task numerous time in the past, to ensure the task is carried out successfully.
 
Avoka User Selector DSC provides an intelligent way to work out whom the next task should be assigned to based on user current workload on&nbsp;current user&nbsp;workload and past history of completing tasks, and returns a nominated user for the next user task assignment.&nbsp; Once the nominated user is selected, the identifier of the nominated user is used in the User "assignTask" operation to be assigned the next task.

h3. The User Selector Service

This is developed by Avoka Technologies, containing a number of useful XML Utilities operations to manipulate XML data, from which two of them will be discussed in the following to cover the scenario discussed above.
\\ !operation.jpg!
*1. Select Least Busy User In Group*
&nbsp;&nbsp;&nbsp; This operation finds the least busy user in a group, judged by the least amount of active tasks currently assigned to the user. It also provides the option as&nbsp;to whether to include shared tasks into consideration, for user the&nbsp;consideration,&nbsp;as users can choose to share tasks with others.
\\
*2. Select Most Experienced User In Group*
&nbsp;&nbsp;&nbsp; This operation finds the most experienced user in a group, judged by the most number of tasks completed by the user.&nbsp; This operation optionally allows the search to be narrowed down to apply to a&nbsp;task of a&nbsp;particular process (if specified) and step name (if specified).

To obtain an evaluation copy of the XML Utilities Service, go to the Avoka Website: [http://www.avoka.com] and follow the links.
...
h3. The Process
\\ !process.jpg!\\
 
As shown in the figure above, the operation of User Selector service should be called first to find out the nominated user, and then the User assignTask in the next step, will use the nominated user identifier to assign the next task to.
 
For demonstration purposes, we have provided the exported [process XML file|^AssignDummyTasks.xml]for the process described above, as an&nbsp;attachment to this article. You can import it as a process to your LiveCycle ES via workbench for guidance in setting up property values for those User Selector operation steps.
\\

h3. Setting Properties for "Select Least Busy User In Group" Operation
\\ !leastBusyUserProperties.jpg!\\
 
&nbsp;
To configure the properties of the "Select Least Busy User In Group" operation step, click on that step, and click on "Properties" view on your Workbench. It will show a dialog shown above.
 
You will need to specify the group for the user selection, via the "..." button. Once clicked, it will pop up a dialog as shown below for group search and select.
\\ !groupSearch.jpg!\\
To configure the properties of the "Select Least Busy User In Group" operation step, click on that step, and click on "Properties" view on your Workbench. It will show a dialog box as&nbsp;shown above.
 
Then depends on your situation, you might want to include shared tasks into consideration. If that's the case, you will need to check the box for "Include Shared Tasks".&nbsp;
You will need to specify the group for the user selection, via the "..." button. Once clicked, it will pop up a dialog box as shown below for group search and select the appropriate entry and click OK.
\\ !groupSearch.jpg!\\
 
Then depending on your situation, you might want to include shared tasks into the&nbsp;consideration. If that is the case, you will need to check the box for "Include Shared Tasks".&nbsp;
Lastly, you Also&nbsp;you need to specify a process variable to store the nominated user identifier (Principal ID) for later use in User AssignTask operation. &nbsp;
\\

h3. Setting Properties for "Select Most Experienced User In Group" Operation
\\ !mostExperienceUserProperties.jpg!
&nbsp;
\\
To configure the properties of the "Select Most Experienced User In Group" operation step, click on that step, and click on "Properties" view on your Workbench. It will show a dialog box shown above.

For this operation, you also need to specify the group for the user selection with the same interface provided as in "Select Least Busy User In Group" operation.
...
Then optionally, you can narrow down the scope of the search by restricting it to apply to a particular process and a particular action name / step name if they are specified.&nbsp;
Lastly, Finally, you need to specify a process variable to store the nominated user identifier (Principal ID) for later use in User AssignTask operation.&nbsp;
\\
\\
...
Configure the rest of the properties of this operation according to your other requirements, such as "Form Data Mappings", Escalation, Deadline, etc.&nbsp;
&nbsp;
\\
\\