-
1. Re: Link between lanes and Human Tasks - Send and Receive task in the same process.
swiderski.maciej Dec 6, 2013 2:22 AM (in response to sadiroveski)1 of 1 people found this helpfuljBPM will try to assign same user to all tasks within the same lane e.g. if there are several tasks on a lane, user who claimed and completed the first task will be assigned to the other tasks on the lane. Considering of course that user possibilities to be assigned - like if (s)he is listed as potential owner. This is to simplify and omit one step (claiming) in case of many or group assignment on the task which is usually used with lanes.
Not really sure what you mean with send and receive tasks? Could you elaborate a bit?
HTH
-
2. Re: Link between lanes and Human Tasks - Send and Receive task in the same process.
sadiroveski Dec 6, 2013 9:58 AM (in response to swiderski.maciej)Thanks Maciej for your response.
Maciej Swiderski wrote:
jBPM will try to assign same user to all tasks within the same lane e.g. if there are several tasks on a lane, user who claimed and completed the first task will be assigned to the other tasks on the lane. Considering of course that user possibilities to be assigned - like if (s)he is listed as potential owner. This is to simplify and omit one step (claiming) in case of many or group assignment on the task which is usually used with lanes.
In order for the user to claim, he must be a member of a Group (For example: HR). Do you mean that I must assign the group-id on the first task and leave other tasks without mentioning Actor_name or Group ID? Or can jBPM look to the Lane Name and Assign the Lane Name as Group-ID on the task.
Not really sure what you mean with send and receive tasks? Could you elaborate a bit?
I have a Send Task in my process, I want to add a lane, which represent a participant, and connect the Send task to the lane. The lane is abstract here where it is designed in details in another process. The attached image is an example. How jBPM can connect to this lane and the Task to the responding receive task in another process? is it mapped by its unique name?
Thanks in advance.
-
ReceiveTask.png 23.7 KB
-
-
3. Re: Link between lanes and Human Tasks - Send and Receive task in the same process.
swiderski.maciej Dec 9, 2013 1:36 AM (in response to sadiroveski)Sadiroveski S wrote:
Thanks Maciej for your response.
Maciej Swiderski wrote:
jBPM will try to assign same user to all tasks within the same lane e.g. if there are several tasks on a lane, user who claimed and completed the first task will be assigned to the other tasks on the lane. Considering of course that user possibilities to be assigned - like if (s)he is listed as potential owner. This is to simplify and omit one step (claiming) in case of many or group assignment on the task which is usually used with lanes.
In order for the user to claim, he must be a member of a Group (For example: HR). Do you mean that I must assign the group-id on the first task and leave other tasks without mentioning Actor_name or Group ID? Or can jBPM look to the Lane Name and Assign the Lane Name as Group-ID on the task.
usually you assign the group id (same group id) to all the tasks on the same lane. jBPM then will ensure that the user who claimed and completed first task will be directly assigned (making task reserved for him) to all the tasks on that lane.
Sadiroveski S wrote:
Not really sure what you mean with send and receive tasks? Could you elaborate a bit?
I have a Send Task in my process, I want to add a lane, which represent a participant, and connect the Send task to the lane. The lane is abstract here where it is designed in details in another process. The attached image is an example. How jBPM can connect to this lane and the Task to the responding receive task in another process? is it mapped by its unique name?
besides what is available from documentation point of view I don't think there is other way to link send and receive tasks on different lanes. When it comes to runtime behavior it depends on the implementation of send and receive task as they are backed by work item handlers. So if your handlers will take the unique names into account that could work.
HTH