Dev:SARA.ProcessAutomationEngine: Difference between revisions

From Kordeus Wiki
Jump to navigation Jump to search
← Older edit
VisualWikitext
Stefanseiler (talk | contribs)
Bureaucrats, dev-team, developer, Interface administrators, iroc-team, Suppressors, Administrators, yousee-team
1,381 edits
Stefanseiler (talk | contribs)
Bureaucrats, dev-team, developer, Interface administrators, iroc-team, Suppressors, Administrators, yousee-team
1,381 edits
No edit summary
 
(11 intermediate revisions by the same user not shown)
Line 1: Line 1:
The automation engine is a rule based processor specifically made for the business domain of '''special assistance requests.'''
The automation engine is a rule based processor specifically made for the business domain of '''special assistance requests''', which adhere to the [[Dev:Travel assistance service request - general handling process|travel assistance service request - general handling process]]. 
 
This is a background service, which supports all processees of an operation center.
 
The engine has these main components:
 
* [[Dev:Travel Segment Service Item Claiming|Travel Segment Service Item Claiming]] - It evaluates the SAR Requests it is requested by a Passenger Digital and indicates it to be the responsible MOC by
** claiming service segments of the requested journey.
** claiming the entire request, if no journey is present
* [[Dev:SARA.ProcessAutomationEngine|Internal Process Automation Engine]] - this service evaluates a specific ruleset and performs specific actions. The ruleset can be configured in the [[Dev:SARA Engine Ruleset Administration Tool|SARA Engine Ruleset Administration Tool]]. 
 
The SARA Process Automation Engine as well has impact on [[PAX.Portal]] behaviour!


In general it holds rules, which lead to special assistance specific actions :
In general it holds rules, which lead to special assistance specific actions :
Line 8: Line 19:
** [[Dev:SARA-PAE Processing rule actions|Processing rule actions]]
** [[Dev:SARA-PAE Processing rule actions|Processing rule actions]]


== Available Triggers ==
== Related articles ==
*
 
== Supported matching criteria ==
**
 
== Actions ==
Each matching rule may define one or multiple actions to be automatically performed
 
====== Information Actions ======
For each of the information actions you have to decide, which information of the case <u>can</u> be included
 
* Personal information
** Name-Properties
** Birthdate
** Communication-Properties (Phone, Fax, Email)
** Body/Medical-Information (Weight, Height)
** Requesting Travel Agent Information
* Booking information
* Classified MEDA information
* Filled placeholders. See [[Dev:SARA-PAE Placeholderlist|placeholderlist]].
When it comes to communication generation, there are often also service specific restrictions about what information <u>may</u> be handed out to external parties.
 
'''Data Privacy Note''': The generated contents for communication or tasks, will then only contain the information which <u>may</u> be included. Even if the template <u>can</u> support more information, it will not be filled.
 
Generally these information actions are supported:
* <u>Create internal task</u> - Requires a selected '''task template''' and needs to define the list of '''task receivers.''' Task receivers can be:
** predefined receipients roles (Passengers, Travel Agent, MOC Team, Doctors Team, Controlling Team)
** secure receipients (Business participant groups or individual business participants) or
** eventually a deadline can be added after which the remote party and the requesting party is notified by Reminder-Emails
* <u>Create communication</u> - Requires a selected '''communication template''' and '''receipients'''. Communication receipients can be
** predefined receipients roles (Passengers, Travel Agent, MOC Team, Doctors Team, Controlling Team)
** secure receipients (Business participant groups or individual business participants) or
** ''insecure receipients'' (by adding TELEX or EMAIL addresses)
* <u>Perform HandlingAdvice</u> - See [[Dev:SARA-PAE Handling Advide|this article for details]].
* <u>Perform RoutineCheck</u> - This will create a communication for a '''specific service''' in a predefined '''communication template''' to receipients, which are calculated by a specific logic for the routine check. It typically contains:
** to all involved service delivery partners (secure/insecure)
** to eventually involved extra routine check receipients (secure/insecure)
 
====== Manipulate SARA Process Flow ======


* Mark Service as impossible on this segment
* [[SARA.Core (Special Assistance Request Management Suite)]]
* Fit-To-Fly is forbidden for this segment
* [[PAX.Portal]]
* Confirmation (HK/KK) is forbidden for this segment
* Comment to show above service section
* Comment to show above service - select service
* Make PAX birthdate mandatory
* Make Ambulance car data is mandatory (driver, plate, ...)
* Add special Email/Telex receipient(s) to Standard Handling Advice for this trip
* Add additional email/Telex receipient(s) to Standard Routine Telex for this trip
* Disable MEDA process flow (if not manually locked)
* Enable MEDA process flow (if not manually locked)

Latest revision as of 05:40, 26 June 2025

The automation engine is a rule based processor specifically made for the business domain of special assistance requests, which adhere to the travel assistance service request - general handling process.

This is a background service, which supports all processees of an operation center.

The engine has these main components:

The SARA Process Automation Engine as well has impact on PAX.Portal behaviour!

In general it holds rules, which lead to special assistance specific actions :

Related articles

Retrieved from "https://wiki.kordeus.com/index.php?title=Dev:SARA.ProcessAutomationEngine&oldid=2513"