The latest EventsAir release (Version 16.3.4) is due to be rolled out from Monday, February 16 and includes various improvements and resolutions.

You can now create logic rules based on the Primary Email address field in both Component Logic and Field Logic, with the same operator options as other text fields (for example "ends with" or "contains"). This will allow you to tailor attendee registration experiences based on email addresses!

All customers now have the ability to create API Keys (to use with the EventsAir public API) via the User setup screen. To find out more about the EventsAir public API visit https://developer.eventsair.com/. You can also read more in this article.

As part of our ongoing commitment to updating and improving EventsAir, we've replaced and upgraded some of our 'core components' to remove legacy dependencies and move to the latest .NET framework. We prepared extensively with testing and reviewing including automated end-to-end testing, manual validation and a gradual rollout of changes.

These upgrades are now complete. Our careful preparation meant there was no customer impact, yet maximum benefit. We thank you for your ongoing support as we continue to bring you reliable yet innovative event technology.

EventsAir users logging in with Single Sign-On (SSO) were still prompted for an access code even after authenticating via Entra ID. [REF: AE-1449]

Updating existing contacts via import caused all billing contact details to be overwritten with the “Billing Title” value. [REF: AE-1444]

Large agendas could fail to load on some mobile browsers. [REF: PE-1802]

Waitlisted registrations - A registration option with unlimited availability on a second page was incorrectly shown as “Full” if a waitlisted option was selected on the first page. [REF: AE-1119]

Page radio groups - Page radio groups allowed multiple selections when revisited from the summary page, preventing users from proceeding to payment. [REF: AE-1086]

Custom fields in functions - Contacts with two instances of the same function type, each with a custom field value, could not log in to interactive sites referencing that function. [REF: AE-1480]

Function fee types - Function fee types with number input could be edited after initial submission, even when set to not be editable. [REF: AE-1452]

Groups - The “Next” button was missing on the Group Registration page when a Group Contact with registered members accessed the site via auto-login and clicked “Edit Group.” [REF: AE-1494]

Groups - Group members could not successfully submit and pay for additional items if the Group Contact had previously submitted on the site. [REF: AE-1479]

Inventory Full - Items in interactive sites appeared as ‘full’ when an event was cloned with a different currency. [REF: AE-1497]

Logic - Users could not change the order of part-logic rules in the Contact component. [REF: AE-944]

Logic - Selecting an option in a dropdown field, with logic referencing another dropdown, prevented further progress on the site. [REF: AE-1502]

Payments/Multiple Contact components - Sites with multiple Contact components could not proceed to the payment processor if the first Contact component did not include either Last Name, Organization, or Email address. [REF: AE-1521]

Payments/Expired Discount Codes - The payment page would fail to load if a previously applied group discount code had expired. [REF: AE-1475]

Payments/required fields - Site visitors could proceed to checkout with EventsAir Pay without providing a last name, organization, or email address, resulting in an error. [A prompt now appears in the site builder if needed: ”EventsAir Pay needs a Contact component with Primary Email Address, Last Name, or Organization set as a required field.”] [REF: AE-957]

Payments/Re-setting or changing EventsAir Pay account - The payment screen was failing to load if the EventsAir Pay account had been changed or re-selected (usually in a cloned event). [REF: AE-1482]

Exhibitors/Payments with EventsAir Pay Stripe - Payments made using EventsAir Pay powered by Stripe on interactive sites linked to an Exhibitor Portal weren’t correctly recorded against the exhibitor’s contact record. [REF: AE-1043]

Registration Recovery/Radio buttons - Incomplete registrations could result in multiple radio buttons being selected in a group, preventing users from progressing. [REF: AE-1476]

Styling - Curved and Panel themes only - The 'No file chosen' placeholder text on document custom fields appeared white and overlapped the upload button. [REF: AE-1481]

Styling - Curved theme only - The Account Email and Confirm Account Email fields overlapped with placeholder text on the sign-in page when an attendee created an account for the first time. [REF: AE-1117]

Travel - Auto login tokens failed if a contact had two separate travel bookings with the same custom field in the same travel component. [REF: AE-1484]

Errors when submitting a meeting request (via the Meeting Diary App). [REF: AE-1447]

Analytics export emails were always sent from [email protected], causing delivery failures for clients using custom SMTP servers. [Export emails now correctly use the "Attendee Communication" sender address set in Event Preferences.] [REF: AE-1486]

AirCast - Attendees who left their browser open after a session ended were not automatically logged out. [Attendees are now automatically logged out after 8 hours of inactivity.] [REF: AE-1471]

AirCast - Attendees could not adjust or mute the main presentation audio when interpretation was enabled. [REF: AE-1313]

Exhibitor Analytics - Exhibitors could access details for all virtual exhibition attendees, even if the attendees didn’t visit that exhibitor’s stand. [REF: AE-1487]

Interactive Workshops - The 'Share Screen' button in embedded Zoom sessions did not function for attendees. [REF: AE-1123]

Live Q&A - Exporting Live Q&A didn’t work if questions or answers contained certain words or special characters. [REF: AE-1483]

Live Poll Results App - Live Poll Results App did not display final poll outcomes after the poll had ended. [REF: AE-1495]

'Theme' and 'Presentation Type' dropdowns in the Reviewer Portal were only showing options from the six most recently assigned papers. [REF: AE-1460]