Skip to content

Yesplan 28, Mar 2022

The update is due in the next few 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 went well.
  • On April 7th, we organized a webinar about Yesplan 28. Watch the recording of the webinar!

Tip

At the bottom of this page, you will find the release notes for the additional updates in Yesplan 28.1–28.37.

Deprecated Functionality§

In the system preferences you will now find the deprecated functionality that will soon be removed or changed in Yesplan. You can still use this functionality temporarily, but we recommend switching to the new way of working as soon as possible. See Deprecated and Removed Functionality for more information. Below is an overview of the functionality that will change.

Automatic Change§

The following functionality will change automatically in Yesplan 28, but you can revert to the old behavior for now:

  • The keywords for contacts anycomment, anycontactinfo and anylabel have been removed from Yesplan.
  • Event and contact labels now appear in alphabetical order throughout.
  • The “Draft” mode is no longer available:
    • The “Draft” button is no longer visible in the top left of the event calendar.
    • Events with the status “Draft” no longer appear in dataviews or query results.

Tip

You can revert to the old behavior, but we recommend switching to the new one as soon as possible.

Quickly Change Manually§

The following functionality is still available by default in Yesplan 28, but we recommend switching as soon as possible:

  • The REST API packages custom data fields for remote data of type “Number” as text. The REST API can also send these values as numbers, but then you must first check your existing integrations and adjust them if necessary. See Types of Remote Data for more information.
  • When editing shifts and breaks in the Teamplanner, the permissions “Edit booking” and “Delete booking” are granted by the owner of the booking, but this owner isn’t displayed anywhere. Therefore, quickly switch to the new behavior: the creation, editing and deletion of shifts and breaks will then be determined by the “Book” permission of the human resource in question.

Tip

You can enable and disable this functionality in “System Settings” > “System Preferences” > “Deprecated Functionality”.

Deleted Permanently§

From now on, the comment field of a resource booking in the Teamplanner will be the system field “Comment” instead of the custom data field “tp_comment”. The latter field has now been removed from Yesplan.

General§

  • You can determine the order of your custom inspector tabs by dragging and dropping them in the system settings. However, the system tabs of Yesplan itself (e.g. “Info”, “Resources” etc.) always appear first in a fixed order.
  • The date picker has been updated throughout Yesplan:
    • The date picker has been redesigned.
    • You can now navigate to the current month within the date picker by clicking “Go to Current Month”.
    • You can select today in one click by clicking “Pick Today”.
    • If you click a custom data field of type “Date input” or “Date and time input” on a resource booking or a contact booking, the date picker will open on the month of the booking. Previously, this was only the case for events.
  • In the navigation menu, under “Help”, you will now find the full version number of Yesplan, e.g. “version 28.0”. In the past, we mainly communicated about the major releases (version 26, 27, 28), but not often about the minor releases (28.1, 28.2, 28.3). From now on, we will also list the changes in the minor releases on the major release page so that you’re always aware of the latest changes and bug fixes.
  • In the navigation menu under “Help”, you will now also find a link to our platform for online learning (English and Dutch).
  • We now offer ZIP files for report templates of Default Reports. Reports in this new format support multiple languages and regions.
  • The use of capital letters is ignored when using your email address to request a new password or to sign in:
    • The email address ‘Violet.Trudeau@yesplan.be’ will therefore be interpreted as ‘violet.trudeau@yesplan.be’, provided that the lowercase email address is unique in the list of users.
    • The email address with capital letters ‘Violet.Trudeau@yesplan.be’ will, however, be stored in Yesplan with capital letters. The capital letters are only ignored when requesting a new password or when signing in.

API§

  • When you request a dataview via the API and send parameters for labels or resource groups, you can now also do this via the ID of the label or resource group.
  • If you request a dataview via the API and enter a parameter for date or time, you’re no longer obliged to enter the time zone. Yesplan assumes the time zone of the installation by default.

Contacts§

  • The contacts finder now always combines the filter for the contact type (“People”, “Organizations” or “Contact links”) with the scope of the query.
  • If you suspend a user in the system settings, the linked contact will appear with a user icon and a red prohibition sign. See Resources and System Settings for more information on changes to the suspension of users.

