Conditions determine whether a certain transition is executed in a process flow. Conditions are used to change the direction of the process flow based on a decision. There are three types of conditions:
| Anchor | ||||
|---|---|---|---|---|
|
...
To add a Condition in a process flow using Expression:
In Web Process Designer, in the Toggle Palette panel, select Gateway element and drag it in the canvas area. Alternatively, click the Source element and select Append Gateway option from Context pad.
Connect the activities, for information on how to connect activities, refer to Creating Process Flow.
To add a condition, select the control flow and click the Options icon and then select Define Condition to display Sequence Flow Condition window.
On the Sequence Flow Condition window, select Expression.
Select the condition to be used for building the expression from the Operator option. You can select the values && (AND) and || (OR).
For defining expressions you need to define rules. A rule supports multiple expressions. You can link the multiple expressions using the rule operator.
Click Add to define the rule.
Provide the details of the rule.
Field NameDescriptionRule Name Name of the rule. Rule Reason Reason on the basis of which the rule will be evaluated as true or false. This is set in the context of the process flow.
Existing Activities Activity Attribute or process flow variable used to build the expression. This drop-down is populated with the current activities. Alternately, if you select a blank value, then a process flow variable is selected.
Activity Attribute/Variable This drop-down is populated with values based on the selection in the Existing Activities field. If an activity is selected, then this drop-down lists all the attributes of the selected activity. If a process flow variable is selected, then this dropdown lists the currently available process flow variables. Operand type Data type of the selected activity attribute or process flow variable.
Number: Select this option if the specified activity attribute contains a numeric value, for example, 1, 12.
Text: Select this option if the specified activity attribute contains a text value, for example, processflow.
Decimal: Select this option if the specified activity attribute contains a decimal value, for example, 10.211, 100.50. The decimal precision can be defined under the decimal precision text field.
Operator Operator to be applied to the activity attribute or process flow variable. The supported operators are:
"=", "! =", ">", "<", ">=", "<=" for Number and Decimal Operand Type.
Equal, Not Equal, Equal Ignore Case, Not Equal Ignore Case for Text Operand type.
Value Value of the activity attribute or process flow variable that needs to be verified. The Number Operand Type should be of data type Long. The Decimal Operand Type should be of Double data type. Click Add to insert the defined condition (comprising of activity attribute or process flow variable) into the Expression text area.
- Once the activity attributes or process flow variable is inserted, you can create another condition for building the expression. Select the condition to be used for building the expression from the Declare Operator to build Expression with values of && (AND) and || (OR).
Select the operator on the basis of which you want to evaluate these rules from the Rule Operator. The supported rule operators are.
Rule Operator
Description
|| This evaluates the rules based on the OR operator. If any of the listed rules are true, then the decision value in the process flow will be executed as true.
&&
This evaluates the rules based on the AND operator. If all the listed rules are true, then only the decision value in the process flow will be executed as true. If any of the listed rules is false, then the decision value will be executed as false.
You can evaluate the rules using one operator at a time. For example, if you select || then all rules will be evaluated on the basis of the OR operator. You cannot evaluate two rules based on the OR operator and two rules based on the AND operator.Click Add to insert the selected operator into the Expression text area.
Both the conditions are displayed in the Expression text area. You can edit this expression for evaluation based on certain rules. These rules are outlined in the table below.
Object
Rule
Activity Attribute/Process Flow Variable
It is to be displayed between $$. For example, Activity Attribute will be displayed as $$ Service. Activity. Activity Attribute $$
Process Flow variable will be displayed as $$ var1 $$Operand Text
All values are enclosed within double quotes. For example, ("text").
Values having '\' are replaced by '\\'.
Values having double quotes (") are replaced by single quotes (').
Operator Equal
The condition is replaced as ($$var$$.equals ("text")).
Operator Not Equal
The condition is replaced as! ($$var$$.equals ("text")).
Operator Equal Ignore Case
The condition is replaced as ($$var$$.equalsIgnoreCase ("text")).
Operator Not Equal Ignore Case
The condition is replaced as! ($$var$$.equalsIgnoreCase ("text")).
The transaction will get aborted if an invalid expression is entered in the Expression text area.Click Done. This returns to the Sequence Flow Condition window with the newly added rule. Similarly, you can add more rules.
You can also edit the Rule Name and Rule Reason from this window by selecting the rule and then clicking Edit option.- Click Done. This closes the window and returns to the Canvas area.
Once you execute the process flow, all the listed rules will be evaluated in the top to bottom sequential order.
If they are evaluated using the OR (||) rule operator, then if any of the listed rules are true, then the decision value will be true and the process flow will be executed in the True path. The reason for all rules that are evaluated as True, will be added as comma separated values, and set as a single value in the context variable ruleReason in the format ruleName (ruleReason).
If the rules are evaluated using the AND (&&) rule operator, then only if all the listed rules are true, then the decision value will be true and the process flow will be executed in the True path. Even if one rule is evaluated to false, then the decision value will be false and process flow will execute in the False path. The reason for all rules that are evaluated as True, will be added as comma separated values and set as a single value in the context variable ruleReason in the format ruleName (ruleReason). The rules that are evaluated as False, will appear as an empty value in the ruleReason context variable.