This is an old revision of the document!
Start
High level:
1. Click or drag the Start icon from left menu and place anywhere in the edit area (need to be in edit/draft mode)
2. Double click the Start icon to access the configurations
3. Click Add new source
4. Enter appropriate configurables
5. If applicable; click Add new source to another source
6. When all is completed; click Save (don´t forget to Save the entire scheme as well)
Available in scheme types:
Mid-Office
Non-pricing
PNR redirector
Pricing and Ticketing
Ticket processing
Sources
 |
|
| Database query Get PNRs from a database, an external source.  Applicable to schemes: Non-pricing PNR redirector Pricing and Ticketing Ticket processing Mid-office | External start PNRs are sent to the scheme from another scheme  Applicable to schemes: Non-pricing PNR redirector Pricing and Ticketing Ticket processing Mid-office |
| GDS queue Get PNRs from a GDS queue  Applicable to schemes: Non-pricing PNR redirector Pricing and Ticketing | REST Get PNRs from a REST API  Applicable to schemes: Non-pricing Pricing and Ticketing Ticket Processing Mid-office |
General parameters per scheme type and source
| Sources/basic parameters per scheme | Database query | External start | GDS queue | REST |
|---|---|---|---|---|
| Fetch PNRs from an external database | PNRs are sent to the scheme from another scheme | Fetch PNRs from GDS queue/s | Fetch PNRs from a REST API | |
| Scheme type Mid-Office | Y | Y | N | Y |
| Scheme type Non-pricing | Y | Y | Y | Y |
| Scheme type PNR redirector | Y | Y | Y | N |
| Scheme type Pricing and Ticketing | Y | Y | Y | Y |
| Scheme type Ticket processing | Y | Y | N | N |
| Time interval to check for new PNR candidates | Y | N | Y | Y |
| Connection name | Y | N | N | N |
| Database query to select PNRs for processing (only PNR field to be selected) | Y | N | N | N |
| OfficeID/PCC | N | N | Y | N |
| Queue number(s) | N | N | Y | N |
| Category/PIC | N | N | Y | N |
| Remove PNR from queue. | N | N | Y | N |
| REST interface URL | N | N | N | Y |
| User Name | N | N | N | Y |
| Password | N | N | N | Y |
General parameters details
Time interval to check for new PNR candidates
Specify how often the scheme should check for PNRs, for example every 10th minute, every 2nd hour, weekly on Mondays at 10:00 only etc.
If the pre-defined intervals doesn´t fit your needs you can add a cron job under the tab Custom. See for example https://crontab.guru/ how to create a cron job.
-Cron job example: 0 10,14 * * MON,WED,FRI,TUE,THU means the scheme will run every Monday-Friday at 10:00 and 14:00.
If the source is GDS do not have a too short interval to prevent too many unnecessary hits to the GDS.
Applicable to source:
Database query
GDS queue
REST
Applicable to scheme:
Non-pricing
PNR redirector
Pricing and Ticketing
Ticket processing
Connection name
If you connect to an integrated database, choose which connection to use in this dropdown list.
Applicable to source:
Database query
Applicable to scheme:
Non-pricing
PNR redirector
Pricing and Ticketing
Ticket processing
Mid-Office
Database query to select PNRs for processing (only PNR field to be selected)
If you connect to an integrated database, specify database query to use for fetching data.
Applicable to source:
Database query
Applicable to scheme:
Non-pricing
PNR redirector
Pricing and Ticketing
Ticket processing
Mid-Office
OfficeID/PCC
Specify from which OfficeID/PCC the scheme should fetch PNRs for processing. To see all available PCCs for your setup click Manage OfficeID/PCCs or use the arrow down to see a list. Only one OfficeID/PCC may be used per source, but you can add multiple sources (but the GDS must be the same in a scheme).
Applicable to source:
GDS queue
Applicable to scheme:
Non-pricing
PNR redirector
Pricing and Ticketing
Queue number(s)
Specify queue number(s) from which the scheme should fetch PNRs for processing. You can specify multiple queueus, separate with a comma.
Applicable to source:
GDS queue
Applicable to scheme:
Non-pricing
PNR redirector
Pricing and Ticketing
Category/PIC
Specify Category/PIC codes from which the scheme should fetch PNRs for processing. You can not specify multiple Categories/PIC codes. If required, use multiple sources.
Applicable to source:
GDS queue
Applicable to scheme:
Non-pricing
PNR redirector
Pricing and Ticketing
Remove PNR from queue.
If checked the PNRs fetched are always removed from the queue when processed. Note that if checked but the scheme process is not completed, the PNR is still removed from the queue.
Applicable to source:
GDS queue
Applicable to scheme:
Non-pricing
PNR redirector
Pricing and Ticketing
REST interface URL
If a REST API is integrated, enter an URL to access to fetch data.
Applicable to source:
REST
Applicable to scheme:
Non-pricing
Pricing and Ticketing
User Name
If a REST API is integrated, enter a username to access to fetch data.
Applicable to source:
REST
Applicable to scheme:
Non-pricing
Pricing and Ticketing
Password
If a REST API is integrated, enter a password to access to fetch data.
Applicable to source:
REST
Applicable to scheme:
Non-pricing
Pricing and Ticketing
Ticketing and Pricing specific parameters
| General Ticketing and Pricing parameters Limit processing to reservations created only in following OfficeIDs/PCCs (optional)  Specify exact OfficeIDs/PCCs allowed to process reservations. Eg, if a reservation is created in an OfficeID/PCC that is not in the list it will not be processed. Separate OfficeIDs/PCCs with a comma or semi-colon. Process reservations only if FQ, PQ, TST has been created by a user listed in the list below (optional)  Price has to be stored by an agent specified in the list otherwise the reservation will not be processed. Use any/private/published fares for PNR pricing.  Choose which type of fares that will be allowed to be processed. Refresh FQ, PQ, TST on a daily basis.  Update the stored price on a daily basis Keep previously stored fare within the same reservation class - This disables change of fare or fare basis at time of pricing if a lower fare is found within the same reservation class.  Make sure a re-pricing/re-storing of a fare/price is using the same reservation class, fare or farebasis as the current stored fare/price. (– for Fare increase rules, see next row below –) Disable fare evaluation for PNRs with following segment status codes: enter codes, for example UX, HX  Enter codes that will be excluded from a check of alternative fares. Stop processing PNR if any part of the routing has been modified.  Stop processing PNR if the fare brand could not be matched to the farebasis in original FQ, PQ, TST.  Send notification if mid-office reference cannot not be determined.  If reference cannot be determined send an email to the email address defined in System Settings ⇒ E-mail ⇒ System e-mail settings ⇒ System e-mail To address. Create FQ, PQ, TST and continue processing PNR if no FQ, PQ, TST exists for the class booked.  Stop processing if the total fare currency is different from the currency set in the scheme properties.  Ensures the fare in the stored total price is the same as specified in the scheme properties. Example:  Send notification if no valid segments were detected in PNR.  If no valid segments found send an email to the email address defined in System Settings ⇒ E-mail ⇒ System e-mail settings ⇒ System e-mail To address. Process split PNRs by the same scheme when detected.  If the PNR has been split the scheme will also process the split PNRs. |
Fare increase rules  Fare rule increase section allows you to detect and manage unexpected increase of Base, Equivalent, Tax or Total Fare every time reservation is processed by the Start element. Create one or multiple rules specifying the fare increase level and suitable action to be taken if such increase is detected. If multiple rules are set, the sequence that they are created in will determine the order how rules are applied. Create one or multiple rules to track fare increase. Compare reservation total value/passenger total value with original value/value from valid PQ, FQ, TST/value from last attempt  Check the following conditions: value increase more (enter than amount or %)  reason for value increase is any/increase of currency exchange rate/not currency exchange rate  valid FQ, PQ, TST from today exists does not matter/yes/no  If conditions are met, perform following actions: issue tickets  notify by e-mail  do not create new FQ, PQ, TST  stop processing of PNR and notify by e-mail  |
__