Dev:SARA-PAE Rule Check Triggers: Difference between revisions
Jump to navigation
Jump to search
Stefanseiler (talk | contribs) m Stefanseiler moved page Dev:SARA-PAE Processing Engine Triggers to Dev:SARA-PAE Processing Rule Check Triggers without leaving a redirect |
Stefanseiler (talk | contribs) No edit summary |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
The ''SARA Engine'' is triggered each time, when a special assistance request reaches one of the SAR checkpoints: | === Trigger categories === | ||
Generally each process automation rule associated with a trigger category. Currently SARA-PAE suppots these trigger categories: | |||
* '''OnBASEDATAUpdate''' - the base data of the SAR has updated changed. Examples: New case, PAX name changed, | |||
* '''OnSERVICEDELIERYTREEUpdate''' - upon any change of the service delivery tree, this event will be triggered. Examples are: The passenger added a new service, the itinerary changed, ... | |||
* '''OnSERVICEHANDLINGDATAUpdate''' - the process or medical team has changed any data relevant in the decision process of a deliery request | |||
* '''OnDELIVERYPARTNERUpdate''' - one of the delivery partners, which are associated with this case has provided information affecting this special assistance request case. Examples: Updated capacity or task was accepted/rejected/done, ... | |||
* '''OnVESSELUpdate''' - if the request holds any service depending on the vessel, this trigger is catched, Examples are: Rotation changed, flight is cancelled, ... | |||
* '''OnGENERALSTATUSUpdate''' - if a milestone of a special assistance request is reached. Example: "Medical team approval", "Process team approval", | |||
* '''OnTRAVEL''' - any defined travel relation goal is reached. Example: 24h before first travel segment start, ... | |||
The ''SARA Engine'' is triggered each time, when a special assistance request reaches one of the SAR checkpoints. | |||
It will then check the SAR-Rules, which are bound to one of these trigger porints: | |||
* On SAR-Request Claim | * On SAR-Request Claim | ||
| Line 20: | Line 35: | ||
== Related articles == | == Related articles == | ||
* [[Dev:SARA | * [[Dev:SARA.ProcessAutomationEngine]] | ||
Latest revision as of 15:45, 22 June 2025
Trigger categories
Generally each process automation rule associated with a trigger category. Currently SARA-PAE suppots these trigger categories:
- OnBASEDATAUpdate - the base data of the SAR has updated changed. Examples: New case, PAX name changed,
- OnSERVICEDELIERYTREEUpdate - upon any change of the service delivery tree, this event will be triggered. Examples are: The passenger added a new service, the itinerary changed, ...
- OnSERVICEHANDLINGDATAUpdate - the process or medical team has changed any data relevant in the decision process of a deliery request
- OnDELIVERYPARTNERUpdate - one of the delivery partners, which are associated with this case has provided information affecting this special assistance request case. Examples: Updated capacity or task was accepted/rejected/done, ...
- OnVESSELUpdate - if the request holds any service depending on the vessel, this trigger is catched, Examples are: Rotation changed, flight is cancelled, ...
- OnGENERALSTATUSUpdate - if a milestone of a special assistance request is reached. Example: "Medical team approval", "Process team approval",
- OnTRAVEL - any defined travel relation goal is reached. Example: 24h before first travel segment start, ...
The SARA Engine is triggered each time, when a special assistance request reaches one of the SAR checkpoints.
It will then check the SAR-Rules, which are bound to one of these trigger porints:
- On SAR-Request Claim
- On Journey Entry/Change
- On Segment-Service add/remove
- On Full MEDA Approval
- Full Fit-To-Fly status reached
- Full Confirmend status reached (all Segments HK [holding confirmed] or KK [manually confirmed] )
- On SAR-request Cancel
- Time (in h) before journey start
- Time (in h) before journey end
- Time (in h) before trip start - embarcation event
- Time (in h) before trip end - disembarcation event
- Time (in h) before segment start
- Time (in h) before segment end
- Time (in h) before port Arrival (or Departure time of first trip segment)
- Time (in h) before port Departure (or Arrival at the last trip Segment)
- On all Segments flown
- On Service capacity limit reached