Users can create a linked message channel within the Messaging module from an incident. This channel is intended to inform others in the organization about the existence and progress of the incident. Comments on an action are now also visible in the app. Action statuses can now be changed with a single click on the incident dashboard and the incident detail page. It is possible to mark incidents as confidential.

Hotfix for correctly handling more precise GPS information

Only actions linked to incidents are shown on the incident dashboard. The incident dashboard displays actions first, followed by incidents. In the HRM integration, persons with unknown gender are also synchronized as unknown. The export of incidents has been decoupled from function roles with config rights.

Incident pages also show action responsibilities who are not CrisisSuite people Incidents can be merged again It is possible to indicate in an incident type that the alert must take on-call shifts into account

The pagination of the person list in the CrisisSuite App retrieves more than 1 page The PDF export of an incident also includes attachments, status updates, and actions Refreshing the edit page of a status update is possible again

Performance improvements: On the incident detail page, fewer questions are asked of the server when retrieving the incident form. As a result, uncompleted answers are now shown as dashes, for example, instead of the unselected options. Searching on the server has been simplified, resulting in faster results. On the dashboard, only incidents and actions for which the user has been directly assigned responsibility are displayed.

Actions, Status updates, etc. collapsed by default: all components containing nothing are collapsed by default; those containing something are open by default on the incident detail page. Filtering incidents: filtering on the incident list view now returns the correct results in the list view. Small input field for status updates: the field has been enlarged.

Hotfix for inability to log in with iOS

The Incidents module has received a functional and visual makeover.

Hotfix for not being able to see what the user is typing in the messaging channel

Hotfix for inability to log in with username/password and PIN.

Hotfix for not being able to download plans via their detail page

Security improvement based on penetration test finding

Manuals are now also available in the app via the hamburger menu on the dashboard

Hotfix for incorrectly displaying the incident form with an unanswered person question

System administrators can send an access token to Merlin's technical helpdesk; The entire module Plans has been given a functional and visual makeover. Both the web and mobile applications now support all plan functionalities; Incidents, like crises, have an incident phase.

Hotfix for difficulty logging in via SSO for function roles that do not lead to the Crisis dashboard.

The incident form is visible and can be edited in the CrisisSuite App

Hotfix: Alerts will come through silent mode again with correct phone permissions

Several security vulnerabilities have been fixed Locations can be directly added when creating an incident

Logging in with the CrisisSuite App now also requires 2FA, if 2FA is activated on the CrisisSuite environment. It is possible to request multiple relief requests for one on-call shift.

Wrongfully shown logo at the login screen has been removed

The implementation of OAuth2.0 between the app and CrisisSuite server has improved the security within the CrisisSuite App. This makes it necessary to open the CrisisSuite App once every twelve months, otherwise you have to log in again. On-call shifts are visible in the app. Relief requests can be created for scheduled on-call shifts. Outstanding relief requests can be accepted or rejected. Status updates can be added to an incident.

Underlying code on which the CrisisSuite App has been built is upgraded to their latest stable version.

- Fixes issue with deeplink on push notifications - Various minor improvements