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:

Process Flow Variable Condition
Java Condition
Expression Condition

Process Flow Variable Condition

A transition may have a condition based on the value of the context variable present in the current process flow. Once the condition is met, a transition takes place. The Process Flow Variable Condition can be of two types:

Activity Attributes Condition: Activity Attributes Condition is used to define a condition based on the value activity specific context variable in a process flow.
Other Condition: Other Condition is used to define a condition using pre-created context variables.

Process Designer allows Conditions to be added only for uncontrolled or default flow having gateway as its source. User cannot enter Condition for Association and Direction association flow under any circumstances.

Adding Condition Using Process Flow Activity Attributes

To add a Condition in a process flow using activity attributes:

In the Process Designer, in the Palette View panel, select Gateway ( ) element and drag it in the Graph canvas area.
Connect the activities with the Gateway element using control flows.

For information on how to connect activities, refer to Creating Process Flow.
To add a condition, right-click the control flow and select View Properties. The properties of the control flow are displayed in the Properties Panel in the Bottom Pane.
Click Edit Condition from the Properties Panel.
On the Condition Wizard window, click Process Flow Variable Condition and click Next.
Click Activity Attributes Condition and click Next.

On the Activity Attributes window, select the activity attributes and click Done.

Field Name	Description
Existing Activities	List of activities of the process flow.
Activity Attributes	Activities of the selected activity.
Operands Type	Data types of the value contained by the above-specified attribute. 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.
Operators	Operator to be applied to the activity attribute. The supported operators are "=", "! =", ">", "<", ">=", "<=".
Value	Value of the above-specified attribute.
Decimal Precision	Applicable only if the Operands Type is Decimal.

Repeat the steps to add a condition on another control flow.

Adding Condition Using Process Flow Variable Other Condition

The transition will execute using Process Flow variable if the value of a specified variable is equal to the defined value.

Prerequisites

Ensure that you have created a Process Flow variable.

To add a Condition in a process flow using other condition:

In the Process Designer, in the Palette View panel, select Gateway ( ) element and drag it in the Graph canvas area.
Connect the activities with the Gateway element using uncontrolled or default control flow.

For information on how to connect activities, refer to Creating Process Flow.
To add a condition, right-click the control flow and select View Properties. The properties of the control flow are displayed in the Properties Panel in the Bottom Pane.
Click Edit Condition from the Properties Panel.
On the Condition Wizard window, click Process Flow Variable Condition and click Next.
Click Other Condition and click Next.

On the Other Condition window, select the value in the fields and click Done.

Field Name	Description
Name	Name of the process flow variable.
Operands Type	Data types of the value contained by the above-specified attribute. 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.
Operators	Operator to be applied to the activity attribute. The supported operators are "=", "! =", ">", "<", ">=", "<=".
Value	Value of the above-specified attribute.
Decimal Precision	Applicable only if the Operands Type is Decimal.

Repeat the steps to add a condition on another control flow.

Java Condition

A transition may have a condition that can be either in the form of script or Custom APIs. Once the condition is met, the transition takes place. Java Condition is a part of the transition.

The sample conditional transition is given below:

<transition
from="state.2" to="state.4">
           <guard>
              <indigo:scripted-guard>
                  <![CDATA[
                                    ..script 
                        ]]>
              </indigo:scripted-guard>
           </guard>
</transition>

A State in Process XML either has a normal transition(s) and/or conditional transition(s). If there is more than one transition from a State, only one transition takes place at a time and it depends upon the order of their occurrence and condition satisfaction (in case of conditional transition). A conditional transition takes place based on an appropriate condition defined in the form of Java code. When the condition is met, the transition takes place. A Condition is satisfied when Java code script returns true. The Java code script should return true or false otherwise an exception is raised.

A transition may have a condition in the form of Custom APIs. If you want to use Custom APIs in the Java Condition, first create a class with method(s) and put them in the .../<AdeptiaInstallFolder>/ServerKernel/customClasses/<ClassPackage> folder where <ClassPackage> is the package where you have defined the Java class.

For example, if you have defined the Java class in the org.custom package then first create the org/custom folder in the .../<AdeptiaInstallFolder>/ServerKernel/customClasses folder and put the class in the custom folder. Ensure that:

The class must implement ConditionExecutor interface.

public class <classname> implements ConditionExecutor

The method should accept only one parameter and that must have an object of ExecutionEvent.
```
public boolean <methodname> (ExecutionEvent event) throws Exception 
```
The method must be public.

Adding Condition Using Java Condition

To add a Condition in a process flow using Java condition:

In the Process Designer, in the Palette View panel, select Gateway ( ) element and drag it in the Graph Canvas area.
Connect the activities with the Gateway element using uncontrolled or default control flow.

For information on how to connect activities, refer to Creating Process Flow.
To add a condition, right-click the control flow and select View Properties. The properties of the control flow are displayed in the Properties Panel in the Bottom Pane.
Click Edit Condition from the Properties Panel.
On the Condition Wizard window, click Java Condition and click Next.

On the Java Condition window, select the interpreter type.

Interpreter Type

Description

Script

In this option, you need to define the Java code for the execution of the process flow. Using this option will decrease the execution performance of the process flow.

Custom API

It is recommended to use this option. Using this option will increase the execution performance of the process flow. In this option, you need to select the class and its method for the execution of the process flow. The process flow will be executed on the basis of the code implemented in the selected method.

Repeat the steps to add a condition on another control flow.

Expression Condition

A transition may have a condition based on an expression. This expression is built using the Activity Attributes or the process flow variable with 'AND' & 'OR' condition.

Adding Condition Using Expression Builder
You can generate an expression using Activity Attributes or Process Flow variables or 'AND' or 'OR' conditions.

To add a Condition in a process flow using Expression Builder:

In the Process Designer, in the Palette View panel, select Gateway ( ) element and drag it in the Graph canvas area.
Connect the activities with the Gateway element using uncontrolled or default control flow.

For information on how to connect activities, refer to Creating Process Flow.
To add a condition, right-click the control flow and select View Properties. The properties of the control flow are displayed in the Properties Panel in the Bottom Pane.
Click Edit Condition from the Properties Panel.
On the Condition Wizard window, click Expression Condition and click Next.
For defining expressions you need to define rules. A rule supports multiple expressions. You can link the multiple expressions using the rule operator. On the Condition Wizard window, click .

On the Rule Information window, provide the details of the rule.

Field Name	Description
Rule 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 Create Expression to insert the defined condition (comprising of activity attribute or process flow variable) into the Expression text area, displayed at the bottom of the window.
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 Select Operator drop-down list. This drop-down is populated with values of && (AND) and || (OR).
Click Insert Operator 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 the control to the Condition Wizard 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 .

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 Done. This closes the Condition Wizard window and returns to the Graph Canvas.
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.

Browser not supported