This action now includes a warning that manually awarding points for item-based goals may result in duplicate points being earned if the same goal is later completed in the Attendee App.

Exhibitor Search component settings in the App Builder have a cleaner layout and clearer labels, making it easier to configure exhibitor information for the Attendee App. [Ref: AE-2052]
​

Terms of Use in the Attendee App (See also the Attendee App release notes.)

The Accommodation Group Inventory List report now includes an “Allocated” column. [Ref: PE-2498]

Renewing an expired API key would intermittently return a “Failed to renew API User secret” error, and deleting an API key was slow or unresponsive. [Ref: AE-2131]

Financial - Payment Type settings

If specific edits were made to payment values and/or credit card fees, payments couldn't be saved properly [Ref: AE-2085]

Presentations module - Session setup

The “Alias is required” error message was hidden behind tab headings when adding a session survey. [Ref: AE-2075]
​

Functions module - Function setup

If a function had a large number of seat allocations and a cancellation schedule applied, the function setup wouldn't save. [Ref: AE-2181]

Payable items in the Travel, Accommodation, Exhibition, and Sponsorship modules could be set to “charge to another contact” using the owning contact, which prevented the contact from being deleted even after the item was removed. [Ref: AE-2183]
​

The delete contact dialog didn't flag contacts assigned as a reviewer for a session, presentation type, theme, or sub-theme (which prevented contact deletion, with no clear error message). [Ref: AE-2187]
​

Presentation authors weren't included in search results when filtering by specific presentation details, such as paper status, theme, or keywords. [Ref: PE-2505]
​

The anonymize record option incorrectly required the same financial validations as the delete option, which prevented you from anonymizing records with existing financial history. [Ref: PE-2536]
​

If an email address contained a space after the text, rows in the data import wouldn't process correctly. [Ref: AE-2072]
​

If the Additional Email field contained multiple email addresses separated by commas or semicolons, contact records wouldn't import correctly. [Ref: AE-2073]
​
​

If the underlying gamification data contained invalid or missing contact information, EventStream Engage wouldn't display leaderboards, prize draws, or goals. [Ref: PE-2310]
​

If the message body contained a specific combination of commas and brackets across multiple lines, registration emails wouldn't send [Ref: AE-2045]
​

Deleted reports still appeared in the portal and couldn't be removed. [Ref: AE-2148]

If a template communication within a site referenced a brand from a different event, the interactive site wouldn't clone. [Ref: AE-2033]
​

If the "Pay Later" option was selected, a registration could occasionally be submitted with no content or items added to the record. [Ref: AE-2132]
​

Modern Theme only: the close button for the error summary banner didn't have a contextual accessible name for screen readers. [Ref: AE-2167]
​

Group discount codes configured for specific group sizes were displayed for all registrations in a group instead of only for eligible members. [Ref: AE-2178]
​

“No option selected” radio buttons in Travel components behaved as a single radio group when initially added, even if they were assigned to separate groups. (This prevented a “no option” choice being selected for both inbound and outbound flight sectors.) [Ref: AE-2189]

The attendee count indicator didn’t display for attendees or presenters in OnAir sessions. [REF: AE-2042]

If a Data Validation option was selected in the Target Group filter, the Attendee Information Sheet displayed an error and wouldn't generate. [Ref: AE-2147]

Rising Star Welcome emails sender addresses didn't match the authenticated domain. [Ref: AE-2180]