Itinerary - Add Service Providers from within Nexus

Overview

This release introduces the ability to create new itinerary provider values directly from itinerary forms without requiring pre-configured master list entries.

Previously, itinerary provider fields were restricted to existing picklist values. If a required provider was not available, users had to wait for a master data update before continuing itinerary creation or maintenance.

With this enhancement, users can add missing provider values directly from the itinerary form using a +Add action. The new value is automatically saved to the corresponding master list, immediately selected for the current itinerary item, and becomes available for future use across the platform.

The enhancement improves itinerary management efficiency, reduces dependency on master data administration, and supports dynamic provider creation while preserving existing picklist-based functionality.

What's New

Ability to add new provider values directly from itinerary forms
New +Add action available on itinerary provider fields
Automatic creation of master data records from newly entered values
Automatic selection of newly created provider values
Immediate availability of newly added providers for future use
Support for dynamic provider creation without administrative intervention
Extension of functionality across all supported itinerary provider fields
Preservation of existing picklist functionality
Support for newly added values in APIs
Support for newly added values in reporting
Support for newly added values in exports
Support for newly added values in Customer Portal displays
Backward compatibility for existing integrations

Functional Summary

The enhancement removes the dependency on pre-existing master list values for itinerary provider fields.

When a required provider does not exist, users can create the provider directly within the itinerary workflow. The system automatically creates the corresponding master record, stores it within the appropriate provider list, and makes it immediately available for selection.

The feature introduces in-context master data creation while maintaining the existing picklist model and master data framework.

Key Capabilities

Dynamic provider creation from itinerary forms
In-context master data creation
Automatic master list updates
Immediate provider availability
Automatic selection of newly created values
Shared framework support across itinerary provider fields
Existing picklist preservation
Existing validation preservation
API compatibility
Reporting compatibility
Export compatibility
Customer Portal compatibility

Itinerary Provider Free Text Creation – Overview

Area	What this means for users
Flights	Missing airport providers can be added immediately
Hotels	Missing hotel providers can be created during itinerary entry
Restaurants	Missing restaurant providers can be added without administrative support
Ground Transportation	Missing transport providers can be created directly from the form
Events	Missing events can be created directly from the form
Master Data	New providers automatically become available for future use
Reporting	Newly created values appear in reports
Customer Portal	Provider values display exactly as saved

Configuration & Administration

Provider Management

No additional administrative setup is required.

The enhancement extends existing itinerary provider functionality.

Master data administration remains available and unchanged.

Users can now create provider values directly from itinerary workflows without requiring a separate master data update process.

Master Data Behavior

When a user creates a new provider value:

The system automatically:

Creates a new master data record
Stores the value in the corresponding provider list
Makes the value available immediately
Makes the value available to future users
Selects the value on the current itinerary item

The value does not remain local to the itinerary record.

User Roles / Permissions / Prerequisites

The feature is available to users with itinerary creation or itinerary maintenance permissions.

Access Level	What Users Can Do
Requester / Event Planner	Create and use new provider values
Event Manager	Create and maintain provider values during itinerary management
Admin	Continue managing master data and provider values
Customer Portal User	View provider values as stored

Prerequisites

User has access to itinerary management.
Itinerary item contains a provider field.
User has permission to edit itinerary information.
Provider field supports shared itinerary provider schema.

How It Works / User Flow – Step-by-Step

1. Open Itinerary Item

Navigate to:

Request Form → Itinerary → Add

Open an itinerary item containing a provider field.

The provider field displays the existing picklist values.

2. Search for Required Provider

Review the available provider values.

If the desired provider exists:

Select the provider.
Continue itinerary creation.

No change to existing behavior.

3. Add a New Provider

If the desired provider is unavailable:

Click:

+Add

Enter the provider name and other details if required.

Save the new provider.

4. Create Master Data Record

The system automatically:

Creates a new master record
Stores the value in the appropriate provider list
Makes the value available immediately

No administrative intervention is required.

5. Automatic Provider Selection

After successful creation:

The system automatically:

Selects the newly created provider
Populates the current itinerary item
Allows the user to continue itinerary creation

6. Reuse Newly Created Provider

Future users can:

