Metadata Governance

Data Catalog

• In Data Lineage, keyword search is now enabled on the lineage page without requiring the full object name.

  What Changed

  In the Data Catalog, the lineage page search in the lineage tab required entering the full object name, which limited flexibility and made it harder to locate lineage objects quickly. Now, users can search using keywords or any portion of the object name, improving search efficiency, accuracy, and overall navigation within the lineage page.

  Affected Users: All Users

• In Data Catalog, a Parent Report column is now added before the Report Name, showing each sheet’s parent report.

  What Changed

  In Data Catalog, when streams were enabled in Qlik Sense, the Data Catalog did not provide a way to distinguish between multiple sheets with the same name from the same stream. This made it difficult to identify and differentiate sheets belonging to different reports within the same stream. Now, a Parent Report column has been added to the Report and Report Column List pages, positioned before the Report Name in the System View. This column displays the parent report for each sheet, enabling users to differentiate sheets with the same name from different reports within the same stream. The Parent Report column supports filtering, sorting, and advanced search (Elastic, Equal/Not Equal), and is included in both Simple Download (CSV) and Detailed Download (LMDF Template) exports.

  Affected Users: All Users

• In Data Catalog, the Access Cart button now appears only when the default project is set to Access Cart.

  What Changed

  In Data Catalog, the Access Cart button was always visible on the Data Catalog List Page, appearing after the Custom View button, regardless of the user’s default project. Now, the Access Cart button is visible only when the user’s default project is set to Access Cart. It is placed before the Custom View button. If the condition is not met, the button is hidden.

  Affected Users: All Users

• In Data Catalog, the Columns tab view on object summary pages has been restored (as in version 6.3.x) with application security enabled.

  What Changed

  In Data Catalog, clicking on a column navigated users to a separate column summary page outside the parent object view, disrupting workflow and requiring extra navigation. The API Attribute Summary tab also lacked application security controls. Now, a dedicated Columns/Attributes tab is available within the parent object’s Summary Page (Table, File, Report, API). Clicking a column opens the parent Summary Page with the Columns/Attributes tab active. Application security is enabled for supported attribute types, including Table Columns, File Columns, and Report Columns.

  Affected Users: Business & Technical Users

• In Data Catalog, increase the technical description limit to 1,000,000 characters.

  What Changed

  In Data Catalog, the system displayed an error when adding a technical description exceeding 10,000 characters in Data Catalog tables. This limit prevented storing detailed descriptions for large datasets or complex metadata. Now, the character limit for technical descriptions has been expanded to 1,000,000 characters across supported modules. Updates have been applied to both the application and LMDF templates to handle large content. The Load Metadata configuration now includes options to update or ignore descriptions based on completeness, with visual indicators for partial entries.

  Affected Users: Authors

• In Data Catalog, Objects Certification marked with "None" appear first when sorting, instead of being excluded from certification type sorting.

  What Changed

  In the Data Catalog, when an object's certification status was set to None and sorting was applied, objects with None appeared at the top of the list. None was incorrectly treated as a valid certification type during sorting. Now, sorting by certification has been removed, preventing None objects from being treated as a certification type in sorting results.

  Affected Users: All Users

• In Data Catalog, the Top Users display is standardized to show 5 users for all object types.

  What Changed

  In Data Catalog, the Top User system setting did not apply consistently across all object types. For example, setting it to 3 displayed 3 users for schemas, 2 for tables, and 1 for table columns, rather than 3 for all objects. Now, the Top Users section consistently displays a fixed number of 5 users across all object types, regardless of the system configuration.

  Affected Users: All Users

Virtual Objects

• Virtual objects can now be created, edited, or deleted in bulk for tables, files, reports, and APIs using the LMDF template.

  What Changed

  Virtual objects could only be created manually, and any updates or modifications also had to be performed manually. Now, virtual objects can be created, edited, or deleted in bulk for tables, table columns, files, file columns, reports, report columns, APIs, and API attributes through the LMDF template.

  Affected Users: All Users

Business Glossary

• Governance role scoring no longer assigns points when the steward or owner is the default admin principal. For all other roles, the score increases by 5 points.

  What Changed

  In the Business Glossary, the governance role score did not increase when the steward or owner had the OE_Admin role. Now, if the steward or owner is the configured default admin principal, no points are added. If the steward or owner is not the default admin principal, the governance role score increases by 5 points.

  Affected Users: Administrators, Authors, Viewers

• The Business Glossary List view Published Section now displays the complete domain hierarchy — including domains, categories, and subcategories — regardless of term status (published, draft, or none).

  What Changed

  In the Business Glossary, the Published Terms view displayed only domains, categories, and subcategories that contained at least one published term. If a domain or category had only draft terms or no terms, its hierarchy was hidden. Now, the Published Terms Tree View displays the complete Business Glossary hierarchy, including all domains, categories, and subcategories, even if no published terms exist. Empty categories or subcategories remain visible but do not list terms until they are published.

  Affected Users: Administrators, Authors, Viewers

