Skip to content

Yesplan 31, Apr 2024

The update takes place over several weeks:

  • You’ll be given notice of the date and time in Yesplan a week before the update.
  • Afterwards, you’ll receive another notification in Yesplan telling you that the update was successful.

Tip

At the bottom of this page, you’ll find the release notes for the additional updates in Yesplan 31.x.

Single sign-on§

In addition to signing in with a password and email address (or username), users can now also use their Google or Microsoft account to sign in to Yesplan.

In the system settings, you can determine which authentication methods are allowed on your installation. You can additionally restrict single sign-on to your Microsoft tenant or to a specific domain in your Google Workspace.

See Single sign-on for more information.

Remark

Single sign-on is a paid module that must first be activated in your installation of Yesplan:

  • Contact support@yesplan.be to have single sign-on activated.
  • Once the module is activated, you can get started with single sign-on.

Ticketing integrations§

  • Yesplan now also offers ticketing integrations with Activity Stream’s Exchange platform, through our Exchange integration.
  • Yesplan also now offers integration with Tessitura (ticketing software), through our Tessitura integration.

Financial integrations§

  • In the Cevi Export and Mercurius Export settings, you will now find both the description of a field and the technical name of that field as it appears in the exported XML file.
  • In Cevi Export (under the section “Mapping of Data for Exports Grouped by Event and Event Group”), the description of the custom data field “Invoice description” has been renamed to “Free Communication on Event”.
  • In Cevi Export (under the section “Mapping of Data for Exports Grouped by Customer”), the description of the custom data field “Invoice description” has been renamed to “Free Communication”.
  • In Cevi Export, for exports grouped by event and event group, you can now use custom data fields on the event for the Cevi fields extra communication and invoice description.
  • In Cevi Export, for exports grouped by customer, you can now also use custom data fields on the contact for the Cevi fields extra communication and invoice description.
  • In Mercurius Export (under the section “Mapping of Data for Exports Grouped by Event and Event Group”) the description of the custom data field “Purchase Order Number on Event” has been renamed to “Extra Information on Event”. This corresponds to the infoZone1 field in the XML export.
  • In Mercurius Export, for exports grouped by customer, you can now also use a custom data field on the contact for “Extra Information on Customer”. This corresponds to the infoZone1 field in the XML export.

Bugfixes§

  • The name of an undisclosed event is no longer shown in roster notifications and in the overview of changes in the Yesplan App.
  • In the history of a ticketing integration we sometimes showed the username instead of the name of the user. We now consistently show the name of the user.
  • In some cases, double-clicking the “Add User” button could result in two dialogs being opened.
  • When multiple users worked on the same permission template at the same time, it could lead to a duplicated template.

Minor Releases§

Yesplan 31.1§

  • ✨ Improvement: in the Tessitura integration, an automated nightly synchronization of the remote data fields on active published events is performed.
  • ✨ Improvement: in the Exchange integration, an automated nightly synchronization of the remote data fields on active linked events is performed.
  • 🐞 Bugfix: rapidly double-clicking the “Add” button in the “Add User” dialog could lead to breaking the step where the permissions are set.