fork related problem

[shirodkar4]

hi,

i am using jboss starters kit 3.1.4

here is my processdefinition.xml file

<?xml version="1.0" encoding="UTF-8"?>

<process-definition
 xmlns="urn:jbpm.org:jpdl-3.1" name="firstProcess">
 <swimlane name="Market Requestor">
 <assignment expression="user(grover)"></assignment>
 </swimlane>
 <swimlane name="Process Leader">
 <assignment expression="user(ernie)"></assignment>
 </swimlane>
 <swimlane name="Market Strategy Director">
 <assignment expression="user(bert)"></assignment>
 </swimlane>
 <start-state name="Set up a draft proposal">
 <task name="Draft proposal" swimlane="Market Requestor">
 <controller>
 <variable name="Engine Type"></variable>
 </controller>
 </task>
 <transition name="" to="Notify Process Leader"></transition>
 </start-state>
 <task-node name="Notify Process Leader">
 <task swimlane="Market Strategy Director">
 <controller>
 <variable name="values" access="read,write,required"></variable>
 </controller>
 </task>
 <transition name="to branchfork" to="branchfork"></transition>
 </task-node>
 <fork name="branchfork">
 <transition name="Notify field support" to="Notify field support"></transition>
 <transition name="gather list of items to investigate" to="Gather list of items to investigate"></transition>
 </fork>
 <task-node name="Gather list of items to investigate">
 <task swimlane="Market Requestor">
 <controller>
 <variable name="Part Numbers"></variable>
 </controller>
 </task>
 <transition name="" to="branchjoin"></transition>
 </task-node>
 <task-node name="Notify field support">
 <task swimlane="Process Leader">
 <controller>
 <variable name="Person to notify"></variable>
 </controller>
 </task>
 <transition name="" to="branchjoin"></transition>
 </task-node>
 <join name="branchjoin">
 <transition name="" to="Review proposal"></transition>
 </join>
 <decision name="Review proposal">
 <transition name="approve proposal" to="Approve proposal">
 </transition>
 <transition name="reject proposal" to="Reject proposal"></transition>
 </decision>
 <task-node name="Approve proposal">
 <task name="Approve Proposal" swimlane="Market Strategy Director">
 <controller>
 <variable name="Comment" access="read,write,required"></variable>
 </controller>
 </task>
 <transition name="" to="end1"></transition>
 </task-node>
 <task-node name="Reject proposal">
 <task name="Reject Proposal" swimlane="Market Strategy Director">
 <controller>
 <variable name="Comment" access="read,write,required"></variable>
 </controller>
 </task>
 <transition name="" to="end1"></transition>
 </task-node>
 <end-state name="end1"></end-state>

</process-definition>

now the problem is the moment market strategy director saves and closes the task assigned to him

i get the message the task has been assigned to null,null

i have also made this observation that the TASK "getting list of items to investigate" which appears after the fork gets assigned to the user who begins the process rather than getting assigned to the user defined in the swimlane(grover) However the Task "Notify field support" gets assigned correctly to ernie.

is this a bug with JBPM-starters kit 3.1.4..

please help me as i am stuck.....

[kukeltje]

i get the message the task has been assigned to null,null

known issue with the 3.1.x webapp

The other issue I do not know about. Could be that the default behaviour in 3.1 is that the start task is assigned to the process initiator.

[shirodkar4]

hi,

thanks for the quick reply Ronald

the 1st error is not much of a concern.

but at least the second error(i think its a very serious error)

how can a process TASK be assigned to any random user when there is a particular swimlane(user) assigned to the Task.

one of the two Tasks after the fork is getting assigned to any random user rather than getting assigned to the swimlane user assigned to the task

if this happens then jbpm fails to correctly implement fork node as the whole concept of swimlane fails for tasks after the fork node

any help regarding this?

please as its critical to our evaluation of JBPM

[kukeltje]

What happens here is that in the start task you have a swimelane defined. I think what happens is that the swimlane get's overridden with the actor that started the process. Probably if you leave out the swimlane in the start-task it will work. Not sure if it is a bug or works as designed. You can then debate the (non)sense of this design, but that is another issue