topic Using Release Token from Pull from List activity. in FlexSim Forum

Using Release Token from Pull from List activity.

richard_McClaughry — Wed, 01 May 2024 14:43:21 GMT

[ FlexSim 24.0.0 ]

I am looking for a way to release a token from a Pull from List activity early based on another activity triggering or TE position.

I had thought to use "Release Token" with it pointed to "Tokens in Pull from List", but that didn't work.

Is this this a valid approach? Are one of the "Use Max ... Timer" options in the Pull from List a better method, even though its not necessarily time based?

Release Token from Pull List v2.fsm

Re: Using Release Token from Pull from List activity.

Jeanette_Fullmer — Wed, 01 May 2024 15:53:19 GMT

Hello @Richard M,

This should work if you use the picklist option

If you are using this and having an issue make sure that your pull from list activity has a unique name from other activities.

Re: Using Release Token from Pull from List activity.

richard_McClaughry — Wed, 01 May 2024 16:32:04 GMT

I am already using the "Tokens in Activity" option, as shown from the snip. Unless I'm misunderstanding what you mean by the "picklist". The List is a unique name, its the "AGV Work List" from the "AGV with Basic Parking" template.

I've attached the model. The interaction is between TE6 at CP "Dispatch1" and TE8 finishing its unload at Finish1 at around 4650.

Release Token from Pull List.fsm

Re: Using Release Token from Pull from List activity.

moehlmann_fe — Thu, 02 May 2024 06:06:01 GMT

Your model didn't upload successfully. But I noticed that you have two activities with the same name in your screenshot. The "Tokens in Activity" option searches for the activity by name and will use the first occurence it finds in the tree. So currently you might be releasing the tokens from the left Pull from List. Maybe try giving the activities unique names.

Re: Using Release Token from Pull from List activity.

richard_McClaughry — Thu, 02 May 2024 13:09:04 GMT

I attached the file again to the original question.

I also gave the Pull from List target and the "Release to" unique names, but it is still not releasing.

Re: Using Release Token from Pull from List activity.

moehlmann_fe — Thu, 02 May 2024 13:23:08 GMT

The issue is that the waiting token and the 'release' token are part of separate instances. By default only tokens in the same instance are found/released.

In the code of the "Token(s)" field in the Release activity replace line 14 ("Array tokens = ...") with the following. Somebody else might know a more elegant version but this should work.

// Get instances of Process Flow
Array instances = processFlow.find(">stats/instances").subnodes.toArray();
Array tokens = [];
for(int i = 1; i <= instances.length; i++)
{
    tokens.append(gettokens(ownerobject(instances.value), otherActivity, flags));
}

Another issue that then became apparent, is that none of the "Finish" processors are connected to their respective CPs.

Re: Using Release Token from Pull from List activity.

richard_McClaughry — Mon, 06 May 2024 11:58:49 GMT

That worked, thank you.

Based on you statement:
"The issue is that the waiting token and the 'release' token are part of separate instances. By default only tokens in the same instance are found/released."

Would moving the block of logic with the Release Token into the container with the target of the Release have worked as well?

Re: Using Release Token from Pull from List activity.

moehlmann_fe — Mon, 06 May 2024 12:21:00 GMT

No. The AGV Process Flow template is an Object Process Flow. Essentially, for each instance object a separate copy of the same Process Flow exists, but the instances work largely independently from each other.

Tokens from different instances normally do not interact with each other. For example, a batch activity would create separate batches for each instance. That is why you need the custom code to also release tokens from other instances.

Re: Using Release Token from Pull from List activity.

richard_McClaughry — Mon, 06 May 2024 12:24:51 GMT

Got it, thank you for the clarification.