|
|
| Line 15: |
Line 15: |
|
| |
|
| == Actions == | | == 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
| |
| * Fit-To-Fly is forbidden for this segment
| |
| * 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)
| |
The automation engine is a rule based processor specifically made for the business domain of special assistance requests.
In general it holds rules, which lead to special assistance specific actions :
Available Triggers
Supported matching criteria
Actions