This article covers how to configure scheme elements, use AND/OR logic, apply inversion, and temporarily disable conditions to create flexible and efficient workflows.
The Conditions element is used to verify specific parameters for a PNR, ticket, or EMD. Represented by a yellow diamond, it determines the next step in a process based on the results of a logical check:
- OK: The condition is met, and the workflow proceeds accordingly
- FAIL: The condition is not met, triggering an alternative path
Since the Conditions element varies depending on the scheme type and GDS, its available checks may differ.
To set up a Condition, double-click the element to open its settings.
Conditions can include multiple checks, which are executed sequentially. They can also be combined or grouped using AND/OR logic:
- AND: The condition is met only if all checks within the group are met.
- OR: The condition is met if at least one of the checks is met.
Example: The system will check the two condition groups sequentially, combined with OR.
If the issuing airline is LO or TK, the condition will exit with OK without evaluating further rules, since OR logic between condition groups means that only one group needs to be satisfied.
If neither airline matches, the system moves to the next condition group, where all conditions must be met (AND logic) to proceed via OK.
Take note of the not Domestic route setting in the example above. This condition is configured using inversion to achieve the opposite of the expected result.
Inversion reverses the outcome of a condition, allowing you to check for the opposite result. For complex conditions, inversion follows these logical rules:
Rule 1:
Inverted condition: Not (A or B) Evaluation: Not A and Not B
Rule 2:
Inverted condition: Not (A and B) Evaluation: Not A or Not B
Example: A condition checks whether the schedule has changed by more than 15 minutes OR the date has changed.
- Without inversion: The condition triggers if either event occurs
- With inversion: The condition triggers only if the schedule change is less than 15 minutes AND the date remains the same
See Conditions to explore compatible scheme types and detailed descriptions.
You can disable a condition without deleting it. Be sure to set how the system will interpret the condition: as true or false.
This is useful when you want to keep a condition for future use.
These elements represent actions through which the system interacts with the GDS and makes changes to the PNR.
In the Toolbar menu, they are displayed in blue. Each element performs a specific function and may include both simple and configurable parameters, accessible by clicking on the element.
Elements may have one or two outputs, depending on the complexity of the action.
If the system is unable to successfully complete the step when interacting with the GDS, it will exit via Error. In this case, the agent should define appropriate follow-up actions in the scheme, such as placing the PNR in a queue for manual review or sending an email notification.
Use these elements only after all necessary checks have been completed using conditions, so that only validated data is processed at this stage.
See GDS usage to explore compatible scheme types and detailed descriptions.
These elements provide additional functionality not related to GDS interaction. They offer the agent extra capabilities within the system, such as redirecting processing to another scheme, sending an email, or assigning a tag.
In the Toolbar menu, they are displayed in light purple.
They may contain either simple or advanced settings, but always have only one output. These elements can be placed anywhere when building a scheme.
See Other elements to explore compatible scheme types and detailed descriptions.
Conditions
- Use AND/OR logic to build precise checks
- Apply inversion when you need to test the opposite of a condition
- Temporarily disable conditions instead of deleting them for easier future modifications
GDS usage
- Place only validated data into GDS actions by running all necessary checks beforehand
- Always plan for error exits (e.g., send email, place PNR in queue) in case the GDS step fails
- Remember that some elements have two outputs: OK and Error — handle both in your scheme logic
Other elements
- Use them to enhance automation (e.g., redirect flows, assign tags, send notifications)
- These elements always have a single output, making them easy to integrate
- Can be placed anywhere in the scheme for added flexibility