We've received requests from the IT Security teams at several of our client organizations to enforce an account lockout after some number of failed login attempts. Not all Clients have the same needs as to whether it should apply to end users, admin users, or both, and on how many failed attempts should be permitted. To that end, event hosts now have the option to enable a lockout after some number of failed login attempts for end users, admin users, or both. The number of login attempts before lockout is configurable and can be different for admin users versus end users. The admin user setting is on the back-end, must be configured by the MeetMax Support Team, and applies to all events. The end user setting is on the front-end, can be configured by any event host, and is established as a per-event setting. For both user types, an account lockout can be cleared by any administrative user on your account.

We've introduced an upgrade to end-user scheduling for unmoderated events which allows attendees to use a more graphical interface for scheduling meetings. This allows a User to choose a meeting time by comparing their own Calendar with their counterpart - and drag/drop the new meeting to a mutually available slot. Whether issuing a request, accepting a request, or editing an existing meeting - the user can now click the "Find a time" link which allows them to open a calendar interface. This calendar view will provide a shaded area for mutually avialable times, as well as a shaded area for times that the other meeting participant is unavailable, and a highlighted area for the meeting duration which you're attempting to schedule. This feature allows a user to more easily find a good time to meet in an event with lots of potential conflicts and overlapping availabilities.

PayPal announced back in 2021 that they were no longer accepting new users to the PayPal Website Payments Pro solution (also sometimes referred to as PayPal ""nvp-soap""). As a result we can't safely support this integration anymore and we will be formally removing support for it in an upcoming release. To replace it, we have introduced a new PayPal integration with the PayPal REST API solution. This is the actively supported Paypal Integration for business customers. It has all of the same feature functionality as our other payment processing integrations, but with a slightly different setup process which will be documented in our Knowledge Base.

We've implemented a new integration which allows event hosts to push corporate participation data from MeetMax into the forward-looking CorpAxe Calendar product. This allows really easy display of your events to key buyside clients. Establishing this connection requires a CorpAxe license and coordination with their team to give MeetMax the ability to send data to them on your behalf, as well as an additional fee to license the feature in MeetMax. But once all of these are in place you can say goodbye to hours of dealing with complicated Excel templates and manually transposing data, and then the wait in having those files then processed on the CorpAxe side. Drop us an email at sales@twst.com when you're ready to upgrade the marketing of your events to buy-side participants.

A few years ago we introduced the concept of a matrix field in MeetMax. This field type is one where you have a series of items with a standardized set of responses. For example, a field labeled Product Interests which lists out a series of potential products with a standardized response that indicates a timeline for purchasing those products (e.g. - 0-6 months, 6-12 months, 12+ months, not interested). This latest release now allows for a client to import values to a matrix field, whereas prior to this release this was not possible. Please refer to the Knowledge Base for more details on how to structure your data for importing to a matrix field.

For events which utilize our two-step approval registration, it's long been the case that some types of participants should be pre-approved while others should be subject to the two-step approval. This feature upgrade allows for event hosts to explicitly indicate one or more roles which should bypass approval in the event's Enable Features menu. Check out the Knowledge Base for more details on two-step approval registration.

If the event has been running prior to conflict management being enabled, it is possible to have overlapping scheduled items already. (Meetings, Presentations, Activities) This can make it difficult to switch on Conflict Management after the fact. Historically, we've provided separate reports for trying to help identify these conflicts for clean-up but we've now replaced all of those reports with one unified Overlapping Scheduled Items report to make it faster and easier. To locate this report navigate to Reports and then go to Meeting, Presentation, or Activity to locate the "Overlapping sheduled items" report. You will also be provided with a link to this report if you try and fail to switch on Conflict Management because of existing overlaps.

In recent years many companies have started utilizing Proofpoint and other email scanning services which effectively "click" the links in emails prior to them actually being opened, in order to determine if they are safe for consumption. Unfortunately this has led to some invitees being improperly shown as "declined" for an event even though a human being never actually clicked on that link. We've introduced a small update which will ensure that the "decline" response will only be triggered when a human being has clicked on the link but not when a "bot" has checked the page for security purposes.

Cancelled Meetings Reasons and Opt-Out Reasons. These are fields that clients have frequently asked us to update and in the past would have required some back-end hacks from the Support team. Now you can freely edit the options in these drop-downs yourselves.

This is a somewhat nuanced new feature which allows for an event configuration where there is a fully moderated meeting request/scheduling process but also the ability for end-users to message one another (either via the web-app or the native mobile app). The role restriction which is lifted in order to enable messaging also controls whether notifications are generated as a result of meeting request activity (add, edit, cancel). So what we've done is to introduce a new option in the Settings widget on the Meeting Requests page which allows an event host to "Supress end-user notifications". This ensures that no notifications will be generated when requests are added, edited, or canceled but that the end-users will still be able to message one another if they're otherwise permitted to do so.

We've introduced a very small tweak to the way that the checkbox works on the Meetings list where you track meeting attendance. Historically, the first click of this checkbox next to the name of a meeting attendee would result in flagging them as a no-show. More clients though use this feature to log actual attendance and not just the non-attendance exceptions. To help improve the ergonomics of this action we've simply changed the ordering so that the first click of this checkbox now indicates attendance, rather than non-attendance.

As part of our SOC 2 technical remediations we've been making upgrades to our database servers. Specifically, we've enabled db-level encryption at rest, as well as enabling TLS layer encryption for data in transit between the database and application servers. Finally, we've fired up a new server in a different geographic region to store offsite backups and also enabled encryption of the database backups.

Please note that Verizon has announced the BlueJeans video conferencing platform will be fully discontinued in February 2024. As such we are retiring support for this integration as of this latest release of our software. We will continue to run industry-leading virtual events on MeetMax utilizing our integration with the Zoom video conferencing solution and our partners at SummitCast.