Triggers

This page provides instructions for the creation of Triggers. This is Step 2 of the rule creation flow. This, along with Unmatched actions, are the only optional steps in the rule creation flow. If you skip this step every single PNR on the queue specified in the previous step will be processed by the rule.

The Triggers page lets you determine the criteria to trigger your rule. You can create a simple trigger with just one criteria in it, or a complex trigger group with multiple criteria. You can also create multiple Trigger groups of various complexity.

If there are multiple criteria in your trigger group you can specify if you want all criteria to match the PNR, or any of the criteria to match the PNR using the AND/OR operator.

Trigger groups execute in the order of priority. Ensure you create the most important Triggers first.

When two or more trigger groups exist, it is possible to rename, delete and move the trigger group in order of importance by using the icons in the trigger group header.

Note: A tooltip displays: "Remember to add your triggers and groups in order of priority. Only one operator is allowed per group and between trigger groups. Subgroups should be used to combine and and or operators."

For an in-depth training guide to building triggers, see Best Practices: Building a Viable Trigger.

To create one or more triggers:

  1. Select an option from the Category drop-down menu. The value selected here dictates the available options in the additional fields that display for you to finalize your criteria creation.

    Criteria Description

    Air Segment

    		Create criteria related to air segment such as airline code, segment status code, departure date, flight number, etc.
    All air segments Create criteria that target all air segments with the same airline or segment status code.
    All car segments Create criteria that target all car segments with the same vendor or status type.
    All hotel segments Create criteria that target all hotel segments with the same hotel or status type.
    All segments Create criteria that target PNRs with the same segment type.

    Booking file

    		Create criteria that target information in the booking file such as Customer ID, SSR Code, Notepad Remarks, etc.

    Car segment

    		Create criteria related to car segment such as City Code, Vendor Code, Base Rate Amount, etc.

    Fares

    		Create criteria that target fares in the booking, e.g., Base Amount, Paper Ticket, etc.

    Form of payment

    		Create criteria that target different forms of payment within the PNR, e.g., Invoice Number, Type of Payment cash, etc.
    Has been ticketed Create criteria that target previously issued tickets details Select options such as Electronic Ticket, Ticket Number, etc.

    Hotel segment

    		Create criteria related to hotel segment such as Property Name, Rate Amount, etc.

    Number of Target

    		Select the number of category to apply the criteria with a count of something. E.g., the number of passengers or number of segments.

    Other segments (passive)

    		Create criteria that target passive segment, e.g., Segment status code.

    Passenger

    		Create criteria that target passenger information such as Name Remark, Passenger Type Code (PTC), etc.
    Quality control Create criteria that quality checks your PNR.

    Schedule change

    		Create criteria to target schedule change scenarios, e.g., Departure Time Change, Flight Cancellation, etc.

    Schedule change - NDC

    Create criteria to target schedule change scenarios, e.g., Departure Time Change, Flight Cancellation, etc., for NDC bookings.

    See Schedule change - NDC notes

    Seat data

    		Create criteria that target seat information, such as Row Number, Seat Code, etc.

    Segment

    		Create criteria that target segment information such as Segment Type or Segment Number.
    Waitlist Create a waitlist segment criteria

  2. Select a subset of the Category in the PNR Field drop-down list.

    Depending on the Category selected, the PNR Field drop-down list displays available options for that particular Category. E.g., if you selected Form of payment category you’d have to choose from the following options: form of payment, free text remark, invoice number, type of payment, type of payment card, type of payment card (card issuer) or type of payment cash..

  3. Select a parameter in the Condition drop-down menu that triggers the Value field based on the selections in the Category and PNR field. For example, if you selected Air Segment in Category, and Air Segment Status Code in the PNR field, you can choose Equal To, and enter HK in the Value field.

  4. Enter an alpha, numeric, or alphanumeric text in the Value field. Some of the Value fields accept multi-selection, and you can choose Select all to select all the values.

    • If Time period is selected in the Operator drop-down, the Value field counts forward from the current date. For example, a value of 7 would include the week including and following the current date, and a value of 0 would target only the current date, e.g., "today."

  5. Optionally click either the Add Criteria button to add an additional criteria to your Trigger group, or, click the Sub group button to add additional mixed operators in trigger logic.

    Add Criteria

    When adding multiple criteria lines, select And or Or operator between the lines.

    • Select And if all criteria lines must match before the associate action is performed.

    • Select Or if only at least one line must match.

    • Only one operator can be selected for each trigger group.

    • Lines are labeled alphabetically as they are added.

    Notes:

    • In the Schedule Change category, the Rerouting change trigger allows users to create a rule targeting routing changes; specifically, a scenario in which the origin and destination remain the same but any intermediary segments are changed, removed, or added. This trigger targets pending rerouting changes, not confirmed changes.

    • When adding segment categories to criteria lines, the "Match to the same segment on the PNR" checkbox displays. This allows for logic that targets the same segment on the PNR. For example, a rule could target a single segment and look to match on both the airline and the status code.

    Sub group

    Trigger sub groups can be added to facilitate the mixing of operators.

    After entering at least one criteria line in a trigger group, the option to add a sub group becomes active.

    Sub groups act as a secondary level within a trigger group. Sub groups behave the same as normal trigger groups; the user will add criteria lines and select a single operator to use within the sub group.

    However, the operator selected within the sub group may differ from the operator in the main trigger group.

    In the following example, the main group with line A links to the sub group with And, while lines B and C within the sub group are linked by Or. As per the new trigger group summary, this results in the expression A and (B or C), and Productivity Automator will now execute the associated Action 1 in one of two scenarios – when A and B are true or when A and C are true.

    Overall, sub groups allow you to create trigger groups with more complex logic but must contain at least two criteria.


  6. If at least two criteria from the same category are added to one Trigger group, the Match drop-down displays towards the top of the group box. Select Any or All.

    • Any indicates that if any of the criteria are met, the rule triggers.

    • All indicates that all of the trigger criteria must be met in order for the rule to trigger.

  7. Expand the Summary section to ensure your values and selections are correct. As the trigger logic is built, the Summary section is filled in to demonstrate the logic in a single expression — and show which action the logic will be tied to

  8. Optionally, click the Trigger Group button to create a new Trigger group. Trigger groups can contain one or more criteria. Repeat steps 1-7 if necessary.

    Notes: The same operators (And, Or) are available between trigger groups with the same logic.

    • If Or is selected in the drop-down above, if matched, stop here check box displays in all but the last Trigger groups in the right bottom corner of the trigger group box. If the check box is selected for a certain trigger group and if a PNR matches the criteria in this Trigger group, Productivity Automator will not process the remaining Triggers.

    • You can check if matched, stop here on multiple Trigger groups. For example:

      • A rule has 3 Trigger groups.

      • Triggers 1 and 2 have if matched, stop here check box ticked.

        • During execution, one PNR matched Trigger group 1.

        • Since it matched, stop here was selected and the PNR matched to the criteria, the rule will not continue to check if Triggers 2 and 3 also matched.

      • The second PNR matched the Trigger group 2.

        • The rule checked if the PNR is a match for Trigger 1 and since it wasn’t a match, it checked Trigger 2.

        • PNR matched Trigger 2.

        • If matched, stop here was selected on that Trigger so the rule will not continue to check if Trigger 3 is a match.

    • If you wish for multiple trigger groups to match, then leave the If matched, stop here unchecked. This means that if groups 1 and 3 both match then the actions associated with both trigger groups are processed.

