Dev:SARA-PAE Processing rule actions

From Kordeus Wiki
Jump to navigation Jump to search

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

Communication actions

Generally these information actions are supported:

  • Create 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)
    • Business participant groups or individual business participants
      • secure receipients (Email, Telex)
      • insecure receipients (Portal)
    • eventually a deadline can be added. If deadline is missed
      • the requested party can be notified by Reminder-Emails.
      • the requesting party can receive reminder tasks (see task template),
    • eventually the task template requres cross-check. Upon completion the requested side, this will automatically create a task to check the contents to a predefined business participant group. If cross-checking is enabled with a task template, tasks do terminate not at done but at the done & crosschecked status.
  • 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)
  • Create chat message - Requires a text message and the sender business participant (MOC-auto-sender?)
  • 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 / Portal 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
  • SARA Comment to show above service section
  • Comment to show above service - select service
  • SARA - Make birthdate mandatory
  • PAX.Portal - Make birthdate mandatory
  • Make Ambulance car data mandatory (drivers name [yes/no], drivers license photo [yes/no], license plate [yes/no], drivers telephone [yes/no])
  • 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)
  • PAX.Portal - Show Comment in service section (Text, background color, foreground color)
  • PAX.Portal - Make standard document downloadable as part of service section [pick standard document, pick master travel service]
  • PAX.Portal - Make standard document downloadable at the closing screen [pick standard document]
  • PAX.Portal - Show Comment at closing screen (Text, background color, foreground color)
  • Document Slot related functionality
    • Add document slot (Slotname, always visible in SARA, visible in PAX.Portal [yes/no], mandatory for pay[yes/mo], requires MOC-confirmation [yes/no], mandatory for fit-to-dly[yes/no], Allow download of bound standard-document templates [yes/no], )
    • Restrict downloadable templates for slot (Select Slot, select the downloadable templates) - required, e.g. depending on regional laws
    • Make document slot comment visible in SARA (Requires comment to be entered)
    • Make document slot comment visible in PAX.Portal (Requires comment to be entered)

Related articles

Retrieved from "https://wiki.kordeus.com/index.php?title=Dev:SARA-PAE_Processing_rule_actions&oldid=2310"