Release 9.39.0

Release Date: 27th April 2025

Status: Released

New Feature

Added Password Reset Enforcement to Security Settings

A new option has been added to the security settings to enforce periodic password resets. This setting is disabled by default but can be enabled and configured in the Settings > Security tab for Trusted Support and Owner users.

Different password reset periods can be set for various user types; for example, "Privileged" users (like Owner and Trusted Support) can be required to reset their passwords every 30 days, while "Standard" users (like Portal and Admin) can be set to 90 days.

If a user's password is nearing expiration, a non-blocking banner will appear at the top of the portal, reminding them to update their password while still allowing them to use the portal.

If a password has expired completely, the user will be required to change their password before they can continue using the portal.

Added support for custom Vendor Lead Email from domains

You can now configure a custom Vendor Lead Email that will allow lead capture emails sent from vendors to come from this specific domain rather than the default event Email Sender ID.

This feature can only be configured by Jomablue and is designed to create a clear distinction from other event communications, preventing vendors from simulating the event organiser by using similar content in their email template. 

Vendor Organisation UIDs are viewable and editable in the portal

Vendor Organisation UIDs can now be viewed in the portal, displayed below the Vendor's name in the Vendor Detail view. Trusted-Support users can edit these values by clicking on the UID (or the hyphen if no value is present). A modal will appear warning users of the potential impacts of this action, and they must confirm their intention before saving the new value.

Session Organisation UIDs editable in Session Detail

Session Organisation UIDs are now visible in the Session Detail View and can be edited by trusted-support users. Similar to Vendors above, but in Session, editing requires users to check a box in a modal that informs them of the consequences of changing these Organisation UIDs.

Improvement

Faster People Searching

Searching for people in events is now faster than ever, including events with up to 50,000 people records. This improvement applies to portal searches and the Omnia admission mode search, with testing covering up to 100,000 people records.

Registration Localisation Label Sets moved to instance settings

Registration Localisation Label Sets have been moved from Registration > Configuration to the Settings tab in the portal. They can now be found under Organisation Settings > Localisation.

Improved Long Event Name Formatting in the Events List

The display of long event names in the Events List has been enhanced to avoid clashes with event images.

Updated Vendor Portal Content

The Vendor Portal UI.

Preloader Added to Portal Insights Welcome Text

To improve user experience on slow Internet connections, a preloader has been added to the Insights welcome text, ensuring it loads gracefully instead of displaying placeholders.

Known Defect

TOTP Reset User Issues Fixed

Resolved a problem where users could become stuck after a TOTP reset by an Owner or Trusted Support user (e.g. if that other user needed to re-register their TOTP). Now, those users can successfully register their new TOTP.

Importing Sessions with long names now flags as an import error.

Improved the handling of long session names upon import.

Duplicate Event modal no longer allows negative number input

The "Target" field in the Duplicate Event modal now prevents negative or zero input; the target must be at least 1.

Sessions now require a Location when being imported

Previously, the system did not properly validate session imports regarding location. A location is now a required field during the import process, and the system will display an error if a location is not present.

Improved portal login form behaviour

The portal login form would sometimes show a blank page if the user was experiencing a poor internet connection or if the user awoke their laptop from sleep and attempted to reload the form before the connection was established.

Additionally, if the user was logged out due to inactivity, the form would not load correctly. Now, a spinner will appear if the connection is poor, and an appropriate message will be displayed if the internet cannot be reached at all.