In this week's release, we are bringing the following changes and updates to our SaaS environments;
What has been added?
- Within Tickets, it is now possible to filter by organisation (of the submitter) and (if enabled) supplier.
- The 'Ticket number (supplier)' field is now also searchable (if enabled) via the general and inline search bar.
- Wiki articles can now have tags.
- The 'status', 'category' and 'tags' fields are now also stored as 'ref fields' and are searchable.
- Datasets now also show a paperclip on linked documents.
- Certificates now have components.
- From now on, components will only be visible if you are authorised to do so. This means that by default nobody is authorised to do so. This applies to applications, certificates and servers.
- For tickets, it is now possible to send an e-mail to multiple addresses. The e-mail addresses must be separated from each other with a ';'. Example: "[email protected]; [email protected]" etc..
- From now on, wiki articles will have a 'Wiki number'. This is initially pushed with a format of 'W${count}'. This means that the numbering starts at 'W0001'. Of course, you can change this via admin (new option).
- For datasets, the primary title is now also shiftable from position within the table. Note: possibly this column is initially invisible. The column can be reinstated by adding it to the table again.
What have we changed?
- Besides several minor changes, we moved the 'Need help?' button to the personal menu. This has made the header more uncluttered.
- The 'Chamber of Commerce number' and 'Client number' fields have been moved within organisations.
- The 'Send via e-mail' checkbox is now disabled by default when creating a new ticket. This is because it is also (still) impossible to send an e-mail directly during creation.
What have we solved?
- Email addresses with spaces caused problems and prevented emails from being sent (tickets).
- The 'Email address' and 'Subject' fields were not hidden when clicking [Cancel] on a ticket.
- Various other minor bugs.
API
Please note that within the API, some things are going to change. We are going to perform authorisation based on headers. This means that the new (safer) methodology is going to change compared to the existing one.
The new method works by sending the token as a 'Bearer' in an 'Authorisation' header. This applies to GET, POST, PUT, PATCH and DELETE.
If necessary, contact support for help or more information.
Per July 28 we no longer support the old method of authorisation. So you should have changed any links to our API before that date.
