The latest EventsAir release (16.2.2) is recommended for all customers as it includes various issue fixes, improvements and security updates. It's due to be rolled out from Monday, September 8.
For more information on any of the items listed below, please reach out to our Support team.
For updates and changes to the EventsAir public API, please refer to the Developer Portal.
π What's new?
Attendee Single Sign-On (SSO) now with OpenID Connect
πAttendee Single-Sign On (SSO) now supports OpenID Connect. You can let attendees sign in after authenticating using their Microsoft/Google account, or their account in your Association/Membership management platform (or something similar). Talk to your Account Manager about using this feature.
Major Accessibility Uplift to Attendee App
π± This release marks completion of a significant accessibility uplift to the Attendee App, enhancing 60+ components to align with WCAG 2.2 standard. These are available in Modern Theme apps, in both the HTML5 app and when a keyboard is attached to a mobile device. An updated Accessibility Statement will be available shortly.
β
Smarter, More Accessible HTML Editing
π HTML editors throughout EventsAir now support copy-pasting text from external sources, such as Word or ChatGPT, while retaining formatting. We've also included a built-in Accessibility Checker which will help guide you to meet key standards.
πOther improvements
Attendee App - More frequent (and separate) updates
Our Attendee App releases are now separate from EventsAir releases, so both can be updated more frequently. For this release, Attendee App amendments and fixes are listed in this article AND in a separate article. From here on, there'll be separate articles for EventsAir version updates and Attendee App updates.
Attendee App - Updated themes
New Attendee Apps now default to Modern theme; Vertical and Mosaic themes are now deprecated. [REF: AE-1083; AE-1084]
Attendee Verification - data fetching
When using Attendee Verification, the registration site can re-fetch data for mapped Contact Fields when the site/page is re-loaded. This allows updates during the registration process, e.g. so an attendee can pay their membership fee and then be upgraded to member status.
ββFor customers who have the Attendee Verification feature, all new events (including cloned events) will have the updated sign-in page options available.
Email authorization updates
Microsoft is retiring basic authorization via SMTP early next year, so we have implemented the OAuth2 authentication flow for Exchange, enhancing security and reliability. More information here.
Security upgrades
Weβve updated core libraries across portals to enhance overall system security.
βοΈ Issues fixed
Communications Panel
Send Communication - sender email domain
If eventsairmail.com had been added to External Connections, any email domain could be entered in "Sender" details. [REF: PE-1114]Send Communication - Merge Docs
Choosing one Merge Doc then switching to another too quickly could load (and send) the content of the first one. [REF: PE-1160]
β
Express Actions Panel
Table Allocation
Automatic allocation wasn't working for rectangular tables. [REF: PE-970]
Deleting a contact wasn't removing table allocation. [REF: PE-1104]
Group members on a table were removed when others in their group were allocated to a second table. [REF: PE-1219]
Putting a host or Group Contact onto a table wasn't adding their guests. [REF: PE-914]
Guests weren't kept with host when automatically allocating tables. [REF: PE-1227]
Groups/guests weren't always kept together when bulk allocating tables if there were insufficient seats at one table for all of them. [REF: PE-1221]
Seats could become blocked unexpectedly. [REF: PE-1225]
Incorrect seating when manually updating table allocation. [REF: PE-817]
Reduction/cancellation of function tickets on a contact record resulted in their seat being allocated to "unknown", instead of cleared. [REF: PE-1224]
Seats marked as "blocked" weren't saving correctly. [REF: PE-971]
Table filter wasn't respected in automatic table allocation. [REF: PE-1075]
Online Panel
Attendee App
Display
The top and bottom of the display was cutting off on some Android devices. [REF: AE-1197]
Updated CSS is available for the Attendee App, including to address a visual focus issue in Live Polling/Live Q&A. [REF: AE-1010]
Notes
[Applies to new apps only]- Updated wording to reflect that notes exports are emailed as a Word doc, not an Excel doc. [REF: AE-1090]
Resource Gallery
An Attendee App with two or more Resource Galleries [with more than 21 presentations] only the first gallery loaded properly. [REF: AE-1179]
Static content
Links to documents in Static Content components weren't opening correctly. [REF: AE-937]
Interactive (Registration) site
Contact component
Billing Address "Country" field couldn't be changed back to default value. [REF: AE-1107]
Groups only - the Address "State" field wasn't retained for group registrations (prevented getting to Payment page). [REF: AE-1161]
Builder display error only - Contact fields in a cloned interactive site initially appeared blank in the builder, unless saved and re-opened. [REF: AE-1073]
Display
When viewed on iOS devices e.g. iPhone 11, footer images added to a Brand were being cut off by the bottom navigation bar. [REF: AE-1070]
Logic
If multiple contact components were added to site, AND specific Page Display logic was added for Group Contacts and Group Members: Group members weren't seeing discounts applied (even though Group Contacts did, and the payable amounts were reduced). [REF: AE-933]
In "Classic" theme interactive sites, logic based on contact custom fields wasn't working. [REF: AE-1162]
Payment Page
The "Enable Additional Payment" option could be checked in the site builder, even when relevant e-commerce account details had been entered (causing the payment option to appear blank). [Users are now reminded to add information if needed.] [REF: AE-935]
Sign-in page
Attendee Single Sign-On was creating a contact record was before the registration site was submitted (which prevented Attendee Verification from working correctly, including data being re-fetched). [REF: AE-1141]
Various panels
Autologin tokens in events linked to Contact Store with same name
If an event and (linked) Contact Store had the same name, trying to insert the event's registration site link would instead insert the Contact Store site link. [REF: PE-1241]
βDate selectors - Several date input selectors included a hidden default timestamp, which could create data problems. [Now, if the time isn't included in the selector, there's no hidden timestamp either.] [REF: PE-1118]
β