ProcessFlow: Wait for Event, match the state it is changing "from"

Question

question

Tom S4 asked May 13 2022 at 2:28 PM Jordan Johnson commented May 16 2022 at 4:05 PM

ProcessFlow: Wait for Event, match the state it is changing "from"

My understanding is that when waiting for a state change event, the new state value can be accessed (matched, assigned, etc). Is there a method to access the old value?

Software Version:

FlexSim 21.1.5

processflow states event trigger

· 1

______

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

YES

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

YES

NO

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

YES

NO

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.

Answer 1 · 2022-05-13T15:17:52Z

Jason Lightfoot answered May 13 2022 at 3:17 PM Jordan Johnson commented May 16 2022 at 4:05 PM

When the event is triggered the state on the BasicFR object is still the old state, so you can detect the new and old.

· 2

Tom S4 commented · May 13 2022 at 3:40 PM

Hi Jason. Thank you for the response.

Are there plans to add to/from to the event params in the future? Right now I don't see any other way to match 'from' without triggering on every state change and checking current state in a separate block, which I imagine would be a hit to performance as tokens need to be created and more events are added to the event queue.

I've attached an example model for the solution I'm thinking.

Example State Change Model.fsm

0 ·

example-state-change-model.fsm (31.9 KiB)

Jordan Johnson ♦♦ Tom S4 commented · May 16 2022 at 4:05 PM

The old value is exposed in the On State Value Change event, or in the OnChange event of the state profile, if you listen to that directly. However, the UI for the Wait for Event or Event Triggered Source shows the Tracked Variable event UI, which doesn't let you work with the old value. You can set up a custom listener, if you really need those values. But it's usually bad practice to try to define model logic based on state change, for two reasons:

Objects frequently go into states for zero time. For example, when an item arrives at a Processor, the Processor will enter the setup state, even if the setup time is zero. In addition, when the item leaves, the Processor will enter the Blocked state, even if the item is blocked for zero time.
The state change event is fired in response to resetting the model, as well as stopping the model. There are probably other UI-level events that cause that event to fire.

Usually, there's some other approach that avoids all of these issues. I'd recommend looking for some other approach. If you post a new question, and explain why you needed the old value (along with a demo model), we may be able to help you find a better alternative.

0 ·

question