![]() ![]() 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.If QueuePlace element is added in the request, the Queue Number is mandatory, while the other elements are optional. Queue placement occurs after the complete booking is created. Queue Place can be requested during booking using the QueuePlace element. Important! Category and Date Range must be configured for agencies and other travel providers via GDS Desktop. Note: The date range feature is not enabled for Worldspan (1P) customers. 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: Use the value of from a previous GdsEnterQueueReq or GDSNextOnQueueReq to determine if the Universal Record is present in the queue. When the Pseudo City Code (PCC) is not included, it is determined by Universal API. ![]() PseudoCit圜ode can also be sent in the request, but it is not required. The ProviderCode, ProviderLocatorCode, and TargetBranch must be included in the request. SchemaĪ Queue Place request is made using GdsQueuePlaceReq in GDSQueue, to place a PNR on the queue. Note: This functionality is supported by Galileo (1G), Apollo (1V), and Worldspan (1P). 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. The Queue Place functionality adds a specific booking (PNR) to a queue in the provider system for a specific Pseudo City Code. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |