Release Notes
Last updated
Last updated
On this page you’ll find a summary of new features, enhancements, bug fixes, and other changes included in each software update. This documentation is intended to keep you informed of the latest improvements and how they may impact your use of the platform.
For insight into our release schedule for acceptance and production, please refer to our .
In control tests, the control details are shown in a dropdown field on the right side. The ID, Name, but also frequency, execution method, and description are available.
Because the testing done at the time of the actual testing is based on the control description that was valid at that time, the historic values are shown: the name, description, frequency and execution method as they were defined at that time of the control test.
Sometimes a test comment requires more space than available in the control test screen. Pop-up signs have been added which, when clicked, the text is displayed in a large pop-up.
Attachments shown per test step were abbreviated if the name was longer than ca. 25 characters. To improve the readability, a hover is added so that the full name can easily be checked.
A warning is displayed when clicking the "x" on an incident type for an incident type field that already contains data.
Files included in a Form result which is used to create an incident, are now included in that incident.
All users, even users without the role “Reporter”, who add an incident via a Form, will be registered as incident reporters.
Archiving an incident type results in users not being able to create an incident of this type anymore. In the workspace these fields belonging to the archived incident were hidden. Incidents that already have this incident type will show the archived incident type.
An incident administrator can archive an incident type via the standing data tab “Configuration”.
Users who are removed from an MOI still get a periodic notification about the MOI. This has been fixed.
In MOIs and Audit, for instance, the information about a document was not fully available, and the description was not visible. This has been fixed.
The financial impact for Gross and Net amounts were displayed as JSON (code), instead of numbers. With this change both variables are now displayed as numbers. They are still shown together in one column. This will be improved later to enable searching and ordering the workspace based on these numbers.
In Standing Data, in tab Configuration, you can specify which Email addresses receive a message whenever an incident of that type is created. However, saving these addresses for the default types “Databreach” and “Operational incident” was not possible. That has been fixed.
Predefined incident type names looked editable, but they are not. So now it is not possible to edit the names.
In the risks, the budget is shown associated with the organization where the risk is defined for.
If the budget-based risk scoring is active, in the workspace the Gross and Net financial impact is shown per risk.
Total Gross and Net financial impact are shown in the workspace, for now in 1 column. Therefore, ordering and filtering is not yet possible. This will be further improved later.
As an administrator, all sent mails can be viewed via an extra tab in the incident module, underneath the Standing Data.
If an incident is created and linked to a Risk or Control, that incident can also be found as a linked item in the specific Risk or Control. For Risks and Controls these incidents are shown in the existing page of linked events.
If an incident was caused by a third party or the third party was affected, the incident can now be found as a linked incident. The incident link can also show the relation if the “+” sign is clicked. The details of date occurred, due date, description, and caused by, or affected by are shown.
Date registered is now made available per incident in the workspace.
The import of one-sample testplans resulted in testplans without a sample instead of testplans with one sample.
While extending a task, the previous end-date was included in the extension period. If a task is planned for that specific day, the task would be created again, resulting in a double task in the list.
SVG Logo format is not accepted anymore by the system.
Notification email addresses for Incident types “Databreach” and “Operational incident” are not saved. Therefore, the mails to inform contact persons that a new incident of this type is created, were not sent. Now this has been fixed.
If no “Responsible” or “Assessor” is assigned, the error was not clearly indicated in screen when saving the incident: under assigned, users can be added. Now the user can easily see what is missing.
PowerBI reports fail for MoIs of the type “Incident”. PowerBI will be improved to be able to handle Incident MoIs.
Deleted Users used to be visible in the “Assigned Users” component. Now that has been fixed.
The fields “Completed by” and “Closed on” were always empty columns in Incidents workspace.
Root cause in use in an incident could be deleted.
We are introducing a new Incidents module which brings significant improvements over the current Events module, offering:
Greater flexibility
Easily create custom fields for each incident type, allowing full customization to match your organization’s needs.
Streamlined workflows
A single, standardized workflow for all incident types simplifies handling and tracking.
Enhanced financial impact tracking
Record financial impact per department and third party for improved reporting
New and improved fields
Includes a due date, support for Framework dimensions, and the ability to register third parties directly in incidents.
Improved collaboration
Discuss incidents directly within the incident page using built-in comments, enabling faster decision-making and follow-ups.
Event Creation
Once migrated, you will no longer be able to create new Events, but existing Events will remain viewable and editable.
Form Updates
Your existing forms used for Event creation will be automatically updated to create new Incidents.
Standing Data
All standing data from Events will be seamlessly transferred to Incidents.
LEI code
It is now possible to register the LEI code of a third party including a LEI code validity check. The LEI code is available in the workspace and API.
Audit sponsor
In an Audit, the Sponsor or Sponsors, can now be registered. The Sponsor could be, for instance, the initiator of the audit. The sponsor does not have any rights, not even view rights. In the document templates the field Sponsor(s) can be added.
Budget-based risk scoring
A new way of scoring risks has been made available. Budget-based risk scoring is the first set-up for this initiative. The purpose is to enable risk scoring based on an estimated financial impact in relation to an organizational budget.
This feature is still experimental. If you are interested, please submit a ticket in the Customer Portal.
Hyperlinks for public presets
It is now possible in the Browse presets overview to create a link to a preset. If the preset is public, this link can be shared with other users via mail or messaging tool for instance. Please be aware that this is only possible for presets that are made public.
User management - Role group removal does not lead to removal of the associated roles for the user
Role group removal did not lead to removal of the corresponding roles of the user. This issue has now been solved. After removing a role group for a user, the corresponding roles are removed for the user if no other active rolegroup for that user includes that role.
KRI - KRI restricted writer can't edit KRI datapoints
KRI restricted writer could not edit KRI datapoints
Audit - Unassigned Auditee cannot be requested to provide a document
All users with the role Auditee could be asked via a mail request defined in the Audit to supply information to an audit. However, only users assigned to an Audit have the rights to do so. In this release both have been aligned: only Auditees assigned to the Audit can be asked to add information to an audit.
