What’s New

23.4.2

Available February 8, 2024

• The city code XAI (Chongoene Airport) was added to the travel data file, which will ensure that robotic ticketing can take place for bookings having this city code.

• The option to “add new” records for Distribute PNRs evenly and Move Unticketed PNRs handlers has been reinstated as part of a defect fix.

23.4

Available December 2, 2023

• When the option Show action runs containing processed PNRs is checked, only the action runs where PNRs are processed through the criteria are displayed.

• Filters applied to the Users page are automatically retained. To remove applied filters, select the Remove Filter(s) button.

• The password policy has been strengthened.

23.3

Available October 15, 2023

• Schedule change handler can handle more complex scenarios.

• Email field in the Actions page allows a wider variety of special characters.

• Security improvements are included.

• The city code DRP has been added to the travel data reference library to allow robotic ticketing for air segments having DRP as city code.

23.2

Available July 15, 2023

• The PNR tracker report allows users to access all PNRs processed by Queue Control Console, including the ones when there are system exception errors, allowing users to track PNRs easily.

• In the schedules list, sort columns by clicking on the headers for agency, name, frequency, and active.

• Additional criteria fields have been added, such as vendor locator, frequent flier number, operating carrier, booking class, itinerary remarks, client file, and owning PCC. These fields allow users to filter out bookings without needing to write queries. Important: These criteria attributes apply to Travelport+ only.

• Email formats in the Failure email recipient field are validated in the action page so that incorrect email IDs are caught before the execution of the action, saving time in correcting the errors later.

• The removal of the passenger’s name in the predefined place from the email body gives the user the flexibility to configure the passenger’s name anywhere in the email body using the extraction capability.

• Static and dynamic code security vulnerabilities have been fixed.

23.1

Available March 25, 2023

• In the schedule change handlerConfiguration for Customers and Configuration for Consultants sections, you can extract attributes from the booking file to send customised or personalized messages to the individual traveler.

• The options to inherit matched and unmatched PNRs from the last action offers more flexibility to users to manage the consultant's workflow and provide better automation and time savings.

• The schedule change handler has been enhanced to fix a defect with the email notification to customers when there is an UN segment without TK segment in the itinerary. Other changes ensure the handler is more robust to handle some complex scenarios, such as when direct and indirect flights have more than one segment with a major general change.

22.5

Available December 3, 2022

• Fares can be refiled based on a specific plating carrier using historical fares through Advanced Robotic Ticketing handler. This feature helps bridge any minute fare differences compared to the option of refiling with the current fares.

• Fares can be refiled without ticketing as part of advanced robotic ticketing. This option lets you ensure that any expired fares are refiled.

• Information can be extracted from the booking file while sending emails through the Send Email handler. This option is useful for agencies wishing to send personalized messages to the traveler.

• Two defects were fixed related to the Schedule Change handler.

  • Some schedule changes related to major/minor time changes were mistakenly getting identified as indirect flight changes.

  • The system was not able to identify the schedule change times when the flight times were displayed in AM/PM format as opposed to the 24-hour format.

22.4

Available October 29, 2022

• Fares can be refiled before ticketing based on a specific carrier. This options provides more flexibility for ticketing agencies that are directly affiliated to a carrier.
  Note: This option is only available for Travelport+ (1G).

• In the Monitoring Queues section, a new option to continue with ticketing if matching record is not available in the TMU table for the booking file allows the agency more flexibility in configuring their robotic ticketing handler.

• The schedule change functionality was enhanced:

  • In the queue configuration section, specify a queue for direct to indirect flight changes.

  • In the configuration for customers and consultants sections, the Major General tab now includes Indirect Flight Changes. Email notifications now include old and new flight information related to the specific direct to indirect flight change.

  • In the configuration for customers and consultants sections, a Cancelled Segment Changes tab has been added.

  • Booking files that do not meet the minimum connection time criteria for any major general, major time, and minor time schedule changes are now moved to the queue for invalid connections, which is specified in the queue configuration section.

• Next scheduled run times display in the time zone selected for the logged in user instead of GMT.

• Two defects were fixed:

  • Schedule filters and access methods were not cleared after logging out.

  • Queue manager migration wizard was set to No when the agency admin saved the agency.

22.3

Available September 10, 2022

• This release contains critical and high security code vulnerability fixes, as well as some bug fixes.

22.2

Available July 9, 2022

• Schedule Change handler supports schedule changes related to cancellation of segments when the airline has accepted the TK segments. This change applies to Travelport+ bookings only. This ability ensures that these kinds of flight cancellations are not skipped, and timely notifications of these schedule changes can happen.

• Any booking files in the Schedule Change Monitoring Queue that do not have any schedule changes are sent to the manual queue for the attention of consultants.

• The Retention handler allows Travelport+ bookings to be retained for a maximum of 338 days.

• The Advanced Robotic Ticketing handler accepts multiple email IDs.

• The Activity Report has been renamed to Robotic Ticketing Bookings.

• When configuring actions, any inactive access methods are indicated in red.

• There also has been some minor security enhancements to address code vulnerabilities.

22.1

Available April 9, 2022

• The Super Agency Admin role is an agency administrator role for managing multiple agencies that belong to an agency group.

• A user profile menu provides access to the user's email, password change, language, and time zone preferences.

• New option to activate/deactivate schedules, actions, and users.

• When creating criteria, any syntax errors are highlighted when the user saves, which means that errors are caught before run time.

• Some security enhancements have also been included in this release, including “IP” logging for audit logs.

21.3

Available November 20, 2021

• The schedule change handler for the customer configuration can include itinerary changes in the email notification and provides a BCC option for emails sent to the traveler.

• Criteria engine lets you select new attributes (ticket designator, PTC code, and fare basis) from the filed fare.

• When a commission Excel file is imported, errors display on a single screen and includes suggestions for correcting the errors.

21.2

Available September 18, 2021

• Two new tabs were added to the schedule change handler:

  • Configuration for Consultants tab is used to specify the content of the email to be sent to consultants to notify them of a flight cancellation.

  • Advanced Schedule Change Configuration tab is used to define how schedule change times are computed (that is, departure time, arrival time, or both). By default, schedule change times are computed based on both arrival and departure times separately, and the greater value is used for minor and major changes. There is also an additional option to indicate the basis on which a schedule change would be accepted.

• Improvements were made to application security.

21.1

Available April 10, 2021

• Queue Control Console was rebranded with the new Travelport logo and colors.

• Grid pages were changed for ease of navigation when a filter is applied.

• Extractions can be used for actions that do not use monitoring queues.

• Prior to this release, audit logs had a 7-day restriction. With this release, you can filter audit logs for any date range.

• The datetime label in criteria interface was removed.

20.2

Available December 12, 2020

• Updates to password security requirements. Programmatic passwords are created with at least 17 characters.

20.1

Available July 11, 2020

• The Inherit PNR functionality has been enhanced, which will lead to faster schedule turnaround times, especially when configuring multiple actions with same monitoring queues.

• The Queues functionality has been updated to reflect the inherit PNR options.

• Export a schedule's actions and handlers using the Download Actions report to quickly review a workflow setup.

• In Agency details, the country name is selectable via a drop-down list to help streamline the recording of accurate and consistent country names for improved reporting.

• Prior to this release, when the AAT table was configured for type 41 (eticket enabled), QCC returned an error while validating the printer linkage and did not continue to ticket both in ticketing handler and Advanced robotic ticketing handler. This issue has been resolved and ticketing will now proceed with both handlers.

19.2

Available October 19, 2019

This release focused on improved security, usability, and accessibility.

• Passwords for Custom handlers are encrypted within the XML definition.

• Track PNRs across agency schedules for agency users.

• Agency users have access to audit logs.

• An active schedule can be run on demand directly from the Schedule Details page.

• Ability to filter on action name column in Schedule Action list grid.

• Ability to see PNRs processed by Distribute PNRs evenly in the Processed PNRs report.

• Better error handling when extractions are used in Cryptic command handler.

• Fixing the incorrect notification due to AM/PM issue with schedule change handler.

• Availability of EMD issuance handler applicable for 1G cores for all customers.

19.1.1

Available June 8, 2019

• Schedule reports enhanced to include:

  • Track PNRs across schedules and actions for a selected date range.

  • List the PNRs processed across the schedules and actions for a selected date.

• Refile fares using historical fares without checking if current fares are available on refiling, if required, and the option to skip the fare tolerance check when refiling using historical fares. Customers can skip the fare tolerance check if they choose to accept the risk of potential ADMs whilst refiling historical fares.

• Refile expired fares based on the stored fare status of “X” in addition to the existing logic of checking if the “last date to purchase ticket” is the past.

18.2

Available October 2018

• When ticketing occurs months after a fare is filed, the fare may no longer be available. You can now ticket based on a historical fare using current or historical taxes. Changes were made to the Advanced Robotic Ticketing screen to accommodate ticketing of historical fares. Automating ticketing based on historical fares and manual adjustments of historical tax codes saves customers substantial time and effort.

• Current or historical taxes can be amended if they are within specified tolerance limits.

• Customers can be provisioned for an EMD issuance handler (for Galileo and Apollo), which provides the following options:

  • Configure the issuance of EMS-S, EMD-A, or both

  • Specify a form of payment or let the system use the form of payment of the PNR

  • Queue PNRs without EMDs to a specific queue

  • Specify the queue where PNRs are moved when EMD issuance is successful

  • Specify the queue where PNRs are moved when EMD issuance has failed

  • Specify multiple email IDs to which a notification of EMD failure is sent

18.1

Available 02 June 2018

• For Activity reports (Advanced Robotic Ticketing users only), users can select the Agency and month for the report. Data can then be filtered using your spreadsheet application.

• Action detail log files can be downloaded to a text file for easier searching of errors and PNRs.

17.12

Available 2 February 2018

For Schedule Actions, a new Do not refresh PNR for applying criteria option is available when the option to Inherit PNRs from previous action in this schedule is selected. By selecting the Do not refresh option, the PNRs that are inherited will not be retrieved again in the action, which improves performance by avoiding extra retrievals.

17.7

Available 02 August 2017

More stringent passwords are required.

• Passwords have increased to a minimum of 7 characters, including at least one number, both upper and lower case letters, and a special character. 

• Passwords expire every 90 days.

17.2.2

Available 25 May 2017

Ticket modifier configuration functionality in the current release:

• For Advanced Robotic Ticketing, ticket modifiers can be applied based on the PNR, filed fare, and configuration in the ticket modifier table.

• In Advanced Robotic Ticketing configuration, a ticket modifier can be configured for each monitoring queue/PCC.

• Agency administrator can centrally maintain (add/delete/update) the ticket modifier configuration table(s).

• The ticket modifiers configuration table settings can be exported/imported by the agency administrator.

17.2.1

The 17.2.1 release loaded on 14 February 2017.

Advanced robotic ticketing handler includes a limit to the number of times a PNR is placed onto the future queue. If the PNR has reached the specified queue placement limit, Travelport Queue Control Console (QCC) continues with the advanced robotic ticketing without any further future queue placement.

16.0

The 16.0 release loaded on 3 October 2016.

• Advanced robotic ticketing handler enhanced to monitor multiple monitoring queues. Multiple commissions can be associated with each of the queues. As a result of these enhancements, the "commission configuration" option and "Save configuration across all queues" checkbox have been removed from the Advanced robotic ticketing screen.

• Multiple default commissions, customised default commissions, and agency-specific commissions can be configured using the new Commission Tables option in the Settings tab (available to Agency Administrators). These new commissions options provide flexibility for corporate agencies to configure commissions as per their regional requirements.

  Note: Commission Tables are not available to Worldspan users.

• Basic functionality has been added for Worldspan users, including: Cryptic, Ticketing, Move to Queue, Remove from Queue, End Booking, and Retention Segment similar. Worldspan users can create actions that implement the handlers listed above. Refer to Worldspan Users for more information.

15.7.1

The 15.7.1 release loaded on 15 March 2016.

• Ten additional languages are now supported: Dutch/Netherlands, Finnish, Swedish, Czech, Afrikaans, Hindi (India/UAE), Polish, Korean, Turkish, and Romanian. To select one of these languages, click the language link in the upper right corner of the Queue Control Console screen.
• Schedules and Actions can be copied, which minimises the effort, time, and errors of creating an action or a schedule.
• Queue 0 can be monitored for action, advanced ticketing, and DistributePNRsEvenly handlers.
• The criteria engine includes additional filters like vendor code, regions, and agency customised regions.
• Advanced ticketing enhanced to allow a re-filed fare to be ticketed if the difference in the total amount is within the defined tolerance limit.

December 2015

The 08 December 2015 update added Schedule Changer and Waitlist handlers.

• Schedule changer places booking files with flight segments containing schedule changes on a manual queue. This handler can also be configured to send notification emails to the customer and consultant, based on the type of schedule change.
• Waitlist handler identifies the waitlisted air segments in a booking file and checks if the waitlisted segments are available to be booked. If the waitlisted segments are available, the travel consultants configured within the handler page will be notified by email.

This update caused the following screen changes:

• Schedule Changer and Waitlist handler options added to the Agency page.
• Send email address and Sender display name fields added to the Create Action page to support Schedule Changer.
• Schedule Changer and Waitlist handler configuration pages added.

The Waitlist handler finds all air segments in a PNR for which the segment status is “HL”. The availability for each of these segments for the same origin, destination, departure date, number of seats, and booking class is determined. If seats are available for any segment, the availability of seat information is added to the notification email.