swimlaneInstance overwritten when creating startTaskInstance

[morpheus_jboss]

confused in TaskMgmtInstance createStartTaskInstance:

 public TaskInstance createStartTaskInstance() {
 ...
 taskInstance.setActorId(SecurityHelper.getAuthenticatedActorId());
 return taskInstance;
 }

this will overwrite any (if there is any) initialized swimlaneInstances related to this taskInstance because:

 /**
 * (re)assign this task to the given actor. If this task is related
 * to a swimlane instance, that swimlane instance will be updated as well.
 */
 public void setActorId(String actorId) {
 setActorId(actorId, true);
 }

 /**
 * (re)assign this task to the given actor.
 * @param actorId is reference to the person that is assigned to this task.
 * @param overwriteSwimlane specifies if the related swimlane
 * should be overwritten with the given swimlaneActorId.
 */
 public void setActorId(String actorId, boolean overwriteSwimlane){
 ...
 }

in our application we have to initialize all swimlaneInstances at processInstance creation time, in order to do reassignment dynamically before the start of a process.

So would it be better if the code looks like this:

 public TaskInstance createStartTaskInstance() {
 ...
 taskInstance.setActorId(SecurityHelper.getAuthenticatedActorId(), false);
 return taskInstance;
 }

[morpheus_jboss]

same problem exists also in TaskInstance:

public void assign(ExecutionContext executionContext) {
...
 if (isStartTaskInstance()) {
 // initialize the swimlane
 swimlaneInstance = new SwimlaneInstance(swimlane);
 taskMgmtInstance.addSwimlaneInstance(swimlaneInstance);
 // with the current authenticated actor
 swimlaneInstance.setActorId(SecurityHelper.getAuthenticatedActorId());

 } else {
...

what is the connection between the Authentication and a startTask?

[morpheus_jboss]

Hi, can anyone share some idea on this issue? Maybe I did not explain the problem well, so here again:

if jbpm set the actorId on a taskInstance with update on the related swimlaneInstance, and this swimlaneInstance was initialized with pooledActors, what will be the consequences? how does jbpm deal with a swimlaneInstance with both actorId and pooledActors set?

tks!

[kukeltje]

the last question is completely independent of the rest. Behaviour is simple:
- pooled actors and no actor: task is in 'group' tasklist
- pooled actors and actor: task is assigned to individual actor id and not in the group tasklist

[morpheus_jboss]

Hallo Ronald,

Tks for your reply.

"pooled actors and actor: task is assigned to individual actor id and not in the group tasklist"
-- yes your reply confirms my assumption. but
-- then after creating the instance for the first task, the related swimlaneInstance with pooledActors changes its behavior: the originally as group task designed task is set to the actor who created the first taskInstance.

[kukeltje]

It does not change the bahaviour. The behaviour you see is as designed. This is how you assign a task to an individual user from a pool of 'possible users'. If you set the actor to null again, it is 'assigned back' to the pool

[morpheus_jboss]

"kukeltje" wrote:
It does not change the bahaviour. The behaviour you see is as designed. This is how you assign a task to an individual user from a pool of 'possible users'. If you set the actor to null again, it is 'assigned back' to the pool

Tks Ronald, but I already understood this part. The problem is with swimlaneInstance, which affects not only one peticular task but also all the tasks related to this swimlane.

[kukeltje]

correct, that is why it is a swimlane.... to have the opportunity to do it on a more generic level than one task