Ga naar inhoud

Yesplan 31, apr 2024

De update vindt plaats gedurende een periode van enkele weken:

  • Je krijgt een week voor de update een melding in Yesplan met de datum en het uur.
  • Je krijgt na de update opnieuw een melding in Yesplan om te bevestigen dat alles goed verlopen is.

Tip

Onderaan deze pagina vind je de release notes voor de bijkomende updates in Yesplan 31.x.

Single sign-on§

Naast het aanmelden met wachtwoord en e-mailadres (of gebruikersnaam) kunnen gebruikers voortaan ook hun Google of Microsoft account gebruiken om aan te melden in Yesplan.

In de systeeminstellingen kan je bepalen welke authenticatiemethodes toegelaten zijn op je installatie. Je kan single sign-on bovendien beperken tot je Microsoft tenant of tot een specifiek domein in je Google Workspace.

Zie Single sign-on voor meer informatie.

Opmerking

Single sign-on is een betaalde module die eerst geactiveerd moet worden in je installatie van Yesplan:

  • Neem contact op met support@yesplan.be om single sign-on te laten activeren.
  • Eens de module geactiveerd is, kan je aan de slag met single sign-on.

Ticketing integraties§

Financiële integraties§

  • Bij de instellingen van de Cevi Export en de Mercurius Export vind je voortaan zowel de beschrijving van een veld als de technische naam van dat veld zoals het verschijnt in het geëxporteerde XML-bestand.
  • In Cevi Export (onder het gedeelte “Gelinkte gegevens voor exports gegroepeerd per evenement en evenementgroep”) is de beschrijving van het customdataveld “Beschrijving factuur” hernoemd naar “Vrije mededeling op evenement”.
  • In Cevi Export (onder het gedeelte “Gelinkte gegevens voor exports gegroepeerd per klant”) is de beschrijving van het customdataveld “Beschrijving factuur” hernoemd naar “Vrije mededeling”.
  • In Cevi Export kan je voor exports gegroepeerd per evenement en evenementgroep voortaan ook customdatavelden op het evenement gebruiken voor de Cevi-velden extra mededeling en omschrijving factuur.
  • In Cevi Export kan je voor exports gegroepeerd per klant voortaan ook customdatavelden op het contact gebruiken voor de Cevi-velden extra mededeling en omschrijving factuur.
  • In Mercurius Export (onder het gedeelte “Gelinkte gegevens voor exports gegroepeerd per evenement en evenementgroep”) is de beschrijving van het customdataveld “Bestelbonnummer op evenement” hernoemd naar “Extra informatie op evenement”. Dit komt overeen met het veld infoZone1 in de XML-export.
  • In Mercurius Export kan je voor exports gegroepeerd per klant voortaan ook een customdataveld op het contact gebruiken voor “Extra informatie op klant”. Dit komt overeen met het veld infoZone1 in de 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.