Dev:LH MOC Admin-Task template administration
The Task Template Administration module allows administrators to define standardized operational tasks that can be automatically or manually generated during case workflows.
Task templates help ensure that recurring operational actions are:
•consistent
•clearly documented
•assigned to the correct participants
•executed within defined deadlines
Typical examples of tasks include:
•Operational checks
•Medical verification
•Service confirmations
•Communication with partners
•Follow-up reminders
•Documentation checks
Task templates support:
•multilingual communication
•dynamic placeholders
•service associations
•priority management
•deadline automation
•assignment to teams, groups, or individuals
•controlled data sharing with external partners
These templates are used throughout the system to support Medical Operation Center (MOC) workflows.
Task Template Groups
Task Template Groups organize task templates into logical categories.
Grouping templates improves:
•navigation
•administration
•workflow clarity
•task discovery
Examples of groups shown in the system:
| Group | Typical use |
|---|---|
| General | Common operational tasks |
| Sitiing case | Tasks specific to sitting passengers |
| Stretcher | Stretcher related operational tasks |
| Oxygen Concentrators | Oxygen service handling |
| SVAN | Special assistance services/pet related |
| Travel partners | Partner coordination tasks |
| Whatever (Free text) | Custom operational tasks |
Each group contains one or more templates.
Task Template Group Overview
Displays all templates belonging to the selected task template group.
Example shown in mockup:
Contents of task template group: General
Table Columns
Column Description
Name Name of the task template
Row Actions
Edit (✏️) Opens the Task Template Editor for modifying the template.
Delete (🗑) Removes the task template.
Deletion is restricted if the template is used in active workflows.
Buttons
Add new Creates a new task template inside the selected group.
Search (🔍) Filters templates by name.
Task Template Editor
The Task Template Editor defines how a task behaves when it is generated in a workflow.
This includes:
•content
•responsible participants
•deadlines
•priority
•service associations
•data sharing permissions
Task Definition
Internal Name
Internal identifier for the template.
Used for:
•administration
•searching
•system reference
Example: Lufthansa Technics DE
Communication (Language Tabs)
Supports multilingual task communication.
Each language version contains:
•task subject
•task description
This ensures that tasks are displayed in the user’s language.
Task Subject
Defines the short title of the task.
Example: Check ESCORT NON-Upgrade SK
This title appears in:
•task lists
•notifications
•workflow views
Description
Detailed explanation of the task.
Used to provide instructions to the user performing the task.
Examples:
•operational instructions
•service procedures
•reminders
•documentation requirements
This field can also include instructional text helpful for new employees.
Task Type
Dropdown defining the nature of the task.
Typical options include:
| Type | Purpose |
|---|---|
| Reminder | Informational task |
| Action | Task requiring operational action |
| Approval | Task requiring approval |
Task type influences how the task appears in the system and actions related to it.
Priority
Marks the task as high priority.
Priority tasks:
•appear highlighted in task lists
•are handled before normal tasks
Due Date
Defines when the task must be completed.
Options:
| Option | Description |
|---|---|
| Immediately | Task appears instantly |
| In hours | Deadline defined in hours |
| In days | Deadline defined in days |
This allows tasks to be automatically scheduled relative to workflow events.
Participants & Groups
Defines who is responsible for executing the task.
Tasks can be assigned to:
•individual users
•teams
•business groups
•external partners
Add Business Group Participant
Adds a specific user belonging to a business group.
Example:
•doctor
•operations manager
Add Business Group
Assigns the entire group.
Example groups:
•MOC Operations Team
•MOC Medical Team
This ensures that any available member of the group can execute the task.
Request Task With
Associates the task template with partners, groups, or users.
Examples shown in mockup:
•MOC Operations Team
•MOC Medical Team
•External Doctors
•MSC Cruises
•LH Technics MUC
•Individual users
A search field allows filtering participants.
Functional Placeholders
Panel: Available functional placeholders
These placeholders allow dynamic values to be inserted into task text.
Examples:
| Placeholder | Purpose |
|---|---|
| Travel partner | Inserts travel partner name |
| Pasenger (PAX) | Inserts passenger name |
| Requesting party | Shows who requested the service |
| Service delivery partner | Shows ground service provider |
When a task is generated, placeholders are automatically replaced with real values.
Associated Services
Links the task template to one or more services.
Example from mockup:
•WENOLL
•STRETCHER
Important:
These are services, not only travel services.
Purpose:
•ensures that correct templates are suggested when specific services are used
•improves task automation accuracy
Data Protection / Task Data Sharing with External Partners
Defines which information external partners can access when tasks are shared with them.
This ensures compliance with data protection regulations.
Shares basic case information:
•case ID
•passenger name
•case status
Allows partners to see:
•flights
•segments
•travel itinerary
Allows access to:
•booking
•PNR
•ticket information
Allow Editing Case Ticketing Information
Allows partners to modify ticket data.
This option becomes available only when ticketing information sharing is enabled.
Allows partners to see which services were requested.
Examples:
•stretcher
•oxygen
•escort
Allows sharing of medical data related to the case.
Example:
•MEDA information
This option should be enabled only when medically necessary.