- DATE:
- AUTHOR:
- SAP LeanIX Product Team
EAM weekly feature improvement & bugfix summary
The following feature improvements have been implemented, and bugs fixed in the past week:
Reports:
All empty rows and columns on Matrix reports are visible or removed correctly according to the setting of 'Hide empty columns/rows', regardless of previous visibility status changes.
Diagrams:
We've updated the version of draw.io, which our diagrams are based on. The latest draw.io version 22.0.8 introduces a range of fixes and exciting enhancements, including:
Updated and new icon sets for AWS, emojis, GCP, Salesforce
Export of diagrams in edit mode as WebP images
See the changelog on the draw.io GitHub for a detailed list of changes.
When data in the inventory or the Meta Model is removed, and a saved diagram with a view based on this data is opened, the diagram is shown without a selected view, and a message informs users about that.
Inventory:
Changes to certain relations in the inventory (e.g., update of their description) were logged in the audit trail with the wrong 'Path' value. Although it's not visible, relations between Fact Sheets are directed and, therefore, have a source and target Fact Sheet. When a relation was changed on a target Fact Sheet, the names of the Fact Sheets in the logged 'Path' were swapped (e.g., relUserGroupToApplication instead of relApplicationToUserGroup). We've corrected that behavior, so the names appear correctly in the audit log and the published webhook events. For webhook users, affected event types are
RelationDeletedEvent
,RelationUpdatedEvent
(for modifications of relation fields),RelationValidityFromChangedEvent
, andRelationValidityUntilChangedEvent
.
Surveys:
The survey response form fully considers users' update permissions configured in the Meta Model. When survey recipients lack the update permission on a surveyed Fact Sheet, they'll encounter a read-only status on the fields, denoted by a lock icon and accompanied by a tool-tip message.
Administration:
A bug was fixed where HTML content was not rendered correctly in warning messages for archived Fact Sheets and when editing a subscription role in the admin area.