• Governance role updates at the category or subcategory level can now be applied to all existing terms.

  What Changed

  In the Business Glossary, governance roles set at the category or subcategory level applied only to new terms. Existing terms did not inherit updated roles, and there was no option to propagate changes, resulting in inconsistent role assignments. Now, users can cascade governance role changes to all existing terms in a category or subcategory. In Domain settings, under Configure Category or Configure Subcategory, the new Cascade to all terms option triggers a background job that applies updated roles to all existing terms.

  Affected Users: Administrators, Authors

• In the Term or Data Object summary, the Reference section now displays only valid, existing objects.

  What Changed

  In the Business Glossary Term Summary, when a referenced object (e.g., a Data Story) was deleted, the reference to it remained visible in the Reference section of the Term or Data Object Summary page. Clicking on this reference resulted in an error or a message indicating that the object no longer exists. Now, when a referenced object is deleted, it is automatically removed from the Reference section of the Term or Data Object Summary page.

  Affected Users: Administrators, Authors, Viewers

Tags

• Tags can now be created under Non-Assignable Parent Tags, allowing more flexibility in tag hierarchy.

  What Changed

  In the Tags module, tags could not be created under Non-Assignable Parent Tags. Now, tags can be created under a Non-Assignable Parent Tag.

  Affected Users: Administrators, Authors

• Tag management now uses Master Tags and governance roles, providing structured organization, control, and standardization across the system.

  What Changed

  In Tags, all tags were managed globally without tag-level security or governance roles. Permissions were centralized and controlled primarily by administrators. Now, Master Tags serve as first-level domains or containers for regular tags. Designated users can manage Master Tags by creating, deleting, and assigning permissions, thereby controlling tag management within each domain. A new system setting, Tags Security Mode, provides two options:

  • Open Mode (default): Maintains centralized administrator control, consistent with legacy behavior.

  • Secure Mode: Enables granular security and role-based governance at the Master Tag level, with flexible security toggling.

  Two versions of the Tags LMDF template are maintained based on the selected mode. Governance roles—Owner, Steward, and Custodian—are now enforced at the Master Tag level, with permissions equivalent to Authors with Admin Access within their domains.

  Affected Users: All Users

• In Tags, the system now allows the creation of tags and master tags with a single character.

  What Changed

  In Tags, creating Tags and Master Tags required a minimum of three characters. Now, Tags and Master Tags can be created with as few as one character, with no minimum character limit.

  Affected Users: Administrators, Authors

Governance Catalog

Data Classification Recommendations

• In the AI Recommendation Engine, temporary lineage objects are no longer considered in recommendations.

  What Changed

  In the AI Recommendation Engine, recommendations for Business Glossary terms to data objects were previously generated using name similarity with fuzzy matching, data values and patterns, and associated objects and their lineage, including both normal and temporary lineage. Temporary lineage could not be excluded, which sometimes resulted in irrelevant or inaccurate suggestions. Now, temporary lineage objects are excluded by default from recommendations, which improves accuracy by preventing false positives, reducing noise in suggestions, and increasing trust in the recommendations.

  Affected Users: Administrators, Authors

• In Data Classification Recommendation and Business Glossary Term Summary, accepting a recommended term now automatically removes the current term and associates the recommended term with policies updated accordingly.

  What Changed

  In the Data Classification Recommendation module, the Model Summary previously displayed two columns, Current Term and Recommended Term. When Apply was selected, a background job was triggered. If a data object already had a different primary term, the recommendation was not applied, and a message indicated that the primary term could not be replaced. The existing term had to be manually removed from the Data Object or Term Summary page before the recommendation could be accepted. This process introduced unnecessary manual steps and reduced the usability of AI-based recommendations.

  Now, accepting a recommendation in the Data Classification Recommendation module or the Business Glossary Term Summary page displays a confirmation pop-up:

  “Accepting the recommendation will remove the associated term and replace it with the recommended term. Note: Policies associated with the previous term will be removed, and new term policies will be implemented on the data object.”

  Selecting Continue completes the replacement, while Cancel aborts the action. On confirmation, the current term is replaced with the recommended term, and term-level policies are updated as follows:

  • If the previous term had masking or restriction policies and the new term does not, existing policies remain.

  • If the previous term had no policies and the new term has policies, the new policies are applied.

  • If both terms have policies, the new term’s policies override the existing ones.

  A background job executes the association change and policy updates. This update eliminates manual steps, ensures policy and governance consistency, prevents policy gaps, enhances adoption of AI recommendations through a more intuitive workflow, and preserves auditability for compliance and traceability.

  Affected Users: Administrators, Authors

Certification Policy

• In Data Catalog, the certification message now appears in table view when hovering over the certification type icon.

  What Changed

  In Data Catalog, in the table view, the certification message was not displayed when hovering over the certification type icon. Now, the certification message in the table view is displayed when hovering over the certification type icon.

  Affected Users: All users

Governed Data Query

• Governed Data Query | Notification for GDQ Execution Completion.

  What Changed

  In Governed Data Query, the executions completed without notifying the executor, requiring manual status checks and delaying access to results. Now, an option is available to send execution completion notifications. The system alerts the GDQ executor when an execution finishes, including the GDQ name, entry name, and a direct download link for results. The notification subject is “GDQ Execution Completed.”

  Affected Users: Administrators, Authors

