Skip to main content
All CollectionsChangelog
8.36 – Feature Sprint VI
8.36 – Feature Sprint VI

Filter by multiple users and discard or archive multiple documents at once

Stefan Philipp avatar
Written by Stefan Philipp
Updated over a year ago

Added – new functions

Filtering by multiple users

With the new release, you can also enter multiple users at the same time in the filters of the overview tables created by, assigned to, edited by and executed by. Previously, the entry was limited to one user. This filter option is available under tasks, orders, rules, documents and reports.

Filtering by multiple users

Changed – improved functions

Remove multiple documents at once

From now on you can also discard or archive multiple documents at once. To do this, select the relevant documents and click the discard or archive option via actions. Please note, that you can only discard documents with the status new, review or draft. You can archive active documents and then restore them in the recycle bin under management.

Remove documents

Note: To use this function, you as a user must have the authorization for it via your role. You can set the permissions under functions using the system settings in the Editor. To do this, activate the remove multiple documents function under documents.

Remove multiple documents

Fixed – corrected functionality impairments

  • The video control user interface was not synchronized with the video player status.

  • The overview table for orders was not updated after more than 12 hours and had to be updated manually.

  • When setting up filters, it happened that more filters were assigned than defined in the filter setting.

  • When playing multiple videos, the next media was not automatically started when a video ended.

  • When a WebSocket connection or subscription threw an error, it was treated as if it was a 401 error, even if it was not.

  • The data submitted via webhook was incomplete.

  • When a user migrates from Azure to OIDC and deactivates the old Azure login, users who were still logged in with Azure could no longer log in.

(Publication: March 4, 2022)

Did this answer your question?