Dev:LH MOC Admin-Text Standard blocks
The Standard Text Block Administration module allows administrators to create and manage reusable text fragments that can be inserted into communication templates such as emails, letters, and notifications.
These text blocks ensure:
•consistent communication
•faster message creation
•reusable standardized phrases
•multilingual support
•dynamic content through placeholders
Typical use cases include:
•email openings and greetings
•closing phrases and signatures
•procedural explanations
•medical information texts
•regulatory statements
Standard text blocks can be reused across multiple communication templates, ensuring uniform wording and reducing duplication.
Standard Text Block Groups
Standard text blocks are organized into groups that categorize their purpose.
This improves:
•navigation
•maintainability
•template design
•reuse of communication fragments
Example Groups
| Group | Purpose |
|---|---|
| Letter | text blocks used in letters and email communication |
| Medical | Medical related standard communication |
| Processual | Procedural or operational |
Selecting a group displays the text blocks contained in that category. All groups will be added manually
Standard Text Block Group Overview
Displays all standard text blocks belonging to the selected group.
Example from screenshot:
Contents of standard text block group: Letter
Table Columns
| Column | Description |
|---|---|
| Name | Name of the text block |
| Used | Indicates whetther the block is currently used in communication templates |
| Usage in Communication Templates | Lists templates where the block is used |
Row Actions
Edit (✏️)
Opens the Text Block Editor.
Delete (🗑)
Deletes the selected text block.
Deletion may be restricted if the block is used in communication templates.
Buttons
Add new
Creates a new standard text block inside the selected group.
Search (🔍)
Filters text blocks by name.
Text Block Editor
The Text Block Editor is used to create or modify the reusable content stored in a text block.
Each block contains:
•an identifier
•multilingual content
•formatted text
•dynamic placeholders
These blocks can then be inserted into communication templates.
Header
Text Block Title
Displays the name of the block currently being edited.
Example: Text block "MEDIF Request via Email"
Text Block Identifier
Field
Text-Block-Identifier
Example: my-text-block-17
Purpose:
•unique internal reference
•used by templates to identify the block
This identifier should remain stable once created.
Internal Name
Field
Internal name
Example: Lufthansa Technics DE
Purpose:
•internal administrative name
•helps identify the block in the system
The internal name may differ from the visible content.
Text Block Content
Language Tabs
The system supports multilingual text blocks.
Languages shown in the interface:
•English
•German
•French
•Italian
Each language version contains the localized content for the block.
This ensures communications are sent in the recipient’s language.
Rich Text Editor (QuillJS)
The content is written using a QuillJS rich text editor.
The editor supports:
| Feature | Purpose |
|---|---|
| Font selection | Choose font type |
| Font size | Adjust text |
| Bold/Italic/Underline | Text emphasis |
| Lists | Bullet or numbered list |
| Alignmnet | Text alignment |
| Links | Insert hyperlinks |
| Images | Embed images if required |
This allows formatting of professional communication messages.
Standard Text Block Content
Main content field:
Standard Text Block
Example: Dear Template:PAX Letter Salutation Template:PAX Last Name,
Purpose:
•defines the reusable communication text
•may contain placeholders
•may include formatted text
This block is inserted into larger communication templates.
Available Placeholders
Panel on the right side.
Displays dynamic variables that can be inserted into the text.
Example placeholders:
| Placeholder | Description |
|---|---|
| SAR-Case-Number | Case reference number |
| SAR-Request Date | Date of the request |
| PAX Letter Salutation | Passenger greeting (Mr./Ms.) |
| PAX Last Name | Passenger last name |
| PAX first Name | Passenger first name |
| PAX Birthdate | Passsenger date of birth |
| PAX Booking Code (PNR) | Passenger booking reference |
| Case Service Request Table (HTML) | Table with requested services |
| Journey (HTML Table) | Table with journey details |
| Journey Departure Date | Departure date |
| Journey Next Trip Departure Date | Next segment departure |
| ESCORT list | List of escort services |
| ESCORT Table with full information | Detailed escort information |
| Full Service Tree Table | Complete list of services |
| AMBULANCE Details Table (HTML) | Ambulance service information |
Purpose of Placeholders
Placeholders are replaced with real case data when the communication is generated.
Example:Dear Template:PAX Last Name becomes Dear Smith
Available Standard Text Blocks
Panel:
Available standard text blocks
This section displays reusable blocks that can be inserted into the current text block.
Examples from the screenshot:
•Standard Letter Opening
•Processing Agent Footer
•Processing Agent Footer with closing phrase
Manage Standard Blocks
Button:
Manage Standard Blocks
Opens the administration area where standard blocks can be managed.
Purpose:
Allows combining smaller blocks into larger communication texts.
Example structure of a letter:
[Standard Letter Opening]
[Main Message Content]
[Processing Agent Footer]
Workflow Usage
Standard text blocks are used in:
| Area | Purpose |
|---|---|
| Communication Templates | Emails and letters |
| Medical communication | MEDIF requests |
| Operational notifications | Service confirmations |
| Partner communication | Message to external partners |