Dataviews§

  • Dataviews remember sorting 🎉

    If you sort a dataview according to a certain column and then close it, this sorting will be applied automatically when you reopen the dataview:

    • You can sort according to a single column.
    • You don’t have to save the dataview to have the sorting remembered.
    • The sorting is personal: it’s remembered for every user who opens and sorts a dataview.

  • Do you want to protect a dataview from accidental changes? Then you can lock it from now on. A dataview is automatically locked when you use it in the parameter of a report. See Locking Dataviews for more information.

  • In dataviews for resources and resource bookings, you can now select an existing value from a drop-down menu in a filter for the field “Resource Group”.
  • It’s now possible to display the value of a custom data field for contacts in a single dataview column, regardless of whether the row is one for a person, organization or contact link. This also applies to the booking of a contact. See Custom Data Fields on Contacts for details.
  • In dataviews for resource bookings, you can now select an existing value via a search field in a filter for the field “Applied Price Definition”.

  • In dataviews for events, you can now display the times of specific schedule items in a column:

    • Select the description of a specific time of day if you want a separate column for that time, e.g. ‘Schedules’ > “Get-in’. In this case, the cells in the column show the start and end times for the get-in.
    • Only schedule items with a promoted description are available in the dataview. You can manage this list in “System Settings” > “Events” > “Schedule Descriptions”. See also Labels and Descriptions for more information.

  • In a column for a custom data field of the “Checkboxes” type, the selected values now appear in the order specified for that field in the system settings.

  • Are the start and end times shown and their descriptions identical for each event in an event group? Then, in dataviews, their values will also appear for that group from now on.
  • The teams of human resources now appear in alphabetical order in dataviews.

Events§

  • In the “Resources” tab of the events inspector, you can now also select a price definition at the level of the resource group “Miscellaneous” and override the price.
  • We have optimized the search for events and event groups to make it faster. This optimization applies to fields where the suggestion list searches for events or event groups, e.g. if you want to add an event to a group.
  • The rules have been refined for receiving updates on events and event groups based on their status or profile:
    • With the comparator “is exactly” you receive updates on events.
    • With the comparator “contains” you receive updates on events and event groups.
  • When swapping placeholders, you used to be able to select resources from the context menu for which you didn’t have the “Book” permission. That has been solved now.

Integrations§

  • From now on, you can also create custom data fields of the type “Remote data” for various data types:
    • That way, you can create fields for remote data of type “Number” for your ticketing integration.
    • If you export these fields from a dataview to an Excel file, you can perform calculations on them.
    • Do you want to convert existing fields to fields of the datatype “Number”? Then read the guide Types of Remote Data for more information.
  • You can now define multiple budget holders in Alfa Export and fill out fields for them separately.
  • In the settings for ticketing integrations and webhooks, the drop-down menus for custom data fields of type “Publication trigger”, “Remote data” and “Integration data” only contain fields of the correct type. That way, you can find the field you’re looking for faster.
  • Yesplan now also offers an integration with the Cevi accounting software, via our Cevi Export.

Permissions§

  • You can now choose to have the permissions for resource bookings depend on the “Edit” permission of the event on which they’re booked. Can a user edit an event? Then he/she can also edit the resource bookings. Resource bookings are still subject to the additional permissions for prices. See Definition of Permissions and System Preferences for more information.
  • The permissions for shifts and breaks in the Teamplanner have changed. See Deprecated Functionality for more information.
  • Can a user not see certain custom data fields because they are only on tabs they can’t view? Then, for this user, the values of these custom data fields will no longer appear in finders, exported files and updates. Values of prices will also no longer appear in updates for users without the “View” permission for prices:
    • For finders, these are dataviews and the individual finders (e.g. for events or contacts).
    • For exported files, these are CSV or Excel files that you export via a finder or a dataview.
    • For updates, these are specifically values that appear in the “History” tab and in the “Updates” item of the navigation menu. It only concerns fields that have been filled out from Yesplan 28 onwards. Do you also want to make older values invisible? Then you can ask support@yesplan.be to delete your entire history. To be clear: in that case, you delete every update ever and start again with an empty history in your installation of Yesplan.
    • An administrator can still see all prices and values in the history, finders and his/her export files. After all, this is necessary to make complete exports, e.g. for price adjustments.
    • The log file in “System Settings” > “Audit” > “Updates” will always contain these values and prices, for the sake of completeness. Only administrators can consult these files.
  • We have fixed various bugs relating to permissions in the Teamplanner. See Teamplanner for more information.

