Maciej Swiderski [https://community.jboss.org/people/swiderski.maciej] created the discussion "Re: Dynamic User Task assignment" To view the discussion, visit: https://community.jboss.org/message/787277#787277 -------------------------------------------------------------- yes, I would say that this is the recommended way of handling dynamic assignment yes, it is treated as any other input parameter that is passed to work item handler. Please note (as Evaluation example illustrates) group assignments is done by specifying data input named GroupId and then you can leave potential owner empty but the construct must be there otherwise parser will complain. in general the best practice is to use process variables to refer to the actual assignee (regardless if it's an actor or a group). The other story is on how do you get the proper value for that variable. One and the simplest way is to ask for it when process starts but of course that is not the only way. Since this is process variable it can be set by other tasks (outcome of a service task), it can be set by business rule since you can access process instance in drools rule, can be set when signaling with event data, etc. You're right the main requirement for user tasks is that there must be at least one valid business administrator by valid I mean it must be known to the task service. There are two ways of informing task service about users and groups: * use UserGroupCallback to load users and groups on demand - recommended * prepopulate task service db with all users and groups you could have a dedicated service that decides about assignment and then use that service in one of the following ways: * define a dedicated service task node that will contact the service and get the right assignee based on some input * define a rule that will contact the service .... * use on entry (not a big fun of putting it there as it's hidden) * if the service is not complex and does not have dependencies to outside world you could make it as process variable and when assigning data input/potential owner call a method of that process variable as mentioned above, yes it is possible to prepare process variable that will be used to assign people to the task. Most likely it would be possible to use task service/client inside the rule consequence to do the assignment post task creation but I think it is too complex for the case. Moreover there is a rule base inside the task service session that has access to task and its data (like potential owners) so defining rules there is yet another option. Please note that to use that I believe it must be initialized differently than what demo setup does so most likely it cannot be shown on demo installation. HTH -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/787277#787277] Start a new discussion in jBPM at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Thomas Setiabudi [https://community.jboss.org/people/thomas.setiabudi] created the discussion "Re: Dynamic User Task assignment" To view the discussion, visit: https://community.jboss.org/message/787552#787552 -------------------------------------------------------------- Hi Franck cdsosi, You got a great answer from Maciej there.  I just want to add another alternative, which is to create a custom implementation of Human Task Handler. this Custom Human Task handler can have the logic on how to resolve the correct actorId or groupId of the task based on some input (you can specify many input parameters for a user task). Regards, Thomas Setiabudi -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/787552#787552] Start a new discussion in jBPM at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Franck cdsosi [https://community.jboss.org/people/cdsosi] created the discussion "Re: Dynamic User Task assignment" To view the discussion, visit: https://community.jboss.org/message/788782#788782 -------------------------------------------------------------- Really thanks to Maciej for such a detailed reply, I am gonna have a look at it carefully ;) Thanks also to Thomas for alternative solution. Correct me if I am wrong but the drawback I see with your solution is that if you create a custom implementation of Human Task Handler it applies to all the Human Task Nodes meaning that you must handle all cases in your handler even for different processes (which may not have same requirements) which I found not to be very flexible. You could say to use different sessions but it could become quite complicated to handle if there are many different cases... Franck -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/788782#788782] Start a new discussion in jBPM at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]