PNR audit tab

Before the PNR audit tab was available, users were unable to easily view the history of actions that Productivity Automator had executed upon PNRs.

With the introduction of PNR audit, users can search by PNR and access a log of actions executed by Productivity Automator, allowing for more detailed and effective troubleshooting, as well as giving users more transparency into their rules’ behavior.

PNR Audit Search

To search for a PNR to audit:

1. Select a Pseudo City Code from the PCC drop-down list.

2. Enter a Passenger Name Record number in the PNR field.

3. Click Search to display a list of rules that have performed actions against the selected PNR.

   Note: The rule summary modal displays when a rule is selected.

   

4. Select the arrow next to the record locator at the top of the list to see a summary of the PNR’s itinerary.
   

Review the PNR actions

To review the rules that have been run against the PNR:

1. Review the name, date and time of the last action, and status of the associated rules.
   Note: Times display in the local time of the UI web browser, whereas time in the PNR history is UTC (Coordinated Universal Time).

2. Click the View rule button to display a summary in a side modal similar to the rule summary that can be displayed from the Overview tab.
   Note The below message will display in this summary, as PNR audit shows the most recent activity taken by Productivity Automator.
   
   

3. Click the download icon to generate and download a summary PDF for the selected rule.

Audit the PNR

Each rule displays one of the following statuses:

• The Actioned status indicates the rule was run successfully.

• Failed status indicates that the rule attempted to run but encountered problems and stopped processing.

• Not actioned status indicates the rule was not run.

To begin the audit of the PNR:

1. Select a rule to display the history of actions that the rule has run.

   • A rule that has run as expected displays a status of Actioned next to the relevant Matched actions.
     Note In the following example, the rule has run successfully, so the Matched actions were triggered while the Failure handler was not.
     
     

   • If the rule fails, PNR audit displays which action caused the failure, and that the Failure handler was executed.
     

   • The email failure reason feature requires no actions from the user. If a Send Email action fails to execute, the PNR Audit displays the reason for the failure in the Details column.

     

   • If the rule has not been triggered at all, the details of the audit display neither the matched actions, nor the failure handler actions, were executed on the PNR.
     

2. Optionally, to ensure that a single notepad remark at the time of the rule execution is added, (to inform that automation has taken place by Productivity Automator) check the box on the Rule setup page. If this is not selected, no notepad remarks are added by Productivity Automator.
   

3. Conditionally, if the Failure handler for a rule does not include a File finish or Send email action and the PNR extract Failure remark, but the rule includes critical actions (Accept changes, Fares and ticketing, Ticket revalidation), then Productivity Automator asks to include a PNR extract Failure remark. Including this PNR extract ensures that the details of the failure are added to the Notepad remarks via a File finish action, or sent in an email via the Send email action. Click Continue.