Resources§

  • The inspector for human resources now shows teams in alphabetical order in the selection menu and in the list of selected teams.
  • Are you creating a new price definition? Then Yesplan will no longer automatically use the name “New price definition”, but you can immediately enter a name yourself. As such, you need to follow the settings and names as defined in “System Settings” > “Resources” > “Price Definition Names”. See Labels and Descriptions for more information.
  • If you suspend a user in the system settings, Yesplan will no longer automatically remove the linked resource:
    • You can still adjust and book the resource.
    • The link between the user and the resource remains intact. The resource appears with a user icon and a red prohibition sign to indicate that the user has been suspended.
    • The link between the suspended user and the resource only disappears when you permanently delete the user.
    • If necessary, you can still mark the resource as inactive.
    • Did you suspend a user before Yesplan 28? Then the linked resource that was deleted at that time will still be restored if you restore that suspended user in Yesplan 28.

System Settings§

  • Suspended users:
    • If you suspend a user, the linked resource will no longer be automatically deleted. You can only delete a resource after the suspended user has been deleted permanently, but you can still mark the resource as inactive.
    • The link between a suspended user and the linked resource remains intact. The link with the user only disappears when you delete the user.
    • Suspended users and their linked resources and contacts appear with a user icon and a red prohibition sign.
    • Did you suspend a user before Yesplan 28? Then the linked resource that was deleted at that time will still be restored if you restore that suspended user in Yesplan 28.
  • Creating new users:
    • When you click “Add User” you don’t have to scroll to see the form for adding users.
    • When you create a new user, a message will appear if there are suspended users with the same or a similar name. You can then restore a suspended user directly from this notification.
    • When creating a new user, a message appears if an active user with the same or a similar name already exists.
    • When you create a new user, a message appears if there is a resource with the same name that you can link. From this message, you can then link the new user to the resource.
  • Can you not click the “Delete” action in the status, profile or role screens? Then you will get a better explanation why. When you hover the cursor over the action, we now also tell you where exactly in Yesplan you must change the use of statuses/profiles/roles to make it possible to delete them.
  • When importing events, you can now define the start and end time shown in the event schedule.
    • You can find more instructions in the template for importing events.
    • The option “Use Imported End Time as Displayed End Time” is no longer relevant during import and has been removed.
  • The custom data field “Publication trigger” is now also available for contacts, resources and their bookings, where you can use it in combination with webhooks.
  • It’s no longer possible to import or export custom data fields, blocks and groups.

Teamplanner§

The following bugs were fixed in Teamplanner:

  • You used to be able to swap or delete bookings on a human resource linked to a user even though you didn’t have the “Delete booking” permission for that resource booking.
  • You also had access to the “Edit booking” action of a human resource linked to a user when you didn’t have the “Delete booking” permission for that resource booking.
  • You had access to the “Repeat” action of a break or a shift when you didn’t have the “Book” permission for that resource.

Minor Releases§

Yesplan 28.37§

  • 🐞 Bugfix: an error occurred in the Excel Add-in when writing back a date in the format dd-mm-yyyy if the locale of Excel was set to “Dutch (standard)”.

Yesplan 28.35 and 28.36§

  • 🐞 Bugfix (28.29 regression): when dragging an event to another location in the event calendar, the “Edit Booking” permission was checked, but only the “Edit” permission for the event and the “Book” permission for the location were relevant.
  • 🔧 This release includes stability improvements.

Yesplan 28.34§

  • ❇️ New: the Themis integration has been improved:
    • The finder now also shows the Themis number and address of each search result.
    • You can now import organizations of type “Feitelijke vereniging”.

