-
- What's New
- Functional Summary
- Key Capabilities
- Flight Confirmation per Attendee – Overview
- Configuration & Administration
- User Roles / Permissions / Prerequisites
- How It Works / User Flow – Step-by-Step
- Data Handling & System Behavior
- Important Considerations & Limitations
- FAQs
- Support & Troubleshooting
Overview
This release introduces attendee-level flight confirmation number management within Itinerary Management, allowing requesters to provide and maintain a unique flight confirmation number for each attendee associated with a visit.
Previously, flight confirmation details were managed at a broader itinerary level. With this enhancement, a confirmation number can now be captured, updated, and maintained individually for each attendee, providing greater flexibility when attendees on the same visit have different flight bookings.
The enhancement improves travel coordination, increases visibility into attendee-specific booking details, and ensures flight confirmation numbers accurately reflect each attendee's travel arrangements.
What's New
- Flight confirmation number management at the attendee level
- Independent confirmation number for each attendee
- Ability to add or update a flight confirmation number for individual attendees
- Ability to remove a flight confirmation number for individual attendees
- Dedicated flight confirmation number field per attendee
- Flight confirmation number visibility within itinerary management workflows
- Support for different confirmation numbers within the same visit
- Enhanced attendee travel tracking
- Improved visibility into attendee booking details
- Attendee-specific confirmation number persistence across itinerary updates
- Individual attendee flight confirmation number auditability
Functional Summary
The feature allows a flight confirmation number to be managed independently for each attendee rather than treating all attendees as a single group.
Each attendee maintains their own flight confirmation number, allowing requesters to accurately reflect real-world travel arrangements when attendees book or modify flights at different times.
The system stores and displays flight confirmation numbers at the attendee level while maintaining existing itinerary management workflows.
Key Capabilities
- Individual attendee flight confirmation number tracking
- Independent confirmation number per attendee
- Support for attendee groups with different confirmation numbers
- Flight confirmation number visibility within itinerary workflows
- Attendee-level confirmation number persistence
- Individual attendee confirmation number updates
- Real-time confirmation number display
- Improved attendee travel management
- Support for varying travel booking timelines
Flight Confirmation per Attendee – Overview
|
Area |
What this means for users |
|
Attendee Management |
Each attendee maintains an independent flight confirmation number |
|
Itinerary Management |
Flight confirmation numbers can be managed without impacting other attendees |
|
Travel Tracking |
Attendee booking details become more visible |
|
Mixed Attendee Groups |
Attendees can have different confirmation numbers within the same visit |
|
Confirmation Number Updates |
Changes apply only to the selected attendee |
Configuration & Administration
Flight Confirmation Configuration
No additional administrative setup is required, and the confirmation number field is now a fixed system field that is specific to each attendee.
The enhancement extends existing itinerary functionality and becomes available automatically once deployed.
Existing itinerary permissions and attendee management permissions continue to apply.
User Roles / Permissions / Prerequisites
Flight Confirmation per Attendee is available to users with itinerary management access.
|
Access Level |
What Users Can Do |
|
Briefing Manager |
View and update attendee flight confirmation numbers |
|
Admin |
Manage attendee flight confirmation numbers and related configurations |
|
Standard User |
Access based on existing permissions |
Prerequisites
- Visit contains one or more attendees.
- Itinerary functionality is enabled.
- User has permission to manage attendee itinerary information.
- Attendee records exist within the visit.
How It Works / User Flow – Step-by-Step
1. Open Itinerary Management
Navigate to a visit containing attendees.
Open the Itinerary section.
Check the attendee checkbox and input the confirmation number.
2. Review Attendee Flight Confirmation Number
Locate the attendee list.
Each attendee displays their individual flight confirmation number field.
3. Provide a Flight Confirmation Number for an Attendee
- Select an attendee.
- Enter or update the attendee’s flight confirmation number.
- Save the changes.
After the update:
- The updated confirmation number shows for the attendee.
- The attendee confirmation number is reflected in Nexus Experience Hub.
- Other attendees remain unchanged.
4. Remove Flight Confirmation
Select an attendee with a confirmed flight.
Remove or update the confirmation status.
Save the changes.
After the update:
- The attendee no longer shows the confirmation number.
- Other attendees remain unaffected.
- Updated status is reflected immediately.
Data Handling & System Behavior
Attendee-Level Status Storage
Flight confirmation status is stored individually for each attendee.
The system does not apply confirmation changes globally across all attendees.
Updates affect only the selected attendee.
Status Independence
Each attendee maintains an independent confirmation lifecycle.
Examples:
|
Attendee |
Flight Confirmed |
|
Attendee A |
Yes |
|
Attendee B |
No |
|
Attendee C |
Yes |
Persistence
Flight confirmation status remains associated with the attendee record.
The system preserves attendee-specific confirmation information during normal itinerary updates.
Visibility
Flight confirmation status is displayed wherever attendee itinerary information is presented.
Users can quickly identify:
- Confirmed attendees
- Unconfirmed attendees
- Mixed confirmation scenarios
Important Considerations & Limitations
- Flight confirmation is managed individually for each attendee.
- Updating one attendee does not update other attendees.
- Multiple attendees within the same visit may have different confirmation numbers.
- Existing itinerary workflows remain unchanged.
- Existing global confirmation numbers are removed and added to each attendee.
- Confirmation information is retained at the attendee level.
Backward Compatibility for Itinerary Exports
Backward compatibility for existing itinerary exports is not automatically handled as part of this enhancement.
Any required updates to legacy or previously generated itinerary export formats must be completed manually to ensure attendee-level flight confirmation numbers are represented correctly.
FAQs
What is changing with flight confirmations?
Flight confirmation can now be managed independently for each attendee rather than being treated as a single itinerary-level status.
Can attendees on the same visit have different confirmation numbers?
Yes. Some attendees may be confirmed while others remain unconfirmed.
Does this change existing itinerary workflows?
Yes, the single confirmation number field for all attendees will be removed, and each attendee will have the same confirmation number for the itinerary.
Support & Troubleshooting
If attendee flight confirmation status is not displaying or updating correctly, verify the following:
- Attendee record exists
- Visit contains itinerary information
- User has itinerary management permissions
- Changes have been saved successfully
- Attendee data is synchronized correctly
- No validation errors occurred during update
When contacting support, provide:
- Visit ID
- Attendee Name
- Current Flight Confirmation Status
- Expected Flight Confirmation Status
- Screenshot of itinerary screen
- Timestamp of the update
- User role
- Any displayed validation or error message