EAM weekly feature improvement & bugfix summary

The following feature improvements have been implemented, and bugs fixed this week:

Inventory:

• In line with the other search capabilities in the inventory, results in central full-text search in the navigation bar are sorted by relevance and not alphabetically anymore. So, the best matching Fact Sheets appear first.

  

Reports:

• We’ve aligned the aggregation of lower-level hierarchy clusters on Roadmap reports to the same behavior as in the Matrix Reports. This means you will see at first glance how an item on the roadmap timeline (e.g., an Application) impacts the highest level of a hierarchy (e.g., a level 1 Business Capability). This helps answer questions like "Which capabilities will be supported by the newly introduced application?".

• Also, the long names of clustering elements are displayed correctly, and lifecycle data is present in the side panel when selected as a detailed field..

Next-Generation Diagrams:

• Connectors between diagram shapes representing a relation between Fact Sheets (e.g., added via 'Show dependencies') can't be detached from the Fact Sheet pointing into the void. When changing connectors, they always require a shape as a connection endpoint or can be removed completely.

Custom Reports:

• Improvements to the LeanIX reporting library (v0.4.129):

  • currentSetup is now accessible over the global variable lx

  • lx.ready() does not need configuration to initialize a report.

  • Errors produced in reports are now propagated to the main application and presented in the same way as other error pop-up messages in the top right corner.

Integrations:

• The GraphQL API no longer returns results for queries including invalid facet keys but ignores the invalid facet filter and returns results based on the remaining filters. If you have set up custom integrations, custom reports, or scripts using the GraphQL API, please check that they only use the correct facet keys.

• Mapping the relations between Applications and Data Objects from LeanIX to Collibra can be elaborate. To ease the process, you can now choose to map the 'Asset' strategy instead of 'Complex Relations' within Collibra. An intermediate asset between the 'Technology Asset' and the 'Business Assets' representing your Applications and Data Objects will be used. For more details, have a look at the updated documentation.