Yesplan 28.33§

  • 🐞 Bugfix: if you removed the value of a custom data field in the Excel Add-in, and the field became invisible in Yesplan before you wrote back the removal (e.g. because of changed status or location), then the value of the field was still removed in Yesplan when writing back.

Yesplan 28.32§

  • ❇️ New: the Generic Ticketing Module now also offers the Grant type “Client Credentials” for OAuth 2.0 authentication.
  • 🐞 Bugfix: in the Excel Add-in, an error appeared when you wrote an empty Excel table cell to Yesplan for a custom data field that wasn’t visible on the element in question.
  • 🐞 Bugfix: in the Excel Add-in, an error occurred if you refreshed a table while the AutoFilter was deactivated.
  • 🐞 Bugfix: the link to the manual was broken in the Dutch version of the Excel Add-in.
  • 🐞 Bugfix: in some special cases, requesting a new Yesplan password could trigger an internal error.
  • 🔧 This release includes stability improvements.

Yesplan 28.31§

  • ❇️ New: the Excel Add-in is now available publicly. See Excel Add-in for more information.
  • 🔧 This release includes stability improvements.

Yesplan 28.30§

  • 🐞 Bugfix: in Profit 22, AFAS changed the value “Overig” to “Non-binair” for the field “Geslacht”. As a result, there was an error in the mapping between AFAS en Yesplan, and contacts were no longer synchronized.

Yesplan 28.29§

  • 🐞 Bugfix: users were able to unlock an event in the tree view even if they weren’t allowed to do so according to their capabilities.
  • 🐞 Bugfix: users were able to move an event even if they didn’t have the “Edit” permission for that event.
  • 🐞 Bugfix: an internal error occurred when exporting an XML file in Mercurius Export if it used a “Unique sequence field” custom data field.
  • 🐞 Bugfix: the documention for the Generic Ticketing API didn’t mention that a location could lack a value and be <null> for events without a location.
  • 🐞 Bugfix: an internal error occurred when multiple users edited the same price definition at the same time. We now show the appropriate warning instead.
  • 🔧 This release includes stability and security improvements.

Yesplan 28.28§

  • ❇️ New: the Generic Ticketing Module now offers OAuth 2.0 authentication.
  • ❇️ New: if your installation counts more than 75 users, Yesplan will divide the table in “System Settings” > “Users” > “Users” into multiple pages, with a navigation by alphabet.
  • 🐞 Bugfix: Yesplan assigned an incorrect date to event groups when deleting one of their subgroups in the tree view. As a result, it was possible that events didn’t show up in dataviews.
  • 🐞 Bugfix: in the Generic Ticketing Module, mapped fields were sometimes not displayed correctly when they contained special characters.

Yesplan 28.27§

  • 🐞 Bugfix: the nightly sync of AFAS contacts failed if there were more than 30.000 contacts to synchronize.
  • 🔧 This release improves the logging of maintenance tasks and the Excel Add-in to improve the monitoring of errors.

Yesplan 28.26§

  • 🐞 Bugfix: an error occurred when adding an email address that contained characters outside the English locale.
  • 🔧 This release includes stability improvements.

Yesplan 28.25§

  • ❇️ New: Cevi Export now uses the Yesplan ID as ‘debiteurnummer’ and no longer requires a custom data field for it.
  • 🐞 Bugfix: Yesplan could time out when calculating duplicates for a contact in the background.
  • 🐞 Bugfix: in the system settings, an error occurred when selecting a value in “Where or When to Show” for an empty custom data block.
  • 🐞 Bugfix: the connection to the Themis integration could time out.

Yesplan 28.23 and 28.24§

  • 🐞 Bugfix: during Yesplan’s automatic nightly maintenance operations, it was possible that you were signed out automatically and unable to sign in again, especially if your updates were set to “Only Show Updates I Follow”.
  • 🐞 Bugfix: in the Teamplanner, the Day Planned Time counter showed an incorrect result for a human resource if the latter contained a booking with altered offset times that was copied from another human resource.
  • 🔧 This release includes stability improvements.

