Thank you for responding, @Jason Lightfoot. Instead of my previous process flow, I generated flow objects utilizing Global tables and set labels to them based on your comment (in above pic).
Executed case: Later created a list for Queues and pulled the tokens to acquire the AGV. In this case (please look into the 1st pic which I shared with you in the previous comment) for 4 different processors I assigned 4 different item type labels. Now, this is fine and AGV automatically picks the items on respective Qs on availability.
But when I tried some other scenarios using the same logic I addressed the following problems
1. I was unable to assign the same label-type item to two different processors using the global table
for example,
Item type 1 to processors 1 and 3
Item Type 2 for processors 2 and 4
2. even, I created two different global tables for each item type and assigned them to process flow
Here, again I addressed another problem that
for Item type 1 I assigned a label to the token as a token.item1
for Item type 2 I assigned a label to the token as a token.item2
now, to acquire AGV I can only use one of the token types as an AGV destination. I don't know how to assign two different items to AGV destinations in the process flow.
3. Again, in the Executed case, AGV only collects one item and delivers it to delivery Q before returning back to collect the next item and continue.
I attempted to have AGV gather all items at all Qs and then move to the delivery Qs, but it failed.
I apologize for the lengthy explanation. As all of these issues are related to this topic, I thought to share them all here. If you feel it's too much and need to break it up into separate questions, simply let me know. I will do so.
