Resolved an issue where users with portfolio management permissions could edit strategy network nodes when an Authorized User was defined but no Authorized User Group was assigned. In these scenarios, authorization checks were not applied consistently across object types. Authorization behavior for strategy network nodes has been aligned and users can now edit nodes only when they are explicitly authorized through the assigned user or user group, ensuring consistent access control across the platform.
The business question What is our vendor roadmap? has been revised to improve performance if there are a high number of contracts.
The captions of the indicators in the Cloud Assessment evaluation type have been aligned with the naming conventions used across the product to ensure a more consistent user experience. The indicator caption Does the app have peaks in the workload? has been changed to Workload Peak Frequency and the indicator Is the license eligible for cloud? has been changed to License Portability. In addition, the tooltip texts for both indicators have been revised and enhanced to provide clearer guidance and improve usability.
Error fixed regarding the Objective filter in the business question What is our strategic progress? Setting the filter now visualizes only the goals and strategic themes associated with the selected objective.
Performance has been improved for the business question Which contracts should we review? The report filter Exclude Predecessor / Successor Contracts has been changed to Include Successor Contracts and shows all existing successor contracts of the contracts displayed in the business question.
Applications with no defined start or end date caused an error in the business question What is the status of our rationalization plan? Applications without a start date and end date are now correctly interpreted as having an indefinite lifecycle.
The Class column has been added to the Data Source page of the business question What are our service costs? to identify which services are business services vs. support services.
The following data quality rules have been updated:
The resolution page for the data quality rule DQR-216: Define the metrics of the SLA opened a page that required further navigation to define the indicators of the service level agreement. Now, selecting the data quality rule opens a dedicated data workbench where users can define the Availability, Backup Frequency, Responsiveness, and Security Breach Alert indicators.
The data quality rule DQR-141: Lifecycle is missing targeting the class Component has been removed from the business questions What is our application roadmap? and What are our cloud focus areas? since this is not relevant to the analyses provided by these business questions.
The data quality rules used by the business question What are our service overlaps? have been refined to improve the relevance of its findings. The scope of DQR-220: Provider is missing has been extended to include objects based on the Business Service and Support Service stereotypes. In addition, the severity levels of two data quality rules have been adjusted: DQR-118: Start Date is missing has been changed to Warning, while DQR-217: Lifecycle is missing has been changed to Hint.
The target property Object State has been added to the data quality rule DQR-155: Object state must be Retired if end date has elapsed.
The following has been corrected regarding the Data Roundtrip functionality:
Resolved an issue where some business questions were missing in the Business Question. These gaps have been addressed and any business question included in the company's licenses can be selected, enabling administrative users to visualize the network of classes relevant to the selected business question. For reasons of performance, only one business question should be selected in the Business Question field.
The business questions What are our project overlaps? and Where are our project dependencies? have been updated to include the classes Business Service and Support Service as affected architecture classes.
The following data workbenches and reports have been changed so that they are only accessible by a user with an administrative user profile:
