You can try with adding a ManagerUser2 task in the same swimlane that the
first task ManagerUser task instead of going back to the first one.
On Tue, Sep 3, 2013 at 5:46 AM, Zahid Ahmed <zahid.ahmed(a)emirates.com>wrote:
Hi Mauricio,****
** **
Thanks for the details. Could u please suggest a possible solution to make
it work (Preferably with swimlanes).****
** **
One solution in my mind was to keep the Id of the assigning manager and
group in a process variable. ManagerUser task will have actor and group
attributes as follows.****
**1. **Actor => #{piManager}****
**2. **GroupID => #{piProcurementManagerGroup}****
** **
*Flow 1*
When for the first time flow comes to the ManagerUser, the #{piManager}
will return an empty String “” and #{piProcurementManagerGroup} will return
the groupId = “procurement”. ****
**a. **#{piManager} = “”****
**b. **#{piProcurementManagerGroup} = “procurement”****
** **
In this flow the task will be assigned to the “procurement” group and will
be available to claim. ****
** **
*Flow 2*
When flow leaves ManagerUser task it will populate the value of
#{piManager} and will clearOff the val;ue of #{piProcurementManagerGroup}.
So values will be as follows****
**c. **#{piManager} = “alex_manager”****
**d. **#{piProcurementManagerGroup} = “”****
** **
Now when the flow comes again to ManagerUser after submission from
SubOrdinate UserTask, the task will be directly assigned to “alex_manager”
user. As group is empty and there is only one user left for assignment,
task will be directly assigned to “alex_manager” in RESERVED status.****
** **
** **
*NOTE : I was hoping to have a simpler solution without having to
implement this logic in script variables or in process definition.\***
** **
** **
Regards,****
** **
Zahid****
** **
*From:* rules-users-bounces(a)lists.jboss.org [mailto:
rules-users-bounces(a)lists.jboss.org] *On Behalf Of *Mauricio Salatino
*Sent:* 02 September 2013 15:41
*To:* Rules Users List
*Subject:* Re: [rules-users] JBPM : Need solution with SwimLane****
** **
Yeah, because as far as I know that's not the intention of a swimlane. The
main idea is taht if you have multiple tasks in the same swimlane all of
them will be assigned to the same actor, but in this case you have only one
task in the swim lane and then you are going into the swimlane again, so it
will create a new context again.. and that's the expected behavior as far
as I know. ****
** **
On Mon, Sep 2, 2013 at 12:34 PM, Zahid Ahmed <zahid.ahmed(a)emirates.com>
wrote:****
Hi,****
****
I am testing swim lanes for a scenario in my requirements. But, I am
unable to get my desired results. ****
****
*Scenario: The scenario *is that when a subordinate task completes and
assigns back to ManagerTask. The manager who assigned the task should be
getting the task again now without having to claim it. For this I have
tried to use swim lanes but its not working. PFA BPMN2 and process image.*
***
****
****
****
****
Regards,****
****
Zahid****
****
****
****
****
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users****
****
** **
-- ****
- MyJourney @
http://salaboy.com <
http://salaboy.wordpress.com>****
- Co-Founder @
http://www.jugargentina.org
- Co-Founder @
http://www.jbug.com.ar
- Salatino "Salaboy" Mauricio -****
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users