Yesplan 28.22§

  • 🐞 Bugfix: in some cases, the default report “Quote” showed the rounded price for a resource, even if its price definition didn’t contain a rounded price.
  • 🔧 This release includes stability improvements.

Yesplan 28.21§

  • ❇️ New: the resource group of a resource booking is now available in the HTTP API at /resourcebooking/{id} and /event/{id}/resourcebookings.
  • 🐞 Bugfix: if you suspended a user in the System Settings while they were signed in, they weren’t immediately signed out automatically.
  • 🐞 Bugfix: the Excel export of a dataview could show a time difference of one hour with respect to the original dataview for the field “End Date and Time”.
  • 🐞 Bugfix: an error appeared in Alfa Export when you tried to export on the level of the event or the resource group, and a price was overridden at a higher level (resp. at the event group and at the event/event group).
  • 🐞 Bugfix: an error occurred in dataviews if you added a parameter without a default value for certain fields.
  • 🔧 This release includes stability improvements.

Yesplan 28.20§

  • ❇️ New: the net price and gross price can now also be displayed per VAT rate in dataviews for resources and events, and requested in the HTTP API. In dataviews, the following fields have been added:
    • Actual Gross Price per VAT Rate
    • Actual Net Price per VAT Rate
    • Gross Price per VAT Rate
    • Net Price per VAT Rate
    • Planned Gross Price per VAT Rate
    • Planned Net Price per VAT Rate
  • 🐞 Bugfix: dataviews failed to open if the name of a column group was empty.
  • 🐞 Bugfix: clearing the altered name of a column in a dataview did not always reset it to its original name.
  • 🐞 Bugfix: the value selected in the date picker for the “Date” field of a resource only appeared in the field after closing the resource inspector and opening it again.
  • 🐞 Bugfix: Yesplan could slow down if you executed actions on event groups and update notification rules were applied to the actions in question.
  • 🔧 This release includes stability improvements.

Yesplan 28.19§

  • 🐞 Bugfix: under specific circumstances following a server maintenance, files in Yesplan attachment fields were not included in reports, or report generation failed.
  • 🐞 Bugfix: if you selected multiple resources in the resource finder and right-clicked one of them to create a new set using “Add to Set…”, then all selected resources were added to the set twice but the resource your right-clicked was added only once.
  • 🐞 Bugfix: if you selected multiple resources in the resource finder and right-clicked one of them to create a new set using “New Set…”, then you created a new set where all selected resources were added to the set except the one you right-clicked. From now on, the action “New Set…” always creates a new empty resource set.
  • 🔧 This release includes stability improvements.

Yesplan 28.18§

  • 🐞 Bugfix: in availability search, you were able to book an all-day event in a non-existent event group by first interrupting the autocomplete in the search field for groups and then clicking the “Book” button. This led to an internal error if the system settings stated that no users were allowed to add new schedule descriptions.
  • 🔧 This release includes stability improvements.

Yesplan 28.17§

  • ❇️ New: you can now filter on event labels in the (Compact) Day Programme report.
  • 🐞 Bugfix: some reports that retrieve a lot of events caused performance issues.
  • 🐞 Bugfix: an error could occur if you opened an event in the calendar while the user preference “Always open calendar on” was set to “previous working date”.

Yesplan 28.16§

  • 🐞 Bugfix: an internal occurred in availability search if you didn’t enter a schedule name while not being allowed to add new schedule descriptions.
  • 🔧 This release includes stability improvements.

Yesplan 28.15§

  • 🐞 Bugfix (28.14 regression): the menu for adding locations to the event calendar didn’t appear correctly if your installation didn’t have the Teamplanner module.
  • 🐞 Bugfix: you received a message that your browser wasn’t supported if you used Chrome on Chrome OS.

Yesplan 28.14§

  • 🐞 Bugfix: if your installation contained a lot of teams, you weren’t able to scroll through the entire list of teams when you clicked the ‘+’ icon in the Teamplanner.
  • 🔧 This release includes stability improvements.

Yesplan 28.13§

  • 🔧 This release includes stability improvements.

