Yesplan 27, Jul 2020

Good to Know§

A few of the changes could make Yesplan behave differently:

In dataviews, the filter for custom data fields of the type “Checkboxes” has changed. We recommend that you check existing dataviews with this filter after the update and alter them if necessary. See the release notes on dataviews for more information on the new filter.
From now on, the keyword for all custom data fields in the query language must match the keyword in the system settings. Previously, you could choose between a manually entered keyword and the keyword that Yesplan generates automatically. If a saved query goes wrong, it’s best to check that the keyword matches the one given in the system settings.

In your User Preferences, you can now specify which tab appears by default when you open the event inspector.
The events finder has been updated:
- Looking up events is quicker.
- You can click through to the event inspector or the event’s position in the event calendar.
- The finder shows the event or group’s position in the event structure.
- You can export the list to Excel.
- See Events Finder for a full summary of the options.
Yesplan now requires you to choose a strong password. When you enter a weak password, you’re given tips on how to make it stronger. See User Details for more information.
At the top of the “Permissions” tab in the event inspector you can now see the permissions that are the most relevant at that time (e.g. for a specific status). If these permissions don’t differ from the event’s default permissions, the latter appear. You can add the permissions for a given status at any time through a drop-down menu. See Permissions for more information.
From now on, fields that are read-only and can’t be edited in inspectors appear as text to improve legibility.
The “History” tab in the event inspector will no longer show an update if:
- The event took place at least two years ago.
- And the action that triggered the update was executed more than two years ago.
You can still download the complete list of updates per year in “System Settings” > “Audit” > “Updates”.

You can now activate roster publication per team. See Using Roster Publication for more information.
In Yesplan’s User Settings, you can specify whether you want to receive email notifications about changes to your roster. Until now this was only possible in the Yesplan App.

Once you have created a numeric input field, you can specify whether it should appear as a percentage: use the “Show as Percentage” checkbox in the “Values” column.
When you delete a predefined value for a custom data field of the type “Checkboxes” or “Dropdown” in the system settings, the value will appear as a prohibition sign in Yesplan if it had already been selected (for an event, for example). This is Yesplan telling you that although the value has been selected, it’s no longer set as one of the current values for the field in the system settings. See Editing Checkboxes and Dropdowns for more information.
You can now assign a type to custom data fields for integration data: “Single-Line Text”, “Multi-Line Text”, “Number”, “Date”, “Time”, “Date and Time”, “Single Option”, “Multiple Options”. These fields can’t be edited by users in Yesplan. See Types of Custom Data Fields for more information.
From now on, custom data fields for integration data can be used by webhooks. You can use all new data types.
You can now retrieve the keyword for custom data fields easily in an inspector by holding down Ctrl+Alt (Windows) or Ctrl+Option (macOS): when you hold down the keys, the field label changes to the keyword. If you want to copy the keyword, then click the label while holding down these keys.

The query language now has the scope event_or_group: the query event_or_group:name:Othello returns all events and groups with the name ‘Othello’.
The query language now has a new keyword dateafter for the scope event, group, event_or_group and production, which can be used to search for events taking place on or after a given date.

Naming and concepts have been updated to accommodate event label suggestion lists, contact labels, names for price definitions and descriptions of schedule items. If users enter descriptions of schedule items manually, you can set Yesplan to make sure that they aren’t automatically directed to visible suggestion lists. See Labels and Descriptions for more information.
You can now download via “System Settings” > “Audit” > “Updates” an annual log file containing all Yesplan element updates. See Audit Updates for more information.
“System Settings” > “Audit” no longer offers statistics in relation to tasks and prices.

In dataviews, custom data fields of the type “Checkboxes” now behave differently:
- When you choose the “contains” or “does not contain” comparator in the filter, you can select a filter value from a drop-down menu. In other words, you now search for the entire value, not a part of it.
- Your can use the “is empty” comparator in the filter for checkboxes for which no value has been selected.
- The different values can appear separately in a column in the dataview. You can filter for these values with the comparator “is selected” or “is not selected”.
The resource bookings dataview now also contains the following fields:
- “Prices” > “To Be Billed?”
- “Prices” > “Billable to”
- “Prices” > “Billable Units”
- “Prices”>”Actual Billable Units”
- “Prices”>”Planned Billable Units”
- All fields relating to the “Applied Price Definition”
In dataviews for events and event groups, you can now call up detailed fields per resource group under “Prices per Resource Group”.
The list of dataviews created now shows the scope (“Events”, “Resources”, “Resource Bookings” etc.) beside the dataview title.
In events dataviews, the event labels are now sorted correctly.
You no longer save a new dataview automatically upon creation. In other words, to save new dataviews you will need to click “Save Changes” explicitly.

When you call up the attributes VAT Rate, margin and actualMargin via the dataviews API, the values returned are now numbers instead of strings. Instead of the string ‘-20%’ the API now returns the number ‘-20’. However, for the attributes discountPercentage and actualDiscountPercentage the API still returns a string.
If default parameters are defined for a dataview, you no longer need to send them with a call to the API.

The documentation for Ticketmatic 2 has been omitted from the manual as our customers have switched to Ticketmatic 3.