Demo of the New Features
With the brand-new dataviews you make your own customized overviews!
A dataview is a ‘report’ in which you call up specific data about events, resources or contacts and organize them in a table. For example, you can make a list of all events in a certain period with their name, date, location, start time, etc. Dataviews are also flexible because you determine:
- which fields are shown, whether they are system fields or custom data fields
- the order of the fields as columns in the table
- which events, resources or contacts are shown because you can add and combine filters
- what users can search for in your dataview via parameters
- who can view, edit or delete your dataview
You can also export dataviews as Excel files.
You can read all about it in the dataviews manual.
Changing Date or Location of Events
From now on you can quickly change the date or location of events without having to drag the event in the calendar. You simply adjust the date and/or location in the popover or the event inspector. This is very handy when moving an event far into the future.
In the calendar you can also use the “Move” action from the context menu to quickly adjust the date or location in the popover.
Please note that the “Cut” action was removed from the context menu; you can achieve the same effect by copying and pasting an event first and then deleting the original. But take into account that a copy of an event will not contain certain data, such as integration data that is uniquely linked to one event (e.g. ticket integrations) or the data that was entered on the event group (if the copy is not pasted in that same group).
Protection of Date Decorations
From now on date decorations can only be edited in the calendar by administrators. If you don’t want this protection, you can change it under system preferences so that all users can edit date decorations.
Externally Accessible Files
By default, attachments and other files in Yesplan can only be accessed by people who have a Yesplan username and password. From now on files can also be made accessible externally. In that case, everyone who has a link to the file can open the file without signing into Yesplan first.
A central overview of all externally accessible files was added for administrators, with the possibility to turn off that external accessibility per file if desired.
- When deleting report templates or generated documents, confirmation will be asked from now on.
- Unavailabilities in the calendar will also be shown from now on if a filter is used, irrespective of the filter settings.
- After deleting a ‘unique’ resource, all (future) bookings of that resource will be indicated as a conflict from now on. Conflicts were shown if insufficient regular resources were available, but this has now been corrected for unique resources. During the booking a warning will now appear stating that the resource was deleted.
- Under system preferences you can set whether you want to use a comma or semicolon as punctuation when exporting to CSV files.
- It’s no longer possible to convert custom data fields that are input fields into text fields or vice versa because they are not completely compatible and data could potentially be lost during the conversion.
API and Integrations
- From now on an administrator can view detailed error notifications in the history of an integration when clicking on a button that calls up external data, for example when refreshing ticket statuses in the event inspector.
- In the generic ticketing integration API from an integration you can send a set of mappings for the drop-down menu of that integration in Yesplan.
- The IDs of external contacts in Yesplan (from AFAS Profit or CIPAL Themis) can now be called up via the Yesplan API and via dataviews. The field is called “Origin System ID”.