Table of Contents

Table of Contents

Change flow product

Change flow product

Overview and Key Concepts

The Change flow product activity changes the current product of a flow object or, specifically in the case of a flow pipe, the type of the entering product.

Connectors

The Change flow product activity only allows one connector out. See Adding and Connecting Activities for more information.

Properties

The following image shows properties for the Change flow product activity:

Each of these properties will be explained in the following sections.

Name

Used to change the name of the activity. See Name for more information about this property.

Font

The Font button opens a window to edit the activity's background color and font properties. See Font for more information about this property.

Statistics

The Statistics button opens the activity's statistics window. See Statistics for more information about this property.

Object(s)/ Group / Array

Use the Object(s) / Group / Array box to specify the object(s) you want the activity to affect. You can specify a single object (using the eyedropper tool or a model.find() command), an object group (flat or nested) or an array of objects and/or groups. When a token enters the activity, the expression will be parsed recursively such that arrays of groups or groups will be properly handled.

Change Product Type To

Specify the new product type. This can be a numeric product ID, or the name of a product from the FloWorks product table. See the Products concept page for more information about numeric vs. named products.

Condition

If the condition is not set to "Always", the activity will only perform its functionality when the condition returns true. If the Object(s) / Group / Array field evaluates to multiple objects, the condition will be checked for each object separately (and passed in as the involved parameter).

The dropdown suggests a few common conditions, such as only working on objects that currently have inflow, or are below their maximum content. You can use it to implement logical conditions (e.g. only open output if a tank is full), but also for model constraints (e.g. only do something with output port 2 if the involved object has at least two output objects).