Version 4.2
7 months ago
This update introduces a range of new functionalities on the CMDB_CI level, including dashboards, reports, and real-time indicators, along with improved rollup options, cost and KPI management, and significant updates to the Relationship Picker, along with bug fixes and nomenclature adjustments.
Introducing New Functionality
- CMDB_CI-Level Features: Cost management, KPI management, reference models, lifecycle management, and recommendations are now available at the CMDB_CI level.
- New Rollup Options: Added "Maximum" and "Minimum" rollups to show extreme values.
- Dashboards, Indicators, and Tables: Introduced new dashboards and reports, real-time indicators supporting fields on relationships in
cmdb_rel_ci
, and new usage and hosting tables at the CMDB_CI level. - Additional Features:
- Right-click "Jump to..." in the Relationship Picker for quick center element changes.
- Standards Lifecycle calculated field on
x_inpgh_upmx_portfolio_element
. - New suggested relationships to support end-to-end Enterprise Architecture use-cases.
Updates & Improvements
- Reports and Dashboards: Merged and cleaned up existing reports; updated Capability Map with further improvements.
- Renaming and Simplification: Renamed scripts and the "Task" table to "Project Task"; simplified and cleaned up the application menu.
- Relationship Picker: Removed asterisks for easier search; upgraded to SweatAlert version 9.4.3; updated suggested relationships to show both directions.
- Data Quality and Lifecycle: Changed Data Quality Business Rules priority to 200; simplified lifecycle stages; updated lifecycle colors and field styles.
Bug & Issue Fixes
- Relationship Picker: Fixed various issues, including incorrect relationship direction, hierarchy depth, and wrong relationship creation. Improved settings view to support large numbers of entries, resolved path extension problems, and addressed bugs causing relationships to be created incorrectly.
- Data Quality: Adjusted business rules priority; resolved problems with configured allowed/blocked relationships on Level 2.