InformationCustom Check

Custom Check Coordinator

Custom Check lets you build rules that can be attached to PNRs to perform quality control checks. With Custom Check you determine the edits that Apollo performs on your PNRs.

	Build rules for new or existing records
	Display rule records
	Copy and rename rule records
	Delete rule records
	Attach rule records to a PNR
	Execute a rule record
	Suspend a rule record
	Cancel a rule record
	Basic Steps to Build a Rule
	Example Rules
	Conditional Logic Outcome Chart
	Message Connector Chart

Build Rule	RULBLD
To Build a Rule	Enter:
Into a new or existing rule record	RULBLD/ACME/IF EW ANDFOR…
For a branch pseudo	RULBLDGK5/ACME/IF EW ANDFOR…
After rule 3	RULBLD/ACME/3/IF TM ANDFOR..

Display Rule Records	RUL*
To Display:	Enter
Rule attached to the PNR	RUL*
List of rule records	*RULLIST**
List of rules within a rule record for a branch pseudo	*RULGK5/ACME**
List of rules beginning with rule number 5	*RUL/ACME/5**

Display Rule Records while in Build Mode
To Display:	Enter:
An attached rule record	*RUL-B**
Rules for a specific rule record	*RUL/ACME-B**
Rules beginning with rule number 5	RUL/ACME5-B

Display Rule Records while in Change Mode
To Display:	Enter:
An attached rule record	*RUL-C**
Rules for a specific rule record	*RUL/ACME-C**
Rules beginning with rule number 5	*RUL/ACME/5-C**
Rule record for a basic pseudo beginning with rule number 5	*RULGK5/ACME/5-C**

Copy and Rename Rule Record	RULCOPY
To Copy and Rename:	Enter:
Rule record (e.g. from ACE to Train)	RULCOPY/ACE+/TRAIN
Rule record to a branch pseudo	RULCOPYGH1/ACME+GK5/TRAIN

Delete a Rule Record	RULDEL
To Delete:	Enter:
A single rule (4)	RULDDEL/ACME/4
All rules and rule record	RULDEL/ACME/ALL
All rules and rule record for a branch pseudo	RULDELGK5/ACME/ALL

Attach a Rule Record	RULA
Note: If the attach format is in a PRO-file, the rule record attaches to the PNR when you move the PRO-file.
To Attach Rule Record:	Enter:
To a PNR	RULA/ACME
To a PNR for a branch pseudo	RULAGK5/ACME

Execute a Rule Record	RULE
To Execute a Rule Record	Enter:
Programmatically	ER, HB;, QEP, Etc.
Manually	RULE
Suspend a Rule Record	RULS

Suspend a rule record	RULS
To:	Enter:
Suspend a rule record	RULS
Activate a suspended rule record	RULA
Note: You cannot ticket with a suspended rule record.

Cancel a Rule Record	RULX
To:	Enter:
Cancel a rule record	RULX
Attach a cancelled rule record	RULA/ACME

Back to Top

Basic Steps to Build a Rule

Each rule may have up to ten components. All components are required except the search function component.

To help you build rules, refer to the ten steps below. Descriptions of the rule components and examples follow these procedures.

Start the rule by typing the start of rule component (IF).
Choose the appropriate enforcement component (EW, EM, or TM).
Choose the appropriate PNR connector component (ANDFOR, ORFOR, ANDNOTFOR, or ORNOTFOR).
Select the appropriate PNR field (N:, P:, F-, D-, T-, W-, C-, T:, T:Z, T:S/, ATX, ITN, OPN, or TUR).
Choose the appropriate data type connector component (AND, OR, ANDNOT, or ORNOT).
If necessary, select a search function component (FIND, FINACT, FINDBR, FINDIC, FINDAAC, OCCURS).
Select the appropriate data type component (ALPHA3, NUM5, SYM2, ALPHANUM6, ALPHASYM2, NUMSYM1, EDD, LIT/*/, VAR4, or TIMES1).
Select the appropriate data type qualifier component (literal, minimum length range, absolute position, or relative position).
Choose a message connector component (THEN SAY or THEN DONT SAY)
Create the message text (freeform text).

Note: You can include SOMs and tab stops in the freeform text.

	To create a SOM, type :*. (colon, asterisks)
	To create a tab stop, type :-. (colon, dash)

Example Rules

The following rule checks for the presence of an address field in the PNR:

IF EM ANFOR W- AND VAR1 THEN DONT SAY PLEASE ENTER AN ADDRESS

The following rule checks for the presence of cash in the form-of-payment field:

IF TM ANDFOR F- AND LIT/S/ THEN SAY PLEASE ENTER ANOTHER FORM OF PAYMENT…CASH IS NOT ALLOWED

The following rule checks for the presence of a correct name field remark in the PNR:

IF EM ANDFOR N: AND FINLIT/*0-/ AND ALPHA3 THEN DONT SAY PLEASE CORRECT NAME FIELD REMARK…NEED *)-ABC

Back to Top

Component/Command List

Component	Command	Descriptions
Start of rule (Mandatory)	IF	Begins each rule
Enforcement level (Mandatory)	EW EM TM	End warning End mandatory Ticket mandatory
PNR field connector (Mandatory)	ANDFOR ANDNOTFOR ORFOR ORNOTFOR	Presence of a field Absence of a field Presence of a field, use with ANDFOR or ANDNOTFOR
PNR field (Mandatory)	PNR field	Actual PNR field identifiers(s)
Data type connector (Mandatory)	AND ANDNOT OR ORNOT	Presence of data Absence of data Presence of data, use with ANDFOR AND ANDNOTFOR Absence of data, use with ANDFOR OR ANDNOTFOR
Search function (Optional)	FIND FINDAAC FINDACT FINDCIT FINDNBR OCCURS (use with times)	Searches for data Find action code Find vendor code Find city code Find number in party Find multiple occurrences
Data type (Mandatory)	ALPHA3 NUM5 SYM2 ALPHANUM6 ALPHASYM2 NUMSYM1 EOD *LIT// VAR4 TIMES1**	Alphas Numbers Symbols Alphas and numbers Alphas and symbols Numbers and symbols End of data Literal Variable data Times of occurrence
Data type qualifier (Mandatory except with data type EOD)	Literal Minimum length Range Absolute position Relative position	Specified data, enclose in slashes (e.g. /DS-/) Minimum number of data (e.g. ALPHA3) Range number of data (e.g. NUM305) Specific position (e.g. n3) Position relative to number (e.g. +4)
Message Connector (Mandatory)	Freeformtext	Actual message text

Conditional Logic Outcome Chart

AND	OR
True AND false = False	True OR False =True
True AND True - True	True OR True =True
False AND False = False	False OR False = False

Message Connector Chart

Rule Outcome/Message Connector	True	False
THEN DONT SAY	Does not display	Displays
THEN SAY	Displays	Does not display

Site Menu / Up One Level / Search / FAQ / Top / Your Feedback