Task: Sign out of Queue

This task allows the user to sign out of the Queue they had previously signed into. The user has several options to choose from regarding the disposition of the currently active PNR/Booking File (BF) when signing out of Queue. These options are described in Section 2.

Section 1: Short Answer

Transaction Name:

QueueProcessing_3

Can any other transaction perform this same task?

This is the only transaction available to sign out of Queue.

Can this task be performed in a sessionless environment?

This task can only be performed in a Sessioned environment.

Are the request and response identical on both the Apollo and Galileo systems?

The request and response information is identical on both the Apollo and Galileo systems.

List any industry-specific knowledge required to understand this task.

None.

Explain any special limits or distinct restrictions.

None.

Section 2: Detailed Description

Request:

Unless otherwise specified, use ALL CAPS in any request data.

For a Sign out of Queue request, a <QueueMods> element is required with a <QueueRemoveSignOutMods> sub-element. The <QueueRemoveSignOutMods> must contain one of the action codes for a Sign out of Queue. The possible action codes are:

QX - Sign out of queue and it leave the last viewed PNR or BF available to the user
QXI – Sign out of Queue and ignore the currently Active PNR/BF. This exits the queue without committing any changes to the PNR/BF
QXIR – Sign out of Queue and ignore and re-retrieve the currently active PNR/BF. This exits the queue without committing any changes to the PNR/BF, then redisplays the PNR/BF
QXE – Sign out of Queue and finish (end transact) the currently active PNR/BF. This exits the queue and commits any changes to the PNR/BF
QXER – Sign out of Queue and finish (end transact) and re-retrieve the currently active PNR/BF. This exits the queue, commits any changes to the PNR/BF, then redisplays the PNR/BF

Note: If the action is “QXE” or “QXER”, a received field must also be present in the <QueueRemoveSignOutMods>.

Prerequisite tasks:

The user must first have signed into a Queue in order to sign out of a Queue.

Expected response:

The expected response is dependent on the action code used.

QXI – A <QueueErrText> element is returned with a <TextMsg> sub-element that indicates “IGND” (ignored).
QXIR – A <PNRBFRetrieve> is returned with PNR/BF data, as listed in Section 3. For more information on the <PNRBFRetrieve> see the documentation for the PNRBFManagement transaction.
QXE – An <EndTransaction> element is returned. For more information on the <EndTransaction> see the documentation for the PNRBFEnd transaction.
QXER – A <PNRBFRetrieve> is returned with PNR/BF data as listed in Section 3. For more information on the <PNRBFRetrieve> see the documentation for the PNRBFManagement transaction.

In addition to these exit options, a PNR/BF can also be routed (placed) to a queue. This process is commonly referred to as QEP (queue, end transact, place). XML Select Transactions do not currently support routing. A terminal command must be performed to route a queue.

Error and warning responses:

There should be no error from a Sign out of Queue request. If the action requested is “QXE” or “QXER”, and there are custom check rule validation errors, a <CustomCheckRuleExecute> is returned. The only time the user is still signed into Queue is when the <CustomCheckRuleExecute> is returned.

Follow-on requests:

If the Sign out of Queue action included a re-display of the active PNR/BF, numerous tasks can be performed to manipulate the PNR/BF. Otherwise, there are no follow on requests. For additional information on PNR/BF manipulation tasks see the documentation for the PNRBFManagement transaction.

Section 3: Tables

Request (Input) Tags

<QueueMods>

Terminal Equivalents:

Apollo QXI, QXIR, QXE, QXER

Galileo QXI, QXIR, QXE, QXER

Ordering	KLR	Min/Max	XML Tag
A	QUR2	0 – 1	<QueueRemoveSignOutMods>

Response (Output) Tags

<QueueErrText>

If “QXI” action is requested.

	Ordering	KLR	Min/Max	XML Tag
		TEXT	1 – 1	<TextMsg>

<EndTransaction>

If “QXE” action is requested

	Ordering	NWB	Min/Max	XML Tag
		2031	1 – 1	<EndTransaction>

<CustomCheckRuleExecute>

If “QXE” or “QXER” action is requested and there is a Custom Check Rule Validation error.

	Ordering	KLR	Min/Max	XML Tag
		CCEV	1 – 50	<CCRuleExecute>

