Release Date: 27.10.2023
Release Components: GoCompliant Toolsuite
New Features
- 814 Assets: additional fields per Asset-Typ possible
The customer-specific additional fields can now be managed per asset type and the definition is taken into account during entry / processing.
Thus, different types can also be configured differently, analogous to the risks.
- 942 ERM: Derived net risks can be displayed in heatmap and exported
For risk assessments with mitigating factors and derived net risks, the heatmap can now also be exported to Excel and Word.
- 1007 CORE: Default values can be defined in the additional fields
Default values can now also be stored for the customer-specific additional fields. These are prefilled as defaults during data entry and can also be defined as type-specific. Advantage: Default values can be predefined and prefilled so that the user only has to intervene manually in case of deviations. Note: no default value is defined for all existing fields, so nothing changes for the user until the configuration is deliberately changed.
- 1013 ERM: Risiko Owner Refactoring
Risks can now also have several owners; as before, only the OU to which a risk belongs is mandatory. However, different roles / owners can now be managed, which is helpful in connection with the new information options. For example, a business and an IT owner can be managed per risk and supplied with information.
Small Enhancements
- 1003 IA: Issues can be captured from the risk
In addition to linking, it is also possible to capture an issue directly from the risk if issue tracking is enabled. Note: in this first version of the feature, the issue must allow capture from the enduser for this to work.
- 1001 IA: Improvements in the assignment of labels (separation of action & issue)
For example, the due date of the action can now have a different name than that of the issue. Type separated labels are possible on both levels.
- 1002 WF: Consistent email notification for owner changes (also 989)
If a risk owner is changed directly by the expert (without WF), an info is now also sent to the new risk owner. The system steps in the custom workflows now also send an email to the new owner (CC to the old owner if one existed) in case of owner changes.
- 996 IA: In the action type you can configure how the due date should be set on creation
By default it remains empty for all existing/new action types and must be filled manually as before. However, the admin can specify how many months from entry a default due date should be set initially. Calculation: current month end plus the number of months results in the suggested date.
- 1000 WF: It is now possible to control per WF type whether several workflows should be allowed for the same object or not
This prevents, for example, that an approval process for a measure is accidentally initiated by two different users in parallel.
- 1004 IA: Improved information mails (to linked owners)
1) An issue owner is now informed by default when individual actions for his issue are closed (also applies to linked objects).
2) If required, a risk owner can be informed via custom workflow when actions / issues linked to his risk are closed.