-
1. Re: swimlaneInstance overwritten when creating startTaskInst
morpheus_jboss Apr 20, 2007 10:37 AM (in response to 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? -
2. Re: swimlaneInstance overwritten when creating startTaskInst
morpheus_jboss Apr 24, 2007 7:45 AM (in response to 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! -
3. Re: swimlaneInstance overwritten when creating startTaskInst
kukeltje Apr 24, 2007 8:33 AM (in response to morpheus_jboss)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 -
4. Re: swimlaneInstance overwritten when creating startTaskInst
morpheus_jboss Apr 24, 2007 12:25 PM (in response to 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. -
5. Re: swimlaneInstance overwritten when creating startTaskInst
kukeltje Apr 25, 2007 4:13 AM (in response to morpheus_jboss)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
-
6. Re: swimlaneInstance overwritten when creating startTaskInst
morpheus_jboss Apr 25, 2007 9:40 AM (in response to 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. -
7. Re: swimlaneInstance overwritten when creating startTaskInst
kukeltje Apr 25, 2007 12:59 PM (in response to morpheus_jboss)correct, that is why it is a swimlane.... to have the opportunity to do it on a more generic level than one task