Search for the provider
Select the provider
Reuse the provider across itinerary records

The provider behaves like any existing master list value.

Supported Provider Fields

The enhancement applies to provider fields using the shared itinerary provider framework.

Examples include:

Itinerary Type	Provider Field
Flights	Airport Provider(Arrival and Departure)
Hotels	Hotel Provider
Restaurants	Restaurant Provider
Ground Transportation	Ground Transport Provider
Events	Event

The implementation is schema-driven and not limited to a single field.

Future provider fields using the same framework can leverage the functionality.

Data Handling & System Behavior

Existing Picklist Support

Existing provider values:

Continue to exist
Continue to be selectable
Continue functioning without modification

No migration is required.

No existing master data is replaced.

Provider Creation Behavior

When a new provider is created:

Action	Result
User enters new value	Provider record created
Provider saved	Added to master list
Save completes	Provider becomes selectable
Current itinerary updated	New value automatically selected
Future users search	Provider available for reuse

Customer Portal Behavior

Provider values display exactly as saved.

Locations include:

Itinerary View
Agenda View
Customer Portal itinerary displays

No special formatting is applied.

No transformation is performed.

Reporting Behavior

Reports support:

Existing provider values
Newly created provider values

No reporting redesign is required.

Reporting behavior remains unchanged.

Export Behavior

Exports support:

Existing provider values
Newly created provider values

Export consumers can process provider values without modification.

Backward Compatibility

Existing integrations must continue functioning without modification.

The enhancement must not introduce breaking API changes.

Validation Rules

Existing validation behavior remains unchanged.

Required Field Validation

Provider fields continue to enforce:

Mandatory field validation
Existing required field behavior

Character Limits

Existing character limits remain enforced.

Existing Input Rules

All existing field validation rules continue to apply.

No validation relaxation is introduced.

Business Rules

Rule	Business Requirement	Purpose
Rule 1	Provider fields must support +Add functionality.	Allow users to create missing providers directly from itinerary forms.
Rule 2	New provider values become master data.	Ensure newly entered values are stored centrally for reuse.
Rule 3	New values must be immediately selectable.	Let users continue itinerary creation without delay.
Rule 4	Existing picklist values remain unchanged.	Preserve current master data and selection behavior.
Rule 5	Character limits remain enforced.	Maintain existing input quality and field constraints.
Rule 6	Required field validation remains enforced.	Ensure mandatory provider fields continue to be completed.
Rule 7	Customer Portal displays values exactly as saved.	Keep provider naming consistent for end users.
Rule 8	Reports support newly added provider values.	Include new providers in reporting outputs without redesign.
Rule 9	Existing integrations remain backward compatible.	Avoid breaking existing consumers and workflows.

Important Considerations & Limitations

Existing picklist functionality remains unchanged.
Existing master data management remains available.
Newly added values become permanent master data records.
Provider values are immediately reusable.
Existing validation rules remain enforced.
Reporting supports newly created values.
Exports support newly created values.
APIs support newly created values.
Customer Portal displays newly created values.
Existing integrations remain backward compatible.

FAQs

Why was this enhancement introduced?

To reduce dependency on master data updates and allow users to continue itinerary creation without waiting for administrative intervention.

Do new provider values become master data?

Yes. Newly added values are automatically stored as master data records.

Will future users be able to use newly added providers?

Yes. Newly created providers become available immediately and can be reused by all users.

Does this replace existing picklists?

No. Existing picklist functionality remains unchanged.

Are reports affected?

Yes. Reports support newly added provider values while maintaining existing behavior.

Does the Customer Portal support newly added providers?

Yes. Provider values display exactly as saved.

Support & Troubleshooting

If new provider values are not available after creation, verify the following:

User has itinerary edit permissions
Provider value was saved successfully
Master record creation completed successfully
Validation rules were satisfied
Character limits were not exceeded
Provider field supports the shared itinerary provider framework
No integration or synchronization errors occurred

When contacting support, provide:

Visit ID
Itinerary Type
Provider Field Name
Provider Value Entered
Timestamp of creation
Screenshot of the itinerary form
User role
Any validation or error messages displayed
Relevant API or integration details (if applicable)