Skip to main content
Release notes 2021

Release notes v21.28

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

In this week's version, we bring you the following additions and improvements;

What has been added?

  • Searching within the 'databases' page has been improved.
  • On the portal, it is possible to post a comment on a ticket.
  • The API now also returns linked clients and persons, linked to applications, certificates, databases and servers.
  • The API now translates the value of the 'Components -> Type' field.
  • Linebreaks within code blocks.
  • The timeline and (in the case of tickets) the request can now be exported to an XLSX file along for all relevant pages.
  • Within datasets, a select box with multiple values has been added as a field type.
  • Within datasets, it has been made possible to show or not show fields based on the values of other fields.
  • For persons, the 'Language' field has been added.
  • Management > Datasets > Schedules now includes the [Sort & Filter] option.
  • Date and Date/Time fields within datasets now also feature a date-time picker as was already in use for tickets, certificates and processes.

What has changed or resolved?

  • From now on, it is possible to click on the entire block of a notification (not the dropdown, but the dedicated page).
  • When searching within a dataset, a fatal error occurred when searching within a field with a '-' within the name.
  • Bookmarks sometimes led to the wrong page.
  • When logging in again from an expired session, a log entry was incorrectly saved (this was co-triggered by the password manager Bitwarden).
  • It was impossible to archive a datasets object.
  • Duplicate fields were saved in the 'History' tab.
  • The end date of a new ticket was overwritten on an error message.