I'm trying to implement a process flow into an existing simulation that is mainly built using task sequence and triggers OnMessage.
I'm having troubles starting my process flow (that mainly dictates how flow items are to be located insinde a Queue) through that task sequence.
Process Flow has two activities that can be used to listen to events on objects. This is the Event-Triggered Source and the Wait For Event. The Event-Triggered Source will create a new token when the event fires, the Wait for Event requires a token to already exist that will wait on the activity until the specified event fires.
In both cases you can tie the activity to listen to events like On Entry, On Message, etc. (Use the sample button and hover over the desired object to see a list of that object's events). Each events passes in different parameters that you get access to (for instance, a reference to an entering or exiting item). You can store off the parameters and then send the token through a set of activities to perform whatever logic you're trying to accomplish.
I've not used it much myself yet, but there is a createtoken() command. This will create a token in the instanced (or general) process flow, at the designated activity. You could try using this command to create tokens at a certains starting point in your process flow, during the execution of the task sequence code.
Here is the info about create token:
createtoken(instanceObject, activity, start)
Creates a token and places the token inside the activity for the given owner object (instance).
(obj instanceObject, obj/str activity, int start)
Creates a token and places the token inside the activity for the given owner object (instance). If start is 1, the token will immediately call the activity's start and begin moving through the process flow. If start is 0, the token will sit in the activity until releasetoken() is called on the token. Calling releasetoken() will fire the activity's finish causing the activity's start to never be called. This may affect how the token responds to the activity it was created in.
For example, if a token is created in an Assign Labels activity with a start of 1, the created token will evaluate the Assign Labels as if entering the activity and receive whatever labels are assigned to it. If a token is created in the same Assign Labels with a start of 0 and then later releasetoken() is called on that token, the token will never evaluate the Assign Labels and will not get any labels set on it.
Return value is the created token.
treenode token = creattoken(node("Operator1", model()), "Start", 0);
setlabel(token, "type", 1);
releasetoken(token);
Did you copy that verbatim from the user manual? Because there is a typo in the first line of the example: creat(e)token.
16 People are following this question.
FlexSim can help you understand and improve any system or process. Transform your existing data into accurate predictions.
FlexSim is a fully 3D simulation software environment. FlexSim can be used to simulate any process in any industry.
FlexSim®, FlexSim Healthcare™, Problem Solved.®, the FlexSim logo, the FlexSim X-mark, and the FlexSim Healthcare logo with stylized Caduceus mark are trademarks of FlexSim Software Products, Inc. All rights reserved.
