Weekly feature improvement and bugfix summary

The following feature improvements have been implemented, and bugs fixed in the past week:

Inventory, Surveys, To-Dos

• In the new fact sheet creation form, you can now add people as subscribers by simply entering their email addresses, even if they have not yet been invited to SAP LeanIX. This makes it easier to involve future users right from the start.

  

• Fact sheet subscribers who have not yet been invited to the SAP LeanIX workspace can now be distinguished from active users in the subscription list of the fact sheet. Such users, called 'Contacts,' show with a gray font color and an invite button next to their names. This makes identifying them as survey respondents who didn't receive a notification possible and sending invitations to them easier, streamlining the process of bringing them into the workspace for full access.

  

• We have fixed an issue that prevented users from viewing a fact sheet if they didn’t have permission to read its tags due to subscription-based read permission for tags.

Diagrams

• The filtering behavior in diagrams has been improved to ensure that drill-down containers remain visible while their contents are being filtered. A container will only disappear if the applied filter removes all fact sheets inside.

Architecture Decisions

• A new 'User Component' is now available for architecture decision templates. Adding it to a template enables decision creators to search for and select users via a dropdown within the decision. This allows for easy assignment of users as decision owners, approvers, meeting participants, or any other relevant stakeholder roles.

Portal

• Users can now search for fact sheets in portals using aliases in addition to display names and descriptions, making it easier to find relevant information using familiar or alternative terms. Admins can configure this option when setting up portals.

Integrations

• The integration with ServiceNow supports matching rules that can be configured for both synchronization directions. Mismatches in naming conventions between the systems can lead to duplicate fact sheets for the same items. To prevent this, admin users can define how the name of IT components is constructed and used to find existing items in the target system.