• Governed Data Query | Enable role-based GDQ Creator Configuration.

  What Changed

  In Governed Data Query, the creation of Governed Data Queries (GDQs) was restricted to Admin roles. Authorized non-admin users could not create, execute, or delete GDQs, causing bottlenecks and delaying query workflows. Now, a new system configuration, ovaledge.GDQ.admin has been introduced in the User & Roles list to define GDQ creator permissions. Roles added to this list can create, execute, and delete GDQs without requiring Admin privileges, enabling authorized roles such as domain stewards or data users to manage GDQs independently.

  Affected Users: Administrators, Authors

• Governed Data Queries (GDQs) now support assigning all applicable governance roles, not just the Steward role.

  What Changed

  In GDQ, Governed Data Query (GDQ) assigned only the Steward role. Other governance roles were missing, causing inconsistent role assignments. Now, GDQ displays all configured governance roles, including Steward, Owner, Custodian, and additional roles (Governance Role 4, 5, 6) based on configured names. Roles are dynamically fetched from Administration → Security → Governance Roles and appear only if enabled for Privacy and Compliance in the admin panel configuration.

  Affected Users: Administrators, Authors

• Governed Data Query | Extend the ‘AND’ condition to more than 4 and the ‘OR’ condition to more than 12.

  What Changed

  The Governed Data Query (GDQ) allowed a maximum of 4 ‘AND’ conditions and 12 ‘OR’ conditions, limiting the ability to build complex queries across multiple attributes or term associations. Now, GDQ supports dynamic addition of AND and OR conditions beyond the previous limits, allowing users to include more than 4 AND conditions and more than 12 OR conditions.

  Affected Users: Administrators, Authors

• Governed Data Query | Add filter, search, and column navigation features to GDQ results.

  What Changed

  The Governed Data Query (GDQ) results lacked filter and search functionality for specific columns, making it difficult to locate and navigate to detailed column information. Now, GDQ results include filter and search features, enabling users to find and highlight specific columns efficiently. A column navigation option allows direct access to column details from the entries, improving navigation and usability.

  Affected Users: Administrators, Authors

User's List

• In Governance Catalog – User Management, the User list layout has been updated, and navigation to a user’s desk is now available from the Users & Roles section.

  What Changed

  In Governance Catalog – User Management, the User List layout and navigation have been updated. Previously, in the User’s List, each User ID included a hyperlink, and the columns Authorized Roles and Users were displayed for each user. In Users & Roles, no hyperlink was available against each User ID to navigate to the user’s desk.

  Now, in the User’s List, hyperlinks against each User ID are removed, and the Authorized Roles and Users columns are no longer displayed. In Users & Roles module, a hyperlink is added against each User ID, allowing direct navigation to the user’s desk.

  With this update, Users & Roles Admin and Default Role Admin can navigate to any user’s desk to view responsibilities that were previously visible in My Desk. Author license users can navigate to their own desk from the Users module.

  Affected Users: Administrators, Authors

Data Quality

• In Data Quality Rules, monetary value, criticality, violation message, and corrective action can now be configured independently of the “Add Failed Rows to Remediation Center” setting.

  What Changed

  In Data Quality Rules, configuring remediation metadata fields (monetary value, criticality, violation message, and corrective action) was previously dependent on enabling the Add Failed Rows to Remediation Center toggle. These fields could not be populated unless the toggle was enabled, which often resulted in missing contextual details and made it challenging to assess business impact, prioritize fixes, and maintain governance.

  Now, remediation metadata fields can be configured regardless of the toggle status. The toggle only determines whether failed rows are sent for further review. This enhancement allows rules to include full contextual details even when remediation is not required.

  This update removes the restrictive dependency, improves compliance tracking and prioritization, and ensures governance consistency. Remediation workflows remain unchanged for backward compatibility. Minor adoption considerations include updating guidance to clarify that metadata fields are optional but recommended, and reviewing legacy rules to populate missing metadata where necessary.

  Affected Users: Administrators, Authors

Query Sheet

• In the Query Sheet, the Query Editor displays only the latest query, highlights the related table, and includes a manual clear option.

  What Changed

  In the Query Sheet, in the Query editor, the query used to fetch results remained in the editor. Selecting a different table did not clear the query; instead, new queries were appended to the existing one. Now, the Query editor displays only the latest query. The table linked to the current query and results is highlighted in the left panel, and a clear button is available to manually remove the query when needed.

  Affected Users: Administrators & Authors

Jobs

• Job execution actions renamed and simplified for clarity.

  What Changed

  In Jobs, the Initialize/Resume Job option resumed the same job instance using the same Job ID. The Hold Job option was available but had no practical use. Now, the Initialize/Resume Job option has been renamed to Initiate Fresh Job and starts a new job instance with a new Job ID. The Hold Job option has been removed from the Manage Jobs dropdown.

  Affected Users: Administrators

---

Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA, USA.