When you are using process flow to control the movement between different queues in order to avoid the connections, it seems like the max content you set on the queue doesn't matter any more, if you define the capacity of the queue to be 1, you can keep moving item to the queue using moving object activity, is this a bug in the software? This is causing some unexpected behaviors and resulting in using zone to add extra layer of controls.
Thanks,
Hi Chao,
This is not a bug. One of the useful aspects of Process Flow is being able to control the logic separately from the fixed resource logic. As you mentioned, one way to set a max content in this case is to use a zone. There are probably multiple other ways to approach this, but it may depend on how your model works and what you're trying to accomplish. For example, you can move an object in Process Flow to one queue, then connect that queue to your queue with max content of 1 so that the fixed resource logic takes over. Another way you might handle this is by adding a "Decide" activity in Process Flow to check the content of the queue before moving the object.
Let us know if this resolves your concerns or if you continue to have issues in your model. If the latter case is true, sending an example model of the problem may be helpful.
The script command moveobject isn't intended to respect the standard flow logic which check if an object is active, available to receive items or capacity is left to store items. All such aspects lay in the hands of the user to program. Instead it is useful to move any object you can set a pointer to, too.
Would this also mean the triggers on the queue would not function the same when moving an object into a queue using process flow?
No, the trigger functions by using script command and ProcessFlow. On Entry Trigger changes color of the surrounding plane of the queues.
6 People are following this question.
© 1993- FlexSim Software Products, Inc. All Rights Reserved.
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.
