Operator Acquire and Release through process flow blocking

Operator Acquire and Release through process flow blocking

ddtsk
Contributor Contributor
161 Views
4 Replies
Message 1 of 5

Operator Acquire and Release through process flow blocking

ddtsk
Contributor
Contributor

Hey Flex simmers,
I have a use case where an operators set need to travel and load which I am having it in a process flow and other action for same operators set i need to travel to another place to unload the item, So below is the example model where I tried to model the same, but here I am observing two challenges 
1.The same operator set is not getting called for second process 
2.And after some load and unload activities the operators are not taking up new tasks 

Kindly can someone help me in fixing this issue. Thanks in advance for you valuable time and efforts.

0 Likes
162 Views
4 Replies
Replies (4)
Message 2 of 5

xavier_low
Contributor
Contributor

Hi @ddtsk ,

The operators are not taking up new tasks because you need to add a 'Finish TS' Activity to pair with your 'Create TS' Activity. Otherwise, the operators will not move on to other task sequences, which is what you are currently seeing.

0 Likes
Message 3 of 5

ddtsk
Contributor
Contributor

Hey @xavier_low,
Thanks for quick fix solution it resolved my problem, I am still observing one issue where the same resource sets are not getting acquired in both the process flow, do you have in resolving it.

Thanks

0 Likes
Message 4 of 5

xavier_low
Contributor
Contributor

Regarding the issue where you want the operator to set both travel and load the item, you will need to create a coordinated task sequence. You can refer this tutorial to learn how to set up a coordinated task: Tutorial 2 - Coordinated Tasks

 

Using one 'Create TS' Activity, it only allows creating a task sequence and dispatching to one operator; it is not capable of creating the task sequence for multiple operators. Hope this helps.

0 Likes
Message 5 of 5

moehlmann_fe
Enthusiast
Enthusiast

The second Acquire not getting the same operators seems to be a bug. For some reason the first Acquire not having a query leads to the array being ignored. If you add some placeholder query (like "WHERE 1") to the first Acquire it works.

Alternatively you can also use the query "WHERE value IN puller.Ops" for the second Acquire activity. That works as expected.

0 Likes