Release6.3.4.3

The OvalEdge Release6.3.4.3 introduces key enhancements, bug fixes, and change impact within the Governed Data Query module, improving functionality, usability, and system performance.

Key highlights include:

Release Type

Release Version

Build

<Release. Build Number. Release Stamp>

Build Date

Service Release

Release6.3.4.3

Release6.3.4.3.6343.07510bd

03 March, 2025

Governed Data Query

New & Improved

Role-based Governed Data Query creation configuration.
Custom-Defined Conditions Now Supported for Governed Data Query Entries
Users Notified Upon Successful Governed Data Query Execution
Breadcrumb Navigation Added to Governed Data Query for Easy Navigation
In Governed Data Query, a breadcrumb navigation has been added. Users can now view their navigation path and return to previous pages by clicking the link sequence.
Governed Data Query Enhancements: UI Updates and Improved Job Details
- The "Object" column on the View Results page has been renamed "Table."
- The "+" icon for "Add Governed Data Query" has been replaced with a checkmark (✔).
- In the "Add Governed Data Query" pop-up window, the placeholder for "Steward" has been changed from "Select Approval Stage" to "Select Steward."
- The View Results page for a Governed Data Query will now consistently display the most recent results.
- A new column named "Condition" has been added to the results page, displaying the condition used to fetch the results.
- The jobs are enhanced to give more details to the end user.
- Data types at each connector level are identified and documented. If an execution involves unsupported data types, the job logs capture and display the details.

Fixed

Fix for Unauthorized GDQ Result Access
In Governed Data Query (GDQ), an issue where users without Domain access could still view the GDQ results from the GDQ result URL page has been resolved. Now, users without Domain access won't be able to view the GDQ results.
GDQ Results Now Require Both Domain and Object-Level Access
In Governed Data Query (GDQ), an issue where users with Domain-level access but without Object-level permissions could still see those objects on the GDQ results page. Users will now see objects on the GDQ results page if they have both Domain-level and Object-level access.