PNR Watcher Release Notes

v3.0.6 - Released 31 October 2017

This version is a small release that fixes the following issues

  • Fixed an issue where Pattern matching logic wasn't working in all instances
  • Added a lot more Booking File fields for Apollo T- options

 

v3.0.5 - Released 06 October 2017

This version is a small release that fixes the following issues

  • You can now edit the first item in the Rules Condition screen with an error occurring
  • Deleting rules on a filtered screen now works correctly
  • Clearing the Search/Filter now also clears the text entered for the search

 

v3.0.3 - v3.0.4

These versions were internal / customer specific releases

 

v3.0.2 - Released 23 August 2017

PNR Watcher has been further stabilised with the following bug fixes following the initial release of our new 3.0.0 edition

  • PNR Watcher will no longer cause an error when trying to interpret the 'NumberOf' booking fields
  • The system will no longer duplicate rules when editing older rules to newer rules
  • Renaming a table name will now go through and automatically update any reference to that table name in saved Rules
  • Users will no longer be able to create tables using the same name twice
  • After using a tablename in some rule logic, you will no longer be forced to use Expert mode to edit the rule
  • Added link to our new Version 3.0 user guide documentation

 

v3.0.0 - Released July 2017

PNR Watcher is used on thousands of workstations by agencies wanting to achieve the highest Quality Control standards and ensure their agents are informed and empowered to perform their daily routines. This latest release introduces a whole range of improvements and new functionality as set out below:

 

Introducing TABLES

Tables will make it quicker and easier to maintain rules aimed at validating several values at once.  As an example take the recent announcement of refurbishment to Terminal 7 at JFK airport. This is going to create extra delays whilst clearing security, so your agency might want to write a rule that displays an alert if any of  the airlines that used that terminal or booked.

Previously this was achieved with long winded 'or' statements strung together, such as

PreviouslyOrLogic.png

With the new Tables feature, you can simply create a lookup table with all the values you wish to use

JFKAirlinesTable.png

And then write a rule to compare the AirVendor to the values in the table (note you can also write logic that says if the value is NOT in the table as well)

AirVInTable.png

The resulting logic is now simply displayed as

TableLogicCondition.png

If you ever need to add or remove airlines from the table you can do this without having to edit the rule logic at all.

 

Pattern Matching Logic

If you have ever needed to validate the format of a Cost Centre or DI line in a PNR, this wasn't possible - until now.  PNR Watcher 3.0 introduces the ability to validate any field in the PNR. To create the rule logic, simply select from the new "Matches Pattern" or "Does Not Match Pattern" criteria drop down

PatternMatches.png

This pattern is looking for "Any alpha character exactly 3 times, followed by any digit exactly four times". This uses the Regular Expression format that users are familiar with when creating Rule Triggers and can get quite advanced to enable high levels of validation.  Navitas Solutions support is always on hand to help you build these patterns to ensure you are getting the most out of PNR Watcher 3.0

 

Rule Start/End Dates

Lots of our users want rules that only apply for a certain time period.  PNR Watcher 3.0 now allows you to set a start date and/or end date for the rule to apply.

RulesValidDates.png

This will allow managers to ensure rules are being applied when relevant and to 'pre load' rules and set a date for them to activate and become live.

 

Prompt for User Input

Until now, the actions that PNR Watcher could perform were static, however with PNR Watcher 3.0 we have introduced the ability to interact with the user and prompt them for information required to create specific entries being made in the PNR.  As an example, say your agency needs a DI line in the PNR that details the Cost Centre, Employee Number and Reason Code on one line.  You can now configure the new 'Prompt for Input' action to request the information be entered by the user:

PromptForInput.png

Here, we are asking the user to input the three fields (numbered 0,1 and 2) and then using that data to construct the required DI.FT- line. The prompt shown to the end user looks like the following:

InputDialogPromptForInput.png

Here the user has provided C3455 for the Cost Centre, PT1234 for the Emp Number and a Reason Code of 4.  This entry will be made in the PNR and the Action will be displayed in the normal PNR Watcher Actions and Alerts window

ActionUserInput.png

 

Secret Actions

Several users have wanted the ability to hide the outcome of an action from displaying in the Actions and Alerts window. With PNR Watcher 3.0 you now have the ability to mark an Action as a 'secret action'

HiddenActions.png

If all the required actions undertaken are 'Secret' and there are no Alerts for PNR Watcher to display, then the Action and Alerts window will not even open for the user.

 

Rule Filtering

If you are like a lot of agencies, the power of PNR Watcher leads to lots of rules being created, and sometimes the rules can get lost in the list shown to the administrator.  PNR Watcher 3.0 introduces the ability to perform a search across the rules to help pinpoint relevant rules

RuleFilteringStart.png

By entering in a search term, the system will look through the rules and display any that have the search phrase in either

  • Rule Name
  • Rule Logic
  • Action Text
  • Entry Trigger

So now you can show all the rules you have written against 'account code 89TY' in your database, or rules against 'BA' or rules for Mr Smith.

Note: The rule filtering also works on Tables, Departments and Users as well.

 

Copy Rules

We have heard that many of our users need to create the same rule over and over again and until now have had to re-enter the rule logic repeatedly. In PNR Watcher 3.0, if the new Tables feature doesn't negate the need for some duplicated rules, then you are now able to click the entire rule logic with a single click.

 

Created Date

PNR Watcher will now keep track of when a rule was created and display this on screen (only for new rules created going forward).  This lets administrators know when a rule was introduced and track down emails or requests for 'why does this rule exist' type scenarios.

CreatedDateList.png

The creation date is also shown on the Rule Details tab

CreateDateDetails.png

 

New Booking File Fields

We have introduced a brand new field into the Booking File Fields available when writing rules, FiledFareTrueLastTktDate

LastDatePurchaseTicketList.png

This will allow administrators to write rules validating the actual Last Date To Ticket from the filed fare information as shown in the PNR.

LastDatePurchaseTicket.png

We have also updated all Date fields to include a new 'Day' field which will hold the specific day of the week (Monday, Tuesday etc) for the date.  The allows you to write rules such as 'if last date to ticket is a Saturday, alert user to place on Q10 date earlier' etc.

 

Ability to Copy from the Actions/Alerts window

We have updated the Actions and Alerts window to allow end user to copy text displayed, incase they wish to paste it into other systems or indeed the PNR, for example

CopyFromAlert.png

 

Non reliance on Galileo Desktop

With the ever increasing uptake to Smartpoint over Galileo Desktop, we have done a lot of work to remove reliance on some of the Galileo Desktop infrastructure and API's. PNR Watcher 3.0 is now more compatible with Smartpoint 7.x and above than ever.

 

 

Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk