The Glossary term detail view has been redesigned with dedicated tabs for Graph, Relations, and Assets, making it easier to explore and manage term context. The legacy view has been unified with the Catalog layout, enabling a side-by-side experience with configurable panel widths that are saved per user for a more personalized workflow.

The platform now keeps a full change history for individual Glossary terms, catalog objects, and attributes. All updates are retained, making it easy to review what changed, when, and by whom, and to revert unwanted changes when needed.

Users can configure automatic notifications for changes to specific Glossary terms or Catalog objects, such as schema drift. Alerts are delivered by email and include direct links to the affected entities, making it easy to review changes as they happen.

Test cases can now evaluate results against a percentage threshold instead of a strict pass or fail. The measured percentage is propagated across the platform and reflected in data quality metrics and dashboards. For example, a validation that checks whether at least 90% of rows meet a rule will display the actual percentage result in dashboard visualizations.

Individual Test cases can now be added directly to Dashboard tiles, making it possible to build custom, validation-based data quality metrics and monitor specific Test cases.

Test case SQL can now be viewed in full screen using a dedicated button in the SQL editor, making complex validations easier to read and edit. In addition, users can define custom row-level result queries by using subqueries in the SQL projection, enabling more flexible and advanced Test case logic (see documentation for details).

New Custom Field types are now available, allowing values to be selected from existing Glossary terms, entered as dates, or captured using larger text areas. This enables richer metadata and more structured documentation across the platform.

Custom fields can now be assigned to Business rules, allowing teams to capture additional metadata and standardize documentation alongside existing rule definitions.