Dev:SARA-PAE Processing rule actions

Each matching rule may define one or multiple actions to be automatically performed

Communication actions

Generally these information actions are supported:

• Create internal task - 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
• Create communication - 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)
• Perform HandlingAdvice - See this article for details.
• Perform RoutineCheck - 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)

Which data will be shared?

For each of the information actions there is generally defined , which information of the case can be included

• Personal information
  • Name-Properties
  • Birthdate
  • Communication-Properties (Phone, Fax, Email)
  • Body/Medical-Information (Weight, Height)
  • Requesting Travel Agent Information
  • Medical information of patient
• Booking information
• Classified MEDA information
• Filled placeholders. See placeholderlist.

When it comes to communication generation, there are often also service specific restrictions about what information may be handed out to external parties.

Data Privacy Note: The generated contents for communication or tasks, will then only contain the information which may be included. Even if the template can support more information, it will not be filled.

SARA process flow manipulations

By default the SARA process flow adheres to standard PWD or MEDA processing flow. Still the process flow can be modified, which affects the user interface and the processes. Currently these process tweaks are available

• 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)

Related articles

• SARA-PAE Process Automation Engine