Skip to main content
Release notes 2021

Release notes v21.30

Door 28 July 2021#!31Fri, 08 Jul 2022 15:51:03 +0200+02:000331#31Fri, 08 Jul 2022 15:51:03 +0200+02:00-3Europe/Amsterdam3131Europe/Amsterdamx31 08pm31pm-31Fri, 08 Jul 2022 15:51:03 +0200+02:003Europe/Amsterdam3131Europe/Amsterdamx312022Fri, 08 Jul 2022 15:51:03 +0200513517pmFriday=124#!31Fri, 08 Jul 2022 15:51:03 +0200+02:00Europe/Amsterdam7#July 8th, 2022#!31Fri, 08 Jul 2022 15:51:03 +0200+02:000331#/31Fri, 08 Jul 2022 15:51:03 +0200+02:00-3Europe/Amsterdam3131Europe/Amsterdamx31#!31Fri, 08 Jul 2022 15:51:03 +0200+02:00Europe/Amsterdam7#No Comments

This week's release includes the following updates / changes. As every week, we are pushing these to all SaaS environments tonight.

What's new?

  • The target date field has been added to the table of tickets. This means that it is now -if enabled- also exportable to Excel.
  • When customising e-mails via the actions, a Markdown-based WYSIWYG editor is now also shown.
  • In actions, a new trigger has been added 'User management > New'.
  • It is now possible to send custom headers with a webhook.
  • Through the API, you can now create and edit tickets in addition to reading. In addition, the same applies to datasets objects.
  • It is possible to save a generated e-mail (from actions) and add it to the relevant object/ticket (EML file).
  • When a user responds via the portal, a log item is now generated and there is a trigger that is fired.
  • It is possible within the portal to disable the ability to respond for both open tickets and completed tickets.
  • You can now use images in all WYSIWYG fields. However, here you have to take into account your audience's authorisations. If someone is not authorised for ticket attachments, for example, and you paste an image in there, they will not see the image.
  • In spaces, you can now also add a category to timeline items.
  • It is now possible to set based on which status or statuses a ticket is completed.

What did we adjust or fix?

  • Various 'notices'. These are alerts displayed in our developers' local development environments.
  • Deleted items were still in users' 'favourites'.
  • It was impossible to edit a Wiki article.
  • It was possible to open files (albeit via a diversion) for which you were not authorised.


From next week (version v21.31), the use of the api_key via URL will be dropped. As previously announced, you need to switch completely to authorising via a header (with Bearer token). Please contact support for assistance.