The Queue Place functionality adds a specific booking (PNR) to a queue in the provider system for a specific Pseudo City Code. If a Universal Record (UR) does not exist for the PNR, it is placed in the queue anyway, but PNR Import is not completed for the UR database.
Note: This functionality is supported by Galileo (1G), Apollo (1V), and Worldspan (1P).
Schema
Located in GDSQueue.xsd:
- GdsQueuePlaceReq
- GdsQueuePlaceRsp
Request
A Queue Place request is made using GdsQueuePlaceReq in GDSQueue, to place a PNR on the queue.
The ProviderCode, ProviderLocatorCode, and TargetBranch must be included in the request. PseudoCityCode can also be sent in the request, but it is not required. When the Pseudo City Code (PCC) is not included, it is determined by Universal API.
Use the value of @QueueSessionToken from a previous GdsEnterQueueReq or GDSNextOnQueueReq to determine if the Universal Record is present in the queue.
The QueueSelector/QueueNumber attribute, as well as the other attributes in QueueSelector are optional, however a Date Range can only be included in the request if there is a category in the request:
- Category
- DateRange
Note: The date range feature is not enabled for Worldspan (1P) customers.
Important! Category and Date Range must be configured for agencies and other travel providers via GDS Desktop.
Queue Place during Create
Queue Place can be requested during booking using the QueuePlace element. Queue placement occurs after the complete booking is created. This is applicable to:
-
Air Create Reservation Request
-
Vehicle Create Reservation Request
-
Hotel Create Reservation Request
-
Passive Create Reservation Request
If QueuePlace element is added in the request, the Queue Number is mandatory, while the other elements are optional. If Queue placement:
- Succeeds, a message is returned: Booking successfully placed on Queue […] Category[…] for Pseudo City […]”.Category […] is optional and will be present if provided in the request.
- Fails, a warning is returned. A Queue Place failure does not impact Universal Record creation.
If Queue Place is successful, Universal API creates the Universal Record and updates Queue Information in the Universal Record History.
Response
The response redisplays the booking that was placed on queue, includes an indicator that the transaction was ended by a Queue method, and provides an information message that the booking was successfully placed on the Queue.
At the same time, Universal API updates the cache time stamp as an interaction so that the customer does not get timed out.
Exceptions
In Worldspan (1P):
- When you enter the queue number, a list displays in the response, starting at with the first item in the queue.
- You cannot specify a place in the queue.
ACH does not support queues.
Feedback / Support