<PNRBFRetrieve>

If “QXIR” or QXER” actions are requested and there is no Custom Check Rule Validation error.

Ordering	KLR	Min/Max	XML Tag
A	CTRL	1 – 1	<Control>
B	BP07	0 – 1	<HeaderLine>
C	BP08	0 – 1	<GenPNRInfo>
D	BP09	0 – 1	<PostScript>
E	BP10	0 – 99	<LNameInfo> *See special information in Section 2
F	BP12	0 – 99	<FNameInfo> *See special information in Section 2
G	BP14	0 – 99	<FreqCustInfo>
H	BP16	0 – 99	<PhoneInfo>
I	BP32	0 – 1	<TkArrangement> *See special information in Section 2
I	BP33	0 – 1	<TAUTkArrangement> *See special information in Section 2
I	BP34	0 – 1	<TAWTkArrangement> *See special information in Section 2
I	BP35	0 – 1	<TLTkArrangement> *See special information in Section 2
I	BP36	0 – 1	<TAMTkArrangement> *See special information in Section 2
J	DPP0	0 – 1	<CreditCardFOP> *See special information in Section 2
J	DPP1	0 – 1	<CheckFOP> *See special information in Section 2
J	DPP9	0 – 1	<OtherFOP> *See special information in Section 2
K	BP17	0 – 1	<AddrInfo>
L	BP18	0 – 1	<DeliveryAddrInfo>
M	IT01	0 – 99	<AirSeg> *See special information in Section 2
M	IT02	0 – 99	<AirSegOpAirV> *See special information in Section 2
M	IT16	0 – 99	<AirSegDetail> *See special information in Section 2
M	IT13	0 – 99	<ARNK> *See special information in Section 2
M	IT03	0 – 99	<HtlSeg> *See special information in Section 2
M	IT04	0 – 99	<HtlSegOptFlds> *See special information in Section 2
M	IT05	0 – 99	<CarSeg> *See special information in Section 2
M	IT06	0 – 99	<CarSegOptFlds> *See special information in Section 2
M	IT07	0 – 99	<NonAirSeg> *See special information in Section 2
M	IT09	0 – 99	<DuePaidInfo> *See special information in Section 2 (Galileo core only)
M	IT10	0 – 99	<FlygTaxiSeg> *See special information in Section 2 (Galileo core only)
M	IT11	0 – 99	<TourSeg> *See special information in Section 2
M	IT12	0 – 99	<CruiseSeg> *See special information in Section 2
M	IT14	0 – 99	<TrainSeg> *See special information in Section 2
N	DPR1	0 – 99	<ItinRmk> (Associated Itinerary Remarks)
O	DPR1	0 – 99	<ItinRmk> (Unassociated Itinerary Remarks)
P	ST01	0 – 99	<SeatSeg> *See special information in Section 2
P	ST02	0 – 9801	<SeatAssignment> *See special information in Section 2 (The max number is really unrealistic, but that would be that max with 99 segments, 99 passengers per segment)
Q	BP19	0 – 255	<OSI>
R	BP20	0 – 255	<NonProgramaticSSR> *See special information in Section 2
R	BP21	0 – 255	<ProgramaticSSR> *See special information in Section 2
R	BP22	0 – 255	<ProgramaticSSRText> *See special information in Section 2
S	BP23	0 – 1	<CustID>
T	BP24	0 – 1	<ProfileClientFileAssoc>
U	BP25	0 – 3	<CustomCheckRules>
V	BP26	0 – 255	<GenRmkInfo>
W	BP27	0 – 99	<VndRecLocs> (Galileo core only)
X	BP28	0 – 99	<VndRmk> (Galileo core only)
Y	DPIR	0 – 99	<InvoiceRmk> (such as Canned Remarks)
Z	BP29	0 – 99	<QMinder>
AA	DPIR	0 – 99	<InvoiceRmk>
BB	BP30	0 – 1	<Untranslatable>
CC	BP37	0 – 99	<NameRelatedData>
FF	BP40	0 – 99	<Email>
GG	BP41	0 – 1	<CorporateID>
HH	BP42	0 – 1	<DividedBookingInfo>
II	BP45	0 – 99	<AdditionalID>

Related Samples

QueueProcessing_3_s7

QueueProcessing_3_s11