1 Reply Latest reply on Oct 15, 2005 11:30 AM by kukeltje

    Group task assignment



      The application I'm thinking of using jBPM for involves a large number of long-running tasks that will be assigned to workers with a very high turnover rate. For example on date x, I may have 10,000 instances of a particular task, and it may be a month before someone has a chance to get to each task. At the time the TaskInstance is created, the worker who eventually does the task may not even be hired yet.

      I'd like to be able to assign a TaskInstance to a Group, and to query TaskMgmtSession for all the TaskInstances assigned to a particular Group. As far as I can tell, at the time of initial TaskInstance creation/assignment, I must retreive a list of all potential actors for the task and assign the TaskInstance to a "group" that way:

      Assignable.setPooledActors(java.lang.String[] pooledActors)

      If necessary, I think I can accomplish my requirement by initially assigning a TaskInstance to a fake actor name (i.e. "Unassigned") that represents a group, and then just reassigning the TaskInstance later, but this doens't seem like a very elegant solution.

      Am I interpreting the task management API correctly? Is there a better way to deal with this requirement?

      Thanks for your help!


        • 1. Re: Group task assignment

          using the unassigned actorname is fine. jBPM does not care about the actorID being either an individual user or a group.

          You can then runtime reassing the task to some individual user once he/she starts working on it.