Multiple condition
Home –> Reference –> Multiple condition
A condition activity that can branch into multiple routes if the Rule is True. The Process follows the first Rule that is met in the list, even if following Rules are also True. The order of the Rules can be changed.
Configuration Dialogs
There are three ways to configure this shape:
- Simple Mode
- Advanced Mode
- Custom Mode
Simple Mode
Field Name / Button | Definition |
---|---|
Name | See (Name) |
Data Binding | See Property Binding |
Description | See Description |
Type | See Type |
Ellipsis (…) | Opens the dialog for selecting a process variable or context data. See Schema Selector |
Advanced Mode | Click to configure shape in Advanced Mode |
Field Name / Button | Definition |
---|---|
New… | Add a new expression |
Edit | Edit an existing expression |
Remove | Remove an existing expression. (Remember to remove any orphaned connectors) |
Move Up / Down | Select an expression and use these buttons to change the order of the expressions. The shape executes the expressions in this order and as soon as an expression is evaluated to TRUE, the corresponding route is followed and the rest of the expressions are not evaluated |
Field Name / Button | Definition |
---|---|
Name | See (Name) |
Operator | Operator |
Value | Type a literal value TIP: If you need to use a dynamic value, then use the Advanced Mode TIP: You can use this shape to determine whether a String value is null by using the “=” operator and entering the value <NULL> |
Advanced Mode
- Drop a Multi-Condition Shape on the canvas
- Click Advanced Mode button
- Click New button
Field Name / Button | Definition |
---|---|
Description | See Description |
New | Open the Define Expression dialog for adding a new condition |
Edit | Edit an existing condition TIP: Click F2 or double-click the text below a condition to edit it |
Remove | Deletes an existing condition |
Advanced | Click to configure this condition in Custom Mode |
Move Up / Down | Select a condition and use these buttons to change the order of the conditions. The shape executes the conditions in this order and as soon as a condition is evaluated to TRUE, the corresponding route is followed and the rest of the conditions are not evaluated |
Field Name / Button | Definition |
---|---|
Bracket | Use for grouping expressions for constructing more complex conditions e.g. (((a = 1) or (b>2)) and (c=d)) |
Name | Name of the attribute to be evaluated on the left side of the expression TIP: In the drop-down click <XML Schema> to open the dialog for selecting a process variable or context data See Schema Selector |
Operator | Operator |
Value | Either use a literal or a dynamic value TIP: In the drop-down click <XML Schema> to open the dialog for selecting a process variable or context data See Schema Selector |
Logic | Use the AND or OR operators |
+ - buttons | Use for adding more expressions or removing existing expression |
Validate | Validates the condition and either shows a success or an error dialog |
Custom Mode
- Drop a Multi-Condition Shape on the canvas
- Click Advanced Mode button
- Click Advanced button
Field Name / Button | Definition |
---|---|
Expression field | Use this for building custom expressions in .NET TIP: There is Intellisense to help create the expressions |
Schema | Opens the dialog for selecting a process variable or context data NOTE: Make sure these variables are inside quotes e.g. “${MyAttribute}”</ See Schema Selector |
Validate | Validates the condition and shows an error dialog if necessary. It does not show a success dialog if expression is valid. |
Shape-Specific Properties
Property | Description |
---|---|
Property Binding | Click its ellipsis button to open the configuration dialog. The data binding expression that is used to evaluate the value of the condition at runtime. NOTE: This field is shown as empty in Advanced and Custom Modes</blockquote> |
Other Common Properties
All shapes have many other common properties. Look them up here: Common Poperties
Actions
Double-clicking this shape opens its configuration dialog.
See Actions