Weekly feature improvement and bugfix summary

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

Inventory

• The inventory builder now recognizes and extracts fact sheet subtypes during document analysis. Discovered items are pushed to your inbox, allowing you to review and decide whether to create corresponding subtype fact sheets. You can also explicitly request specific subtypes in your user prompt for best results.
  Also, we've changed the entry point when accessing the inventory builder from the inventor to no longer show the overview of recent imports, but directly to the step to upload a file for analysis.

• We fixed an issue where fact sheet naming conflicts were not detected during test runs when deleting a fact sheet via the Excel import. If the deleted fact sheet’s name was part of another fact sheet's display name (e.g., as a prefix or suffix), its removal could lead to a name clash. These conflicts are now correctly flagged during the test import run, so you can resolve them before completing the Excel import.

• We have fixed an issue where the constraining relation editor did not adjust to screen size, preventing users from viewing all content. It now supports scrolling and scales correctly to the screen.

• Users in a custom user role can select workspace views as expected when configured for their availability

Diagrams

• When creating any diagram, the initial version is automatically saved to prevent the loss of diagram content when the application or browser tab is closed without saving it. From there, all changes to the diagram are saved automatically in real time, as before.
  Additionally, this update provides you with more configuration options and flexibility from the start. You can add a description, adjust permissions, and toggle the automatic updates for labels and view colors from the beginning.

Integrations

• The OAuth2.0 authentication method for the Collibra integration now supports more customizable configuration to match your Identity Provider’s requirements for issuing tokens. You can configure OAuth 2.0 strategies, including custom request and query parameters.