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 also limit 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 which must first be activated in your Yesplan installation:

  • 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§

Financial Integrations§

  • In the settings for Cevi Export and Mercurius Export you 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 Data for Exports Grouped by Event and Event Group”) the description of the custom data field “Invoice Description” is renamed “Free Communication on Event”.
  • In Cevi Export (under the section “Mapping Data for Exports Grouped by Customer”) the description of the custom data field “Invoice Description” is renamed “Free Communication”.
  • In Cevi Export, for exports grouped per event and event group you can now also 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 Data for Exports Grouped by Event and Event Group”) the description of the custom data field “Purchase Order Number on Event” is renamed “Extra Information on Event”. This matches the field infoZone1 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 matches the field infoZone1 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.6§

  • ✨ Improvement: the default reports “Day Program” and “Compact Day Program” have been merged. The behaviour of the compact variant is now handled by a parameter. Additionally, a non-paginated variant has been added.
  • ✨ Improvement: in the Tessitura ticketing integration, it is now possible to enter the Tessitura production ID in a Yesplan input field instead of using a drop-down menu that lists all possible productions. This is a solution for Tessitura environments that have a large set of titles and productions.
  • 🐞 Bugfix: in the user preferences, the options for the “Always open event inspector on tab” drop-down menu were not translated.
  • 🐞 Bugfix: the condition to follow updates related to events or event groups in a certain location now only lists viewable locations and the “No Location” option is translated.

Yesplan 31.5§

  • 🐞 Bugfix (31.4 regression): the Excel Add-in could crash with the message “Dataviewparameters loading”.
  • 🔧 Technical improvements to Single Sign-on authentication.

Yesplan 31.4§

  • ❇️ New: in dataviews, you can now add filter conditions that combine multiple values in a single rule for the fields status(es), profile(s), location(s), labels and contacts.

    For example, until now you could only filter on multiple statuses using additional OR rules:

    • “Status” is ‘Confirmed’
    • OR “Status” is ‘Closed’
    • OR “Status” is ‘To be invoiced’

    You can now do this in a single rule, adding or removing any number of values:

    • “Status” is one of ‘Confirmed’, ‘Closed’, ‘To be invoiced’

  • ❇️ New: you can now set a condition to only follow updates related to events or event groups in certain locations.

  • ✨ Improvement: in the bookings tab of a contact inspector, a contact that is booked on an event group is now shown with both start and end date of the event group instead of only the start date. The creation date of the booking is now always shown in the list as well.
  • ✨ Improvement: adding, suspending, restoring and deleting users is now shown in Updates (to administrators only).
  • ✨ Improvement: the read-only calendar has been removed because it was almost never used.
  • 🐞 Bugfix: when adding or editing a saved query in a finder, the changes were sometimes not saved.
  • 🐞 Bugfix: the price of an ad hoc resource booking could be editable in the resource booking inspector even though the user had no permission to edit the resource booking in the event inspector.
  • 🔧 Technical improvements to the Tessitura ticketing integration.
  • 🔧 Technical improvements to Single Sign-on authentication.

Yesplan 31.3§

  • ✨ Improvement: when booking a unique resource, the number of unique resources per booking is now limited to 50. This prevents a performance issue. If you are faced with this limit, consider using a regular resource instead.
  • 🐞 Bugfix: in the task finder, tasks were not sorted correctly by date.
  • 🐞 Bugfix: when entering a negative number for a resource booking, Yesplan crashed.
  • 🐞 Bugfix: in the system settings, the API key of the (hidden) Yesplan Support user was listed.
  • 🐞 Bugfix: Yesplan could crash when trying to login with a single sign-on provider.
  • 🐞 Bugfix: in “System Settings” > “User Groups”, you need to double-click the name of a user group to edit it, but it seemed directly editable in the browser.
  • 🐞 Bugfix: in the event inspector, when overriding the price of a resource group or a resource set containing resources with different VAT rates, the layout in the VAT rate selector popover was wrong.

Yesplan 31.2§

  • ✨ Improvement: we changed how the Universe ticketing integration’s credentials are set up.
  • ✨ Improvement: the Tessitura “Access ID” can no longer be entered in the integration settings. It must now be entered by Yesplan support.
  • ✨ Improvement: the list of suspended users in “System Settings” > “Users” > “Suspended Users” is now paginated when your installation has more than 75 suspended users.
  • 🐞 Bugfix: deleted users and user groups were not indicated as such in the permission templates in the system settings.
  • 🐞 Bugfix: in Teamplanner, when using the action “Swap with Placeholder” or when dragging a booking from one human resource to another, resource bookings that were assigned via a custom data field of type “Resource Field” were removed from that custom data field.
  • 🐞 Bugfix: in the event inspector, Yesplan crashed if you entered a value with a / character when overriding a price for a resource set or resource group with multiple VAT rates.
  • 🔧 Technical improvements to opening attachments in the App.

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.