Differences

This shows you the differences between two versions of the page.

--- sidebar:products_solutions:automation:actions:start [2020/09/03 09:12] – Peter Lagnerud
+++ sidebar:products_solutions:automation:actions:start [2020/09/11 09:26] (current) – Peter Lagnerud
@@ Line 3: / Line 3: @@
 {{  :sidebar:action_start.png?nolink&200  }}
-High level:
+**Available in scheme types:**
-. Click or drag the Start icon from left menu and place anywhere in the edit area (need to be in edit/draft mode)
-. Double click the Start icon to access the configurations
-. Click Add new source
-. Enter appropriate configurables
-. If applicable; click Add new source to another source
-. When all is completed; click Save (don´t forget to Save the entire scheme as well)
-Available in scheme types:
 Mid-Office\\
@@ Line 26: / Line 12: @@
 === Sources ===
+You can have multiple sources in the Start step (but only one GDS per scheme).
 |{{  :sidebar:sources.png?nolink&600  }}||
@@ Line 108: / Line 96: @@
 {{  :sidebar:start_pcc_new.png?direct&600  }}
-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).
+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 (and PIC/Category) may be used per source, but you can add multiple sources (note: you must have the same GDS for all sources in a scheme. If you have the same scheme/process for several GDS: create separate schemes).
 Applicable to source:\\
@@ Line 199: / Line 187: @@
 |**Fare increase rules** \\  \\ {{  :sidebar:ticketingpricing_02.png?direct&600  }} \\ 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** \\  \\ **{{  :sidebar:farerules_1compare.png?direct&400  }}** \\  \\ **Check the following conditions:** \\  \\ **value increase more (enter than amount or %)** \\ {{  :sidebar:farerules_2valueincrease.png?direct&400  }} \\ **reason for value increase is any/increase of currency exchange rate/not currency exchange rate** \\  \\ **{{  :sidebar:farerules_3reasonforvalue.png?direct&400  }}** \\ **valid FQ, PQ, TST from today exists does not matter/yes/no** \\  \\ {{  :sidebar:farerules_4validpq.png?direct&400  }} \\  \\ **If conditions are met, perform following actions:** \\ **issue tickets** \\  \\ {{  :sidebar:products_solutions:automation:actions:farecond_1issue.png?direct&400  }} \\ **notify by e-mail** \\  \\ {{  :sidebar:products_solutions:automation:actions:farecond_2notify.png?direct&400  }} \\ **do not create new FQ, PQ, TST** \\  \\ {{  :sidebar:products_solutions:automation:actions:farecond_3donotcreate.png?direct&400  }} \\ **stop processing of PNR and notify by e-mail** \\  \\ **{{  :sidebar:products_solutions:automation:actions:farecond_4stopprocessing.png?direct&400  }}**   |
-__
+----
+[[:sidebar:products_solutions:automation:schemes:actions|Back to Actions]]
 [[:sidebar|Back to main page]]