After NDC bookings have been synced and moved to the desired queue from Queue 11 for actioning, the user should set up a second rule to designate those actions.

The category "Schedule change - NDC" is available, and works similarly to the existing "Schedule change" category. It can be used to target NDC bookings that encounter different types of schedule updates, including airline changes, arrival/departure time changes, class changes, and date changes.

This second rule should target that desired queue with every type of schedule change that the user wishes to account for. For example, the user could set up a different action for bookings with an Arrival/Departure time change of greater than 30 minutes, a second action for bookings with a Date change, and third action for bookings with an Arrival/Departure time change of fewer than 30 minutes.

Test Triggers

If you create 1 or more Trigger groups, you can test them before the rule goes live.

  1. Click the Test Triggers button at the bottom of the Triggers page.

  2. Review the Test Triggers pop-up window that displays.

  3. Select options for Productivity Automator, which checks the PNRs on the queue specified on the Setup page.

  • If you configured the rule to target 1 PCC, that PCC automatically displays in the Target PCC drop-down, and the selection is grayed-out.

  • If you target multiple PCCs, you can select 1 PCC at a time from the Target PCC drop-down.

  • You can test all PNRs on the queue if you leave PNR (optional) field empty. Enter PNR in the PNR (optional) field to test a specific PNR.

  • You can test your PNRs against all the trigger groups or just one of them, depending on the selection you made in the Trigger group drop down.

  1. Click the Test button to display results. Matched and unmatched PNRs are listed per every Trigger group.

  2. Click Return to triggersto dismiss the Test Triggers pop-up.

  • If there are no PNRs matching the criteria, a message, ‘No results found, try again' displays.

  1. Click Next to display the Matched Actions screen.