Yesplan 28.12§

  • 🐞 Bugfix: when exporting a file in the Cevi Export, some error messages appeared in English instead of Dutch.
  • 🐞 Bugfix: an internal error occurred if there was a mismatch between the type of a “Remote data” custom data field and a mandatory field it is linked to in the ticketing system (e.g. “Single-Line Text” and “Boolean” for the field “Closed”).
  • 🐞 Bugfix: in the (nightly) automatic retrieval of values from ticketing systems, an error occurred for fields of deleted events.

Yesplan 28.11§

  • 🐞 Bugfix: you were unable to import events with new schedule descriptions if users weren’t allowed to add new schedule descriptions.
  • 🐞 Bugfix: it was not possible to upload report templates if their filename contained non-Latin characters.
  • 🐞 Bugfix: an error occurred when you booked an ad hoc resource in a custom data field of the type “Resource field”.

Yesplan 28.10§

  • 🐞 Bugfix: an error occurred in the Teamplanner if you created a booking on a shift that starts after midnight and ends after the shifted day line.
  • 🐞 Bugfix: an error occurred in the Teamplanner when you dragged a shift (e.g. 13:00-21:00) to a day that already contained a break outside that shift (e.g. 12:00-12:30).
  • 🐞 Bugfix: in some cases, you could not upload the zip file of a report template because Yesplan didn’t accept its media type.
  • 🐞 Bugfix: the mapping of values from Ticketmatic to custom data fields of the type “Dropdown” didn’t work if these values contained commas.

Yesplan 28.9§

  • 🐞 Bugfix: the date picker didn’t open in the event calendar if your browser was zoomed in or zoomed out.

Yesplan 28.8§

  • 🐞 Bugfix: dataviews failed to open if they contained a number (e.g. “42”) as the name of a column group.
  • 🐞 Bugfix: Yesplan no longer warned about an unsupported browser when opened on a mobile device.
  • 🔧 This release includes stability improvements.

Yesplan 28.7§

  • 🐞 Bugfix: an error could occur if a ticketing integration requested information for an event that was just deleted.
  • 🐞 Bugfix: the date picker didn’t open when you clicked a custom data field of type “Date and time input” that you had just filled out.
  • 🐞 Bugfix: in a resource’s date field, the selected value didn’t appear immediately when you selected a date with the date picker.
  • 🐞 Bugfix: opening the “Permissions” tab in the event inspector could be slow if it contained permissions for many users or user groups.
  • 🐞 Bugfix: when your browser was zoomed out, creating or moving bookings in the day view of the Teamplanner could produce an error.
  • 🔧 This release includes stability improvements.

Yesplan 28.6§

  • 🐞 Bugfix: when you selected a date in a dataview filter, the date picker didn’t use the earliest possible year as defined in the system preferences.
  • 🔧 This release includes stability and performance improvements.

Yesplan 28.5§

  • 🐞 Bugfix: the context menu of an unavailability sometimes contained actions related to an event on the same day if you used the expanded view of the event calendar. Clicking one of these actions resulted in an internal error.

Yesplan 28.4§

  • 🐞 Bugfix: an error could occur during the update when migrating the data for the Alfa Export integration.
  • 🐞 Bugfix: if the field “Alfa Customer Code on Contact” was not filled out in the settings of Alfa Export, the export failed for events that have a deleted contact in the customer field.
  • 🔧 This release includes stability improvements.

Yesplan 28.3§

  • 🐞 Bugfix: an internal error occurred in the event calendar when you navigated to a week that contained so-called Hidden Events whose parent event group had been deleted.
  • 🔧 This release includes stability improvements.

Yesplan 28.2§

  • 🐞 Bugfix: if you clicked the link for resetting your user password during an upgrade of Yesplan, the link didn’t lead to the “Maintenance” page.
  • 🐞 Bugfix: an internal error occurred when you exported the search results in the global finder, which can be accessed via “Search” in the navigation menu.

Yesplan 28.1§

  • 🐞 Bugfix: a conflict occurred in the case of concurrent API requests.
  • 🔧 This release includes stability improvements.