In Traveller version 6827 a new auto processing mode is introduced, this improves the existing system with an extended and more secure interface.
Client locking - Each individual download can now only be viewed by a single user, this prevents two users trying to access the same download at the same time and helps to organise large lists with many users potentially viewing the queue.
Download Recovery - If a system crash occurs during the download process previously the download could become hidden and would require users to either redownload the booking from the GDS or have Micros|Travel recover the booking. In this scenario downloads can now be seen on the queue and actioned locally.
New Choices - When a booking hits the error queue the user now has the ability to decide what the next step will be, they can process the file there and then, or pass the booking back for the Auto Processor.
Multiple CRS Processors - Previously traveller would be restricted to a single Auto Processor, the new system allows for multiple machines to be running the Auto Processor at the same time thus increasing the rate at which downloads are processed. This also means that each branch in a multi branch dataset can have it's own Auto Processor. The technology behind the new system also enables idle Auto Processors to assist the busier branches. Download processors may be seperated by pseudo city code, and the new system even works with Evolvi.
-
The Auto Processor is a system in Traveller that enables a single machine to automatically process GDS download bookings, this machine will scan the booking for errors, create the consultations and produce the invoices. Any bookings that it can not process are passed the Error Queue, or the CRS Queue as it is known in the new system.
The Error Queue and the CRS Queue are just different views of the same list. In 'Error' mode this list shows all bookings that have failed to auto process for one reason or another. This could be anything from a missing name or payment to an intentional stopping of the bookings auto process ability.
The system has distinct advantages outlined below :
Enabling the new system is simple, in Options / Tools -> Global options there is a CRS / BSP tab (Shown below) the option to switch the Auto Processor is highlighted in RED. This option is only required on a per Dataset basis and will require the reboot of all machines connected to Traveller at the time to take effect.
The CRS Menu will change from this :
To this :
Users below level 4 will see only the highlighted option.
For all intents and purposes the Error Queue and the CRS Queue are identical, this list shows all bookings that have failed to auto process for one reason or another. This could be anything from a missing name or payment to an intentional stopping of the bookings auto process ability. (See EQUE entry)
A few, but the flow is intuitive and simple. Most noticeable are the changes to the Error Queue screens which now give the user the ability to process a booking manually or allow the processor to continue with it. Previously the user had only 1 choice which was to return the booking to the list. The new choice buttons are at the bottom of the CRS Queue correction screen (shown below)
No, the new system is much more robust and will not require user intervention on the Auto Processor machine(s) under normal circumstances.
In the unfortunate circumstance where the booking process is interrupted for whatever reason prior to these changes the booking would no longer be visible on the queue and would be redownloaded from the GDS. The queue processing has been changed so that now the booking will appear on the error queue. In a similar way to the booking being locked because it is being processed any failed bookings will be closed and you will not be able to pick them up until they have been unlocked. Care must be taken when doing this as to implement this feature it has been necessary to show bookings that are correctly being processed. To processes a booking can take a minute or two where there are no problems depending on the options that are chosen so note should be taken of the date/time that a booking was picked off of the queue to begin autoprocessing. Typically if this was more than say 10 minutes ago the booking has probably hit a problem and can be unlocked to the error queue so that corrective actions can take place.
To unlock a booking either double click it, or click the "release" button that appears when a locked booking is selected on the error queue.
Do I need to configure my Pseudo City Codes?
Yes, In order to use the new autoprocessing mode, Pseudo City codes must be configured for all users.
Return
to 6827 Contents
Return
to main
