Mionamilosevic: /* Travel Partner Overview Page */

2026-02-25T14:03:22Z

Travel Partner Overview Page

← Older revision		Revision as of 14:03, 25 February 2026
Line 79:		Line 79:

	•Cannot delete if partner is referenced in task automation		•Cannot delete if partner is referenced in task automation
			[[File:Travel partner.png\|none\|thumb]]


	== '''Travel Partner – General Page''' ==		== '''Travel Partner – General Page''' ==
Line 194:		Line 196:

	•Cannot delete assistant if assigned to open tasks.		•Cannot delete assistant if assigned to open tasks.
			[[File:Travel partner general.png\|none\|thumb]]


	== '''Travel Assistant Details Page''' ==		== '''Travel Assistant Details Page''' ==
Line 269:		Line 273:

	Confirmation popup if unsaved changes exist.		Confirmation popup if unsaved changes exist.
			[[File:Travel partner travel assistans.png\|none\|thumb]]


	== '''B-Op Digital Integration''' ==		== '''B-Op Digital Integration''' ==

Mionamilosevic at 13:56, 25 February 2026

2026-02-25T13:56:11Z

← Older revision		Revision as of 13:56, 25 February 2026
Line 302:		Line 302:

	== Related articles ==		== Related articles ==
	Translations		[[Dev:LH MOC Admin-Travel partner Translations\|Translations]]

Mionamilosevic: Created page with "The '''Travel Partner Administration''' module allows administrators to manage external agencies and operational partners that interact with the system. Travel Partners can: •Request services on behalf of passengers •Receive automated tasks •Act as operational or medical intermediaries •Be linked to B-Op digital workflows This module ensures: •Proper identification of partner organizations •Clear contact structure via assistants •Traceable communic..."

2026-02-25T13:53:16Z

Created page with "The '''Travel Partner Administration''' module allows administrators to manage external agencies and operational partners that interact with the system. Travel Partners can: •Request services on behalf of passengers •Receive automated tasks •Act as operational or medical intermediaries •Be linked to B-Op digital workflows This module ensures: •Proper identification of partner organizations •Clear contact structure via assistants •Traceable communic..."

New page

The '''Travel Partner Administration''' module allows administrators to manage external agencies and operational partners that interact with the system.

Travel Partners can:

•Request services on behalf of passengers

•Receive automated tasks

•Act as operational or medical intermediaries

•Be linked to B-Op digital workflows

This module ensures:

•Proper identification of partner organizations

•Clear contact structure via assistants

•Traceable communication and responsibility

•Integration into automated task and service flows

== '''Travel Partner Overview Page''' ==
'''Purpose'''

Provides a searchable list of all registered Travel Partners.

This page enables administrators to:

•View existing partners

•Add new partners

•Edit partner details

•Remove partners

•Monitor digital connection status

'''➕ Add New'''

Creates a new Travel Partner entry.

'''🔍 Search (Search icon)'''

Filters the list by:

•Travel Partner Name

•Internal Code

•Country

'''📋 Table Columns'''

'''Column''' '''Description'''

Name Official name of the Travel Partner

Entity of Indicates which carrier or organization the partner belongs to (if applicable)

B-Op Connection / Linked Digital Shows digital connection status

'''✏ Edit Icon (per row)'''

Opens the Travel Partner details page.

'''🗑 Delete Icon (per row)'''

Removes the Travel Partner from the system.

A confirmation popup must appear before deletion.

Deletion restrictions:

•Cannot delete if partner is used in active service requests

•Cannot delete if partner is referenced in task automation

== '''Travel Partner – General Page''' ==
'''Purpose'''

Defines the core identity of the Travel Partner and enables its operational activation within the system.

=== '''Base Data Section''' ===
'''Travel Partner Name (Required)'''

Official name of the organization.

Used for:

•Task assignment

•Notifications

•Service requests

•Operational visibility

'''Internal Code (Required)'''

Unique internal system identifier.

Used for:

•Backend logic

•API communication

•Reporting

•Filtering and segmentation

Must be unique.

'''Country (Required)'''

Defines:

•Operational jurisdiction

•Time zone logic (if needed)

•Regulatory considerations

'''Label (Status Indicator)'''

Shows lifecycle status:

•🟢 Active

•🟡 Pending

•🔴 Inactive

This reflects:

•Whether the partner is fully configured

•Whether required data is missing

•Whether digital connection is established

'''Actions'''

'''💾 Save'''

Stores changes.

Validation:

•All required fields must be completed.

•Internal code must be unique.

'''❌ Cancel'''

Returns to overview page.

Confirmation popup required if unsaved changes exist.

=== '''Travel Assistants Overview Panel''' ===
'''🔍 Search'''

Filters assistants by:

•Name

•Email

•Job position

'''➕ Add New'''

Creates a new assistant entry.

'''✏ Edit'''

Edit selected assistant.

'''🗑 Delete'''

Remove assistant.

Confirmation popup required.

Deletion restrictions:

•Cannot delete assistant if assigned to open tasks.

== '''Travel Assistant Details Page''' ==
'''Fields'''

'''First Name (Required)'''

'''Last Name (Required)'''

Used for:

•Task assignment

•Notification display

'''Job Position at the Agency (Required)'''

Defines role within the Travel Partner organization.

Used for:

•Task routing logic

•Filtering in automation rules

•Hierarchical responsibility

This field may:

•Allow selection from predefined positions

•Allow creation of new positions (depending on role management settings)

'''Email (Required)'''

Primary communication channel.

Used for:

•Automated task notifications

•Service updates

Must be valid email format.

'''Phone (Required)'''

Used for:

•Urgent operational contact

•Medical coordination

'''Actions'''

'''💾 Save'''

Stores assistant.

Validation:

•All required fields must be filled

•Email must be valid

•No duplicate email under same Travel Partner

'''❌ Cancel'''

Returns to Travel Partner page.

Confirmation popup if unsaved changes exist.

== '''B-Op Digital Integration''' ==
If B-Op digital connection is enabled:

Travel Partner may:

•Receive automated tasks

•Send digital service requests

•Synchronize case updates

•Be assigned as service delivery partner

Connection states:

•Connected

•Not Connected

•Pending

•Error

System must:

•Show connection indicator

•Provide connection validation

•Show error message if connection fails

== Related articles ==
Translations

Dev:LH MOC Admin-Travel partner - Revision history

Mionamilosevic: /* Travel Partner Overview Page */

Mionamilosevic at 13:56, 25 February 2026