XOR branching is always tied to conditions. These conditions are defined in the Event element and checked during process execution. The result determines which of the predetermined process branches is chosen. The XOR branching recognizes two results per condition: Either the defined condition is fulfilled or it is not fulfilled.

Conditions are defined in the element Event, therefore pay attention to the following during modeling:

Defining Conditions

The ACME procurement process requires employees to complete a Procurement Request in order to react to a demand.

The amount in Order Value determines the next process steps:

• If the demand remains in the credit limit (<= 50), the process continues to the process step Sending confirmation.
  
  
• If the demand exceeds 50 Dollar, the event Credit limit exceeded (>50) comes into effect, triggering the next process step Informing Approver.

Each branch following the XOR connector requires its own event. In the element option you have to enter the corresponding condition referring to and verifying the field's value in the data container.

Verification Credit limit adhered

Verification Credit limit exceeded

Designers can assign a Field Name in Container to form fields, that varies from the field's actual name (see page The Container Principle for further details). However make sure to use the Field Name in Container when defining the condition, since during the event verification the value in the data container will be used.

Example: The Field Name in Container procurementValue is assigned to the input field Order Value

Accordingly the conditions refer to procurementValue, the Field Name in Container:

The conditions need to be defined to cover all possible events. In our example is not only verified if the Order Value is larger or smaller than 50 $, but also covers the possibility that the amount equals 50 $. Therefore all possible values are covered.

Expert Advice

Use the Button Function After Click to generate variables for the event verification. 

Example: Creation of variable approved

	Insert the buttons Reject and Approve to your form.
	Set the Reject button's variable approved to 'no' in the Function: After Click : container.save('approved', 'no');
	The function of button Approve is used to set  approved to "yes": container.save('approved', 'yes');

Now check in the events for the variable approved :

Conditions: Syntax

In a condition verification Logical Operators are used. The placeholder needs to be encased in single quotation marks. The placeholder is the value to be referenced (= Name or Field Name in Container of the form field). String comparisons are always encased in double quotation marks.

Example:

Conditons: Special Cases 

Some form fields have special characteristics, that need to be considered when checking conditions.

	Drop-down Field The values of a Drop-down Field are always saved as value pair value/label. When checking the values of a Drop-down Field, you always need to specify if you are looking for the value entry or the label entry. Additional informations can be found on page Possible Values: Value and Label.
	Checkbox A Checkbox can only assume two values: true and false (boolean values): If the checkbox is activated, then the value saved in the container is true. If it remains unchecked, then the value in the data container is false. Example: Check for the MyBox checkbox' value Checkbox MyBox was activated Checkbox  MyBox was not activated 'MyBox' === true 'MyBox' === false 'MyBox' !== false 'MyBox' !== true
	Radio Button Analog to the Drop-down Field, the value of a Radio Button is also saved as value pair value/label. When checking for the values of a Radio Button you therefore always need to specify whether you are searching for the value or the label. Additional informations can be found on page Possible Values: Value and Label.

Logical Operators

Find an overview of commonly used logical operators below: