Scheme properties are the settings that define how a scheme interacts with the GDS, handles PNRs, and processes data. Understanding scheme properties is essential to ensure your workflows run smoothly and efficiently. Let’s walk through the key aspects of scheme properties, so you can configure your schemes confidently.
After pressing New Scheme and setting the scheme type, the Scheme properties window will appear. Its look and functionality vary depending on the scheme type and GDS.
First, enter the scheme name. Consider using key words describing your workflow. This will make it easier to navigate through the schemes as they grow in quantity. You can edit the scheme name any time after.
Then, you can enable Test mode. It's a simple run of a PNR, tickets or EMDs through the scheme to test its functionality without altering the object.
The Scheme properties window includes several tabs.
- Main and Error e-mail are compulsory. These tabs are essential for setting up the basic functionality and ensuring you’re notified of any critical issues.
- Description, Error queue, and Warnings are optional but recommended for optimizing your workflows.
Note that the contents of the tabs vary depending on the scheme type and GDS.
This is where you set the core parameters of your scheme.
- GDS: Choose the GDS your scheme will work with. This is the source where your PNRs, tickets, and EMDs will come from.
- Operational PCC/OID: Specify the office where processing will occur. If the office you need is missing from the list, click Manage PCC and add it manually.
- Alternative PCC/OID: A substitution for operational PCC when tickets or EMDs are unavailable in it.
- Priority: Set the scheme’s priority: Urgent, Normal, or Low. For example, ticket issuance schemes should have high priority, while queue processing can be set to low.
- Reservation must be accessible in GDS for ticket (EMD) processing: Enable this setting if the scheme requires access to the PNR data associated with the processed document.
- Use historical flight segment data: Enable this setting if historical segments need to be considered during processing.
In this tab, you can add a general description of the scheme, including its purpose, objectives, and key settings. This will help find the scheme using keywords from the description.
In this tab, you can define where the PNR will be placed in a queue if a processing error occurs. This feature is particularly useful if you prefer working directly in the GDS terminal, as notifications will appear there instead of in your email.
You have two options for specifying the PCC:
- Static: A fixed PCC value will always be used as the target.
- Dynamic: The system will automatically use the PNR owner (also known as the Responsible PCC) as the target.
If the PNR fails to queue, a notification will be sent to the email address specified in the Error e-mail tab. Be sure to monitor your notifications, as they will help you quickly identify and resolve potential issues.
Add an email to receive notifications about fatal errors requiring manual intervention. Be sure to check this email regularly.
Make sure that the sender's domain matches the SMTP server settings:
System Settings → E-mail → E-mail SMTP server settings
We recommend setting a custom sender's name to make it easier to find these emails in your inbox.
This tab helps configure notification settings to monitor the workflow. If an active workflow has no processing activity, it may indicate a system freeze.
Conversely, multiple PNR processing attempts could signal a process loop.
Notifications will be sent to the email addresses specified in the Error e-mail tab.
By carefully setting up the scheme properties, you can minimize potential disruptions and streamline the overall workflow.
- Regularly review scheme settings to ensure they align with your current operational needs
- Monitor notifications to quickly identify and resolve potential issues, such as system freezes or process loops
- Use meaningful names and descriptions for easier navigation and troubleshooting