OvalEdge Releases
      Back to home
      1. Knowledge Base
      2. Architecture, Security & Releases
      3. OvalEdge Releases

      Release6.3.4

      The OvalEdge Release6.3.4 introduces key enhancements, bug fixes, and change impact across various modules, 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

      		 Release6.3.4.6340.a4b576d 28 January, 2025

      Login

      New & Improved

      • OvalEdge now supports integration with ADFS using OpenID Connect (OIDC) protocol, enabling secure OAuth2-based authentication. This enhancement allows organizations to configure ADFS application groups and set up the OvalEdge server for seamless user authentication via ADFS credentials.
      • Before logging into the OvalEdge application, a new Warning Banner is displayed to inform users about the organization's privacy and security notices. When the user clicks the Okay button, the Sign In page is displayed, allowing the user to enter their credentials and sign in.
        A new system setting, 'login.warning.enable,' has been introduced to display a warning banner when logging into the OvalEdge application.
        • If set to 'true,' the warning banner appears.
        • If set to 'false,' the warning banner does not appear.
        To display content on the banner, another system setting,  'login.warning.description,' has been developed, and 'login.warning.enable' is set to 'true.' The description supports up to 2000 characters. Users can click 'Okay' on the banner to enter their login credentials.

      Home

      New & Improved

      • Previously, users could not view the total number of unsuccessful login attempts or the last successful login date on the Home page.
        With this improvement, users can now see the last successful login date and the number of unsuccessful login attempts between the current and previous successful logins on the Home page.

        Configuration:
        To enable this feature:
        • Navigate to Administration > System Settings > Others.
        • Use the key home.lastlogin.enable and set its value to true.
        • By default, this system setting is set to false.

      My Resources

      New & Improved

      • In My Resources > My Project Tasks, drag and drop functionality has been implemented for task cards in the Board view for individual projects.

      • A new component has been built, allowing users to choose language preferences so the application shows in that language. In the My Resources section, go to My Profile and select your preferred language from the drop-down menu. The application will then be displayed in the chosen language.

      Data Catalog

      New & Improved

      • Administrators can now control access to the report preview tab in the Data Catalog and Dashboards. They can enable or restrict other users' access to the report preview tab as needed. Additionally, they can manage report preview access by setting viewer permissions and role-based controls.
        Navigate to Administration > Security > Applications and search for the Application Name (Report - Preview).
      • In the Data Catalog's list view, users now have the provision to add comments when certifying multiple data objects using the 9-dots action menu. This functionality allows users to include relevant comments during bulk certification.
      • The Froala Editor now supports Right-to-Left (RTL) and Left-to-Right (LTR) text alignment when adding business and technical descriptions in Arabic. This enhancement allows users to achieve proper indentation and formatting for languages like Arabic that require RTL alignment.
      • A new feature, 'Add to Impact Analysis,' has been introduced to enhance impact analysis workflows. Users can access this feature in multiple areas. 
        • Navigate through Tables, Table Columns, File, File Columns, Report, and Report Columns, click on the Nine Dots, and select the '+Add Impact Analysis' option. 
        • Alternatively, on the Tables, File, and Report Summary page, go to the Lineage tab, open the Graphical View, locate the nodes section, click on the three dots, and select 'Add to Impact Analysis'. This enhancement provides a streamlined approach to managing impact analysis.
      • Previously, there were no loading bars to inform users when a page was loading. Now, loading bars have been implemented on all the pages in the Data Catalog.

      Fixed

      • In the Data Catalog objects grid view, an issue where the naming conventions of statuses in the "Certification" column and its filter did not match has been resolved. Users will now see consistent certification status names in the 'certification' column and its filter.
      • In the Data Catalog’s Object Summary, the issue of terms becoming invisible in the object summary after being associated with data objects has been resolved. Users can now view the associated term(s) in the object summary without issues.
      • In Data Catalog’s Object Summary, the issue that caused the URL field to be invisible in the business and technical descriptions during edit mode has been resolved. Users can now view the URL field in the pop-up after clicking the "Insert Link" icon.
      • In Report Columns, the issue where the formula field for a virtual report column became non-editable for a manual connector after saving has been fixed. Users can now edit the formula field for virtual report columns linked to a manual connector, even after saving.
      • In Data Catalog’s Object Summary, an issue where the Data tab displayed "No Data Exists" even after crawling and profiling the SSAS on-prem connector has been resolved. Users can now view the data in the Data tab for the SSAS on-prem connector objects as expected.
      • In Data Catalog > Databases > Create New View, the issue that prevented users from creating a Public View when the "View Visible to All" option was selected has been resolved.
        Users can now create and configure Public Views without encountering any issues.
      • In the Data Catalog > Tables, an issue where if the cloned table did not exist, column-level lineage was not built has been fixed. Now, column-level lineage is also built along with table-level lineage.
      • Users can now hide/display the "Generate with AI" button across all the metadata description fields using the system configuration.
      • The Remote Tags section has been removed from the Data Catalog's File Column Summary, as it applies solely to files, not file columns.
      • In the Data Catalog object summary's nine-dots action menu, the label in the 'Update Governance Roles' pop-up has been updated to "Cascade all Governance Roles to Hierarchy."
      • Creating Virtual Tables and Reports no longer requires adding at least one column during setup.

      Business Glossary

      New & Improved

      • Users can now clone any existing term. The cloned term will be created in the same domain but not linked to any specific category or subcategory. It will inherit the following metadata: Business Description, Detailed Description, Tags, Custom Fields, Related Objects, Classification, and Policies.
      • In the Term Summary > Associated Objects, users will now find an "Originative Source" column within each associated object type category tab. This column allows users to mark data objects (e.g., tables, columns, files, APIs) as originative sources, enabling quick identification of the origin of data within the organization.
        This enhancement improves clarity and significantly enhances data traceability, particularly lineage tracking.
      • In the Term Summary, users can now filter report columns in the Associated Objects and Recommendations tabs by connection name. This enhancement simplifies navigation, making it easier to find relevant report columns.

      Fixed

      • In the Term Summary, an issue has been resolved where the metadata curation scores for terms were not updating after running the metadata curation advanced job. Previously, the scores would only refresh when users clicked the metadata curation icon. Now, users can view the updated metadata curation scores for terms automatically without clicking the icon.
      • In the Term Summary, an issue where the associated code count was missing on the summary page has been fixed. Additionally, the issue of connector names not appearing for Codes and Report Type objects in the Associations tab has been resolved. Users can now see the code count in the Term Summary and the connector name details in the Associations section for Codes and Reports.
      • In the Tree View, text wrapping and justification issues in term descriptions have been fixed. Users can now read term descriptions without any text layout problems.
      • Admins can now reset the default system configuration and grant access to only specific Governance Role(s) users to publish the Term.
      • Changes made by Security and Governance Admins (SGA) to the default classifications within a domain will no longer impact the classifications already checked or unchecked in existing terms within the same domain.
      • Users won't be able to download the masked data when a masking policy is applied to a term associated with a file column.
      • Users can now select multiple objects as authoritative sources.

      Question Wall

      New & Improved

      • The assignee will receive email notifications for the initial question and all follow-up replies.

      Dashboard

      Fixed

      • In Dashboard, previously, when a report was unavailable, the corresponding tile appeared blank, causing confusion. Now, the system displays a placeholder message within the tile to inform users that the report is unavailable clearly. 

      Projects

      New & Improved

      • The Project's Board View has been enhanced to improve object naming conventions, display curated task descriptions, and show task status history.
      • Previously, users needed to manually configure the status workflow when starting a new project. With the "Copy Existing Status Workflow" option, users can choose an existing project from a dropdown menu to apply its workflow to the new project. The new project will default to system-generated statuses if no project is selected.
      • A new "Priority" column has been added to the Projects List View, enabling users to view and manage task priorities.

      Fixed

      • The issue of data stories not showing up in the List View after being added to a project has been resolved. Now, users can see data stories linked to a project in both the List View and the Board View.
      • In All Projects, an issue where the project label in connected modules such as Grid View (Data Catalog, Business Glossary) and tags associations was incorrectly displayed as "Project" even after selecting the default project type as "Access Cart" has been resolved.
        Users will now see the default project type set in the Projects module, and the same is reflected as the project label in all connected modules.
      • A safeguard mechanism has been implemented in projects to prevent the accidental deletion of the default project, whether during single project deletion or as part of a bulk deletion process.

      Service Desk

      New & Improved

      • Automated Metadata Curation allows users to transfer metadata from one report to another. When a new report is created in the source system, and the connector is crawled in OvalEdge, the report is added as an object with its metadata.

        A new request type, Curating New Asset, is introduced and available when Tables or Reports are selected as object types. A custom template guides this process, enabling users to curate metadata for a new report based on an existing one. Users can fill in fields such as Business Description, Technical Description, and Associated Tags.

        During the approval phase, users can select the new report group and name the report. After the request is fulfilled, a virtual report with the curated metadata is created. The virtual report remains in the Data Catalog even if the connector is crawled again. When the report is fully created and crawled in OvalEdge, it is added as a crawled object with the existing metadata from the virtual report.
      • In the Service Desk Template, previously, fields such as Placeholder Text, Tooltip, and Field Label could not be edited once a service request was raised. Additionally, system-defined Workflow Action and Status Labels were not editable. In the current version, these fields are now editable if the template has no pending service requests. System-defined Workflow Action and Status Labels are also editable. A new Description field has been added for Status, allowing users to specify the use case for each System Status and modify the name accordingly, providing greater flexibility and control.
      • Enhanced Service Request Closure Permissions in Service Desk.

      Data Classification Recommendations

      New & Improved

      • In the Governance Catalog, Data Classification Recommendations, the AI configuration for setting the maximum number of data objects for AI recommendations was previously limited to Table Columns. This functionality has now been enhanced to support additional data objects, including Report Columns and File Columns.
      • In the Data Classification Reports Overview, identifying data classifications while filtering and downloading records was challenging for users. Now, a “Classification” column has been added to every object page. This addition provides clear visibility of the classification applied to each data object, enhancing data clarity and accessibility.

      ROPA

      Fixed

      • In ROPA Reports, the issue of Top Users being invisible under the "Top Users" section in the report summary has been resolved. Users can now view the Top Users list.

      Data Quality

      New & Improved

      • In the Data Quality Rule Overview, previously, users had to navigate to the Rule Executions tab to view metrics such as Passed Count, Failed Count, Undetermined Count, and Execution Failed Count. The updated Data Quality Rule module now displays these fields directly on the overview page, providing immediate visibility based on the latest rule execution.
      • The labels for "Report Data Quality Issue," "Report Metadata Change Request," "Term Data Quality Issue," "URL Data Quality Issue," and "Data Literacy" have been corrected to Arabic from the current version to the correct version.
      • The supported data types for the Exasol connector were previously outdated and caused potential inaccuracies in the rule application. Following the update, the data types now align with the accurate list, ensuring consistency and accuracy in applying table column rules. 
      • The Data Quality Remediation Center has been enhanced to display failed values for Custom SQL Rules, addressing a significant limitation in the previous version where failed values were not shown. This improvement allows users to view problematic data directly, enabling quicker identification and resolution of data quality issues.
      •  In Data Quality Rules, users can now create custom SQL rules using the LMDF template, addressing the limitations of the previous version that required manual rule configuration. This enhancement allows users to upload templates containing boolean, statistical, and failed value queries, simplifying the creation of complex or customized rules for their datasets. Additionally, the feature supports direct query uploads via the template, reducing manual effort, streamlining the rule creation process, and ensuring the system efficiently interprets, catalogs, and applies these queries.
      • Previously, Data Quality rules were not directly linked to terms, making it difficult to track their associations. The new solution allows users to add Data Quality rules in the 'Related Objects' section, enabling them to link rules with specific terms and specify relationship types. This change improves tracking and organization, offering a functional way to manage Data Quality rule relationships.
      • Standardized Default View and Enhanced Customization for Data Quality Rules.

      Fixed

      • Change in Operator Default Values
      • Enhanced Access Controls for Inline DQR Menu Actions
      • Accurate User Attribution for Data Quality Rule Modifications
      • In Data Quality Rules, scheduling conflicts are resolved to ensure the "Last Run By" field accurately displays the user who scheduled each rule, even during simultaneous executions.
      • In the Data Quality > Rule Recommendations section, the "Add Objects" widget now displays only the connectors associated with the Data Quality Add-On license.

      Query Sheet

      New & Improved

      • Users can now copy and paste SQL queries into the Query Sheet and execute them without errors.

      Fixed

      • An issue where users encountered blank data when downloading a query related to the Azure Synapse connector after increasing the row count limit has been resolved. Users can now view the complete SQL query data in the downloaded file, regardless of the adjusted row count limit.
      • An issue where an error was thrown when users added the complete SQL code with intermittent line breaks has been resolved. Users can now execute queries, even if the SQL query includes line breaks.
      • An issue where SQL queries failed to execute has been resolved. Users will no longer face query execution issues caused by line breaks, spaces, or other formatting in the SQL commands.
      • Enhanced Security for Query Sheet Column Access

      Jobs

      Fixed

      • An issue where the file name displayed a temp path after downloading has been resolved. Now, users can view the created user ID and timestamp included in the file name for better clarity and tracking.

      Compare Profile Results

      Fixed

      • Previously, the Source and Target drop-down list placeholder was shown as "Please select the connector," is fixed and now showing as "Please select the schema" as per the functionality.

      Compare Schemas

      Fixed

      • An issue was encountered when comparing schemas by selecting Schema A from one connector and Schema B from another, where only the latest crawl date appeared in the Select Date dropdown, even though the schema had been crawled on multiple dates. This issue has been resolved, and now the Select Date dropdown displays all the dates on which the schema was crawled, allowing users to select from a complete set of crawl dates.

      Build Auto Lineage

      New & Improved

      • Lineage dashboard has been enhanced.
      • Metadata propagation has been enhanced.
      • Temp connector is not displayed on the Connectors page.

      Fixed

      • An issue with the clone table not building the lineage in the OvalEdge application when using the Clone function in Snowflake SQL. This issue has been fixed, and the Clone function is now supported in OvalEdge for Snowflake SQL.
      • An issue while building lineage for the Dataset semantic tables expression, a new type of MCode function used in expression i.e. Analysis.Services() has been resolved. Now that function is handled and the lineage is populated for the expression and connected to the SSAS server, which is mentioned in the MCode.

      Load Metadata from Files

      New & Improved

      • Users who uploaded the Datasets LMDF template with the code type set to "OTHER" encountered an invalid SQL error.

      Fixed

      • In the Load Metadata from Files > Data Quality Rule, an issue with downloading the “Data Quality Rule” template with data from the “Object Name” column has been resolved. Users will now be able to download the Data Quality Rule template with data. 
      • In the Load Metadata from Files > Table Column, when users renamed a downloaded template file and uploaded it an error occurred. This issue has been fixed, allowing users to upload renamed files successfully.
      • In the Load Metadata from Files, when users uploaded table details where the table name and view name were identical, the governance roles were not updated. This issue has been fixed, and governance roles are now correctly updated for these tables on the Data Catalog page.
      • In the Load Metadata from Files > Upload Users, when users logged in using SAML and attempted to upload user data, the upload failed if the username and first name fields were empty. This issue has been fixed, and the sheet now uploads successfully even if these fields are empty.

      OvalEdge APIs

      New & Improved

      • A new API has been developed to retrieve all the reports based on the Report Group ID.
      • A new API '/api/getAssociatedCustomFieldValueObject' has been developed to get the object details with a particular custom field.
      • A new API, DELETE /api/connector/{connectorid}, has been introduced to remove connector information from the OvalEdge application.
      • A new API (GET/api/v1/entity-relationships) has been developed to get the entity relationship information.
      • A new API, 'GET/api/query/lineagegraph' has been developed based on 'lineageid'. This returns the Query details such as query, summary, its associations, references, and lineage details.
      • The Table and Table Column APIs now display all associated term details, including the term ID, domain name, term name, category name, and subcategory name, based on the table or column ID.

      Connectors

      New & Improved

      • The SAP Table connector in OvalEdge is now enhanced to fetch relationships from the source system and display them in the data catalog. A new Relationships option has been added to the connector settings. When enabled, the crawler automatically retrieves the relationships from the source SAP system and displays them in the entity relationship diagram (ERD), providing a clear view of table relationships and improving data governance and discovery.
      • The Crawler options in Connector Settings have been enhanced with a new Indexes checkbox. When users select the Indexes checkbox, indexes from SQL, Oracle, and Greenplum databases are automatically crawled and displayed in the Data Catalog under the Index tab within the Table Summary.
      • A new enhancement has been made for the Sybase connector to build the lineage from files to tables for stored procedures.
      • The size limit for fields in Secrets Manager has been increased.
      • For the Synapse connector, 
        • The Synapse labels from the source system were not crawled in OvalEdge's regular crawling process. An advanced job (Fetching Labels for Synapse Columns) has been developed to crawl the Synapse labels from the source system to OvalEdge.
        • The Azure Active Directory - Password authentication is supported.
      • For the MySQL connector, previously, Username/Password authentication was supported. Now, it has been enhanced to support Azure Entra ID authentication, providing more security for users.

      Fixed

      • An issue in the About OvalEdge section, where the number of connectors was displayed incorrectly, has been resolved. Previously, a temporary connection (Connector ID—1 MySQL) was incorrectly counted as the Base Connector. Now, temporary connections are excluded from the count, and the number of connectors is displayed accurately.
      • An issue with the Power BI connector not displaying the correct lineage status has been fixed. Now, if the lineage is built successfully, the status shows Success. The specific error details are displayed in the Error column if there are errors.
      • For the CartoVista connector, an issue where the connector failed to save after validation due to a database connection error has been fixed. Now, the connector successfully saves after validation.
      • For Qlik Sense, FME connectors, an issue where a null exception occurred while fetching connector attributes during Edit Connector using the 9-dots menu has been fixed. All connector attribute values display correctly when accessing 9-dots > Edit Connector.
      • For the SharePoint connector, an issue where the crawling job failed and could not catalog the folders and files, which has been fixed. Now, able to catalog the files and folders.
      • For the SharePoint connector, an issue such as 'Requested array size exceeds VM limit' has been fixed. The connector now validates successfully.
      • For the SQL Server connector, an issue where the Delete Connection job failed while deleting the connector has been fixed. Now, the connector is deleted successfully.
      • For the Looker connector, an issue of an error occurring when the port number was entered and the connection string was set to 'auto' has been fixed. If the string is set to manual' during validation, the user should enter the port number in the string field. The connector now validates successfully.
      • For Delta Lake Connector, an issue with connection validation has been resolved. Previously, connection validation failed when using a Personal Access Token in internal and client environments or Service Principal Authentication in the client environment. This issue has been fixed, and connections are now validated successfully for both authentication methods.
      • For the Qliksense On-Premises Connector, an issue was encountered where report columns were missing during metadata crawling. This issue has been resolved, and now, when users crawl or profile the report, the report columns are successfully fetched from the data source and displayed in the Data Catalog Report Column.
      • For Talend Connector, an error occurred when users attempted to crawl and build lineage using the GitHub Workspace ID, with the job logs stating that the query could not be parsed. This issue has been fixed by manually correcting the query in the Build Lineage > Correct Query page. Users can now successfully build lineage without encountering any errors.
      • Disabling unsupported options for SharePoint Connector

      Known Issue

      • The Google BigQuery connector encounters an issue where the application fails to load the required library, resulting in a ClassNotFoundException error.
        Temporary Workaround:
        A necessary library will be added to the OvalEdge configuration to ensure proper loading.
        Resolution:
        This issue is scheduled to be fixed in the upcoming release.

      Users & Roles

      New & Improved

      • In Users & Roles, previously, when using Okta for authentication, the user's title or job title was not mapped to the corresponding field in the OvalEdge Users table. Now, if an instance uses Okta for authentication, the user's title or job title is correctly mapped to the OvalEdge Users table during login. This update ensures that the user's title or job title is accurately reflected in OvalEdge, improving user data consistency.

      Security

      New & Improved

      • In Administration > Security > Domains, users can now input Domain, Category, and Subcategory names and their descriptions in Arabic, providing improved support for multilingual configurations.

      Service Desk Templates

      New & Improved

      • In Service Desk Templates, for Azure DevOps integration, the mapping of Service Desk Template Fields to Azure DevOps Fields, Area, and Iteration fields was unavailable. This functionality has now been enhanced. When an Azure DevOps ticket is created, the Area Paths and Iteration Paths specified in the Service Desk Template mapper fields are now mapped and displayed in the Azure DevOps ticket.
      • In Service Desk Templates, for the Associated Workflow, the Actor dropdown previously displayed all Team or Role names, even if no users were associated with them. This caused confusion for users.

        This functionality has now been enhanced:
        • The Actor dropdown displays only Team or Role names with at least one user assigned.
        • If a Governance Role is the approver in the workflow and an empty team is assigned as the Governance Role for an object, the workflow will skip that team and move to the next approver.
      • In the Service Desk Template, the default term status for the Term Creation Request template was previously set to "Published." Additionally, system templates were not editable, and custom templates could not be modified once a service request had been raised. In the current version, the default value of Term Status has been changed to "Draft." Custom options in service request templates are now editable when the template is inactive and has no pending service requests.
      • Specific fields in the Service Desk Template and Workflow Actions and Status Labels are now editable if no service requests are pending.

      Custom Fields

      Fixed

      • An issue causing inconsistent visibility of custom fields while navigating between Global Custom Fields and Connector Custom Fields has been resolved. Users can now view the global and connector custom fields without any issues.

      System Settings

      New & Improved

      • A new System Setting (oe.profile.importancescore.threshold) has been developed to define a threshold value for the importance score of data objects in the profiling process. Only data objects with an importance score equal to or greater than this threshold will be included in the profiling. The value should be in the range of 0 - 100.
      • Two separate tabs have been added for APIs and Projects.
      • Previously, the OvalEdge application did not support the Spanish language. Now, the OvalEdge application supports the Spanish language. Navigate to Administration > System Settings > Others, search the key as "ovaledge.locale" and set its value to "Spanish."

      Fixed

      • System Setting 'tags.children.pagination.row.size' has been removed.
      • System Setting 'tags.pagination.row.size' has been removed.
      • System Setting 'is.erd.advancedsettings.enabled' has been removed.
      • System Setting 'catalog.views.setdefault.allow' has been removed.

      Audit Trails

      New & Improved

      • In the Audit Trails, under the Catalog tab and the Terms sub-tab, the action for data objects was previously displayed as Add for both when a term was moved to the draft state and the published state. This caused confusion among users.
        This functionality has now been improved. When a term is moved to the draft or published state, the action is recorded only once. Detailed action information is displayed in the Governance Catalog under Terms in the Action Details column, with the following messages:
        • Term successfully moved to Draft State.
        • Term successfully moved to Published State.

      New Connectors

      Oracle Analytics Server

      • Oracle Analytics Server (OAS) is an on-premises analytics platform offering reporting, data visualization, and advanced analytics capabilities. OvalEdge requires a service account and uses SOAP services to connect to OAS. This integration enables users to crawl data objects, such as reports and report columns, allowing detailed analysis and metadata exploration within OvalEdge.

      New Advanced Jobs

      Name 

      Description

      Migration_JobtoInactivate_Datasets

      This advanced job is used to make the child dataset(s) inactive when their parent dataset is inactive.


      Previously, the child dataset(s) remained active and visible in the Data Catalog under code associations, even when their parent dataset was inactive. However, the child datasets will now become inactive after running this job.


      Note:

      When to run this job:

      This migration job has to run once if users migrate from any release version to R6.3.4.

      DQTAT Execution Overview

      This job analyzes the Data Quality Test Suite, highlighting the status of each Data Quality Rule (DQR) executed in the current release. The job generates a summary of passed and failed rules, listing associated objects for each failed rule. This overview enables swift identification of potential data quality issues and assists teams in pinpointing areas that may require additional focus or remediation.

      Fetching Labels for Synapse Columns

      This job helps fetch the Synapse labels at table level and column level.

      Advance Job for Inserting data into the Lineage table

      This job allows the insertion of data into the Lineage Table to build a Connection Dashboard view.

      FME TO CARTO VISTA Lineage

      This job will establish lineage from FME to Carto Vista based on the FME Components.

      Report Crawl Analysis

      This job facilitates the analysis of activated and inactivated objects during the second crawl of the Power BI server. Upon running the job, a report is generated that provides details about the updated activated and inactivated objects of the Power BI server in OvalEdge, enabling users to track and manage object status effectively.

      New System Settings

      The latest release introduces a new system setting that enhances user control over the application's behavior.

      Key 

      Description

      Impacted Modules in OvalEdge

      dataquality.associatedobjects.tables.limit

      Set the maximum number of objects (tables and table columns) that can be associated with a Data Quality Rule.


      Parameters:

      The default value is set to 1000.


      Enter the value in the field provided.

      Minimum entered value is 1.

      Maximum entered value is 1000.

      Data Quality

      dataquality.associatedobjects.files.limit

      Set the maximum number of objects (files and file columns) that can be associated with a Data Quality Rule.

      Parameters:

      The default value is set to 20.


      Enter the value in the field provided.

      Minimum entered value is 1.

      Maximum entered value is 250.

      Data Quality

      oe.profile.importancescore.threshold

      Configure to define a threshold value for the importance score of data assets in the profiling process. Only assets with an importance score equal to or greater than this threshold will be included in the profiling. 


      Parameters:

      The default value is 0.

      Enter the value in the field provided.

      The value should be in the range of 0-100.

      In Data Catalog > Tables, Table Columns.

      max.character.count.for.text.custom.fields

      Specify the maximum character count allowed for text custom fields.


      Parameters:

      The default value is 1000 characters.

      Accepted value is < 5000.

      Custom fields are available in the Data Catalog, Business Glossary, Tags, Data Quality Recommendations, ROPA Report, and ROPA Processing Activities.

      ai.description.enable

      Configure to show/hide the 'Generate with AI' icon for the Business, Technical, and Detail descriptions.

      Parameters:

      The default value is True.


      If set to True, show the 'Generate with AI' icon for the Business, Technical, and Detail descriptions.

      If set to False, hide the 'Generate with AI' icon for the Business, Technical, and Detail descriptions.
      • Business and Technical Descriptions in Data Catalog.
      • Business and Detail Descriptions in Business Glossary.

      home.lastlogin.enable

      Configure to show/hide the user's last successful login date and the number of unsuccessful login attempts between the current and the previous successful login.


      Parameters:

      The default value is 'False'.


      If set to 'True,' show the last successful login date and the number of unsuccessful login attempts between the current and the previous successful login.

      If set to 'False,' hide the last successful login date and the number of unsuccessful login attempts between the current and the previous successful login.

      Login page

      login.warning.enable

      Configure to show/hide the banner. Upon clicking Okay, users can enter their User ID and Password to proceed with the Login.

      Parameters:

      The default value is 'False'.


      If set to True, show the banner.

      If set to False, hide the banner.

      Login page

      login.warning.description

      The specified description in the Value column shows on the banner if login.warning.enable is set to 'true.'

      The maximum number of characters supported is 2000.


      Parameters:

      The default value is 'Empty'.


      If the Value column contains the content, it shows on the banner.

      If the Value column is 'Empty,' the banner is not shown.

      Login page

      Hotfix Release6.3.4.2

      This hotfix release introduces key enhancements, bug fixes, and change impact across various modules, improving functionality, usability, and system performance.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix

      Release6.3.4.2

      		 Release6.3.4.2.6342d6db54b March 20th, 2025

      Data Lineage Dashboard

      Known Issue

      • In the Lineage Dashboard, we see the ovaledgedb connection, which happens when the schema or connector containing lineage tables is deleted. This issue will be fixed in the upcoming release, and users will not see the OvalEdgedb in the lineage dashboard.

      Data Quality

      Fixed

      • In Data Quality Rule previously in Data Quality Rule execution, failed values appeared unmasked in the Data Quality Remediation Center (DQRC) and Notifications despite being correctly masked in Rule Executions and Object Executions. This issue is now resolved, and failed values are correctly masked across all relevant sections, ensuring consistency and data security.

      Build Auto Lineage

      Fixed

      • Go to Data Catalog > Report Columns > Select any object, then click on Lineage. In the tabular view, an issue where the icons for report columns were showing as tabular icons has been fixed. Now, the icon for the report column is showing correctly.
      • Go to Data Catalog > Tables and click the Has Lineage button; it navigates to the Lineage tab. Then, if the user clicks on Dashboard > Data Lineage and clicks on Lineage, again, if the user clicks on Data Catalog > Tables and clicks on Has Lineage, the page is not found error has been fixed. Now, if the user navigates from the Dashboard, able to view the Lineage.

      Connectors

      Fixed

      • In Administration > Connectors, when you crawl tables from the Salesforce connector, they are crawled into OvalEdge. If a table is deleted from Salesforce, it should automatically be marked inactive in OvalEdge after the next crawl. However, this process was slow and caused performance issues. Now, the issue has been resolved by optimizing the performance by simplifying the inactivation of tables while using relationships.
      • In Administration > Connectors > select any connector of type RDBMS or Report connector, go to Connector Settings and Others tab; an issue where when the user chooses any Team and saves changes and again navigates to Others tab, then the user is unable to see the added team is resolved. Now, the user can see the selected team.

      New & Improved

      • In Administration > Connectors > OAS7 connector, AWS Secrets Manager has been introduced as a Credential Manager.

      Reporting Framework

      New & Improved

      • The ovaledgedb connector now supports Azure Key Vault and AWS Secrets Manager when users store their credentials in the oasis.properties file. While validating the ovaledgedb connector using these Credential Manager, the connector gets authenticated based on the values specified in the oasis.properties.file. This functionality has also been applied to Azure Entra ID and MariaDB connections.

        Migrated the Reporting Framework (RFW) from file-based storage to Liquibase for improved data management and integrity.
        • Previous Challenges:
          • Deleting and inserting RFW data led to data loss and disrupted associations.

        • Enhancements with Liquibase:

          • Corrects inaccurate queries and ensures data consistency.
          • Inserts new scripts without affecting existing data.
          • It protects data and formatting, preventing any unintentional changes.

      Hotfix Release6.3.4.2.1

      This hotfix release includes a bug fix in the Lineage, where the Lineage did not appear despite showing a Lineage status as successful.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.2.1

      Release6.3.4.2.1.63421.21d6424

      24th March 2025

      Lineage

      Fixed

      Lineage for SAP BO Reports

      In Connectors > SAP BO Reports, an issue that showed a "Lineage build successful" status but did not display the lineage has been resolved. Users can now successfully view the Lineage.

      Hotfix 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.

      Hotfix Release6.3.4.4

      This hotfix release includes a security patch, ensuring improved system security. Additionally, it contains bug fixes and enhancements for Auto Lineage, Qlik Sense, and Salesforce connectors, along with introducing a new Salesforce Commerce Cloud connector.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.4

      Release6.3.4.5.6344.

      		 07 March, 2025

      Security

      Fixed

      • Security Update
        A security vulnerability was identified in the io-netty library as part of routine Secure Software Development Lifecycle (SSDLC) assessments. This issue has been patched in the latest version. Users should update to the latest version to improve system security and stability.
        For more details, refer to the official advisory: CVE-2025-24970.

      Build Auto Lineage

      Fixed

      • Fix for SQL Server Query Failures in Auto Lineage
        In Advanced tools > Build Auto Lineage, an issue where the queries were failing for the SQL Server connector due to syntax issues has been fixed. Now, the lineage is built successfully with all the queries.

      Connectors

      New & Improved

      • Option to Include/Exclude Unpublished Sheets
        In Administration > Connectors > Qlik Sense (On-Prem), a new option has been added to exclude/include unpublished sheets by entering Y or N options. Users can enter 'Y' to exclude unpublished sheets or 'N' to include them.
      • Enhanced Regex Filtering
        In Administration > Connectors > Salesforce, previously, Salesforce APIs retrieved all tables, even when a regex filter was applied during crawling. A new enhancement has been made so that Salesforce APIs now fetch tables from the source based on the specified regex criteria.

      New Connectors

      Salesforce Commerce Cloud

      OvalEdge uses REST APIs to connect to the data source, which allows users to crawl system objects and object fields.

      • Type: RDBMS
      • Crawl: Supported
      • Profile: Not Supported
      • Manual Lineage: Supported
      • Data Quality: Not Supported
      • Query Execution: Not Supported
      • Bridge: Not Supported

      Refer here for detailed Salesforce Commerce Cloud connector documentation.

      Hotfix Release6.3.4.5

      This hotfix release includes OpenID Connect (OIDC) support in ADFS, enabling authentication using Active Directory usernames instead of email addresses.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.5

      Release6.3.4.5.6345.a5c1ed3

      		 11 March, 2025

      Login and SSO

      New & Improved

      OIDC-Based Authentication with Username in OvalEdge

      Users previously authenticated in the OvalEdge application using their email addresses. A new enhancement introduces OpenID Connect (OIDC) in the Active Directory Federation Services (ADFS) implementation, enabling authentication with usernames existing in the Active Directory instead of email addresses.

      Hotfix Release6.3.4.5.1

      This hotfix release includes a bug fix in connector crawling, where crawling failed on report groups after setting the “Exclude Unpublished Sheets” option to Y.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.5.1

      		 Release6.3.4.5.6345bff1c44 20th March 2025

      Connector

      Fixed

      Crawling in QlikSense On-Prem

      In Connectors > QlikSense On-Prem, an issue where crawling failed on report groups after setting "Exclude Unpublished Sheets" to Y has been resolved. Users can now successfully see the report groups for QlikSense On-Prem Connector. 

      Hotfix Release6.3.4.6

      This hotfix release enhances lineage building for Power BI reports with live connections. It uses connection files when DataModel or DataModelSchema files are unavailable.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.6

      Release6.3.4.6.6346.a5c1ed3

      11 March, 2025

      Build Auto Lineage

      New & Improved

      Enhanced Lineage Building for Power BI Live Connections
      In Advanced Tools > Build Auto Lineage, a new enhancement has been made so that when Power BI reports are built using a live connection, no DataModel or DataModelSchema files are available. In this case, lineage is built using the connection file containing the connection details to the source system.

      Hotfix Release6.3.4.7

      This hotfix release includes bug fixes and gap enhancements for Data Catalog, Business Glossary, Data Quality, and Connectors.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.7

      Release6.3.4.7.6347f874548

      19 March, 2025

      Data Catalog

      Fixed

      • Custom Fields Header Column Values Overlap Issue in Public View
        In the Data Catalog, an issue where the values in the Custom Fields header column overlapped with other header column values when creating a public view has been resolved. Users can now view the header column values without overlap.
      • Salesforce Formatted Source Description in Data Catalog
        An issue preventing users from viewing the exact Salesforce-formatted Source Description in the Data Catalog object summary has been resolved. Users can now see the Salesforce-formatted Source Description in proper format within the object summary.

      Business Glossary

      Fixed

      • Business Glossary Download Issue with Tags Filter Resolved in List View
        In the Business Glossary > List View, an issue preventing users from downloading the Business Glossary when the Tags filter was applied has been resolved. Users can now successfully download the Business Glossary after applying the Tags filter.
      • Published Terms Now Visible in Business Glossary Tree View
        In the Business Glossary, an issue that prevented users from viewing published Terms in Tree View while they remained visible in List View has been resolved. Users can now access all published Terms directly in Tree View without relying on the search functionality.
      • Governance Role 4 Visibility in Business Glossary
        In the Business Glossary, an issue has been resolved where users could view governancerole4 from the "Update Governance Roles" option in Nine Dots only if the governancerole4 checkbox was enabled for both Display in Data Catalog and Display in Business Glossary (located under Administration > Security > Governance Roles). Users can now independently enable or disable the visibility of governancerole4 in the Data Catalog or Business Glossary based on their preferences.

      Data Quality

      New & Improved

      • Improved Sorting Logic
        In Data Quality Rules for Object Execution Results. Previously, object executions were ordered by Object Execution ID in descending order, which caused new objects added to existing rules to appear at the bottom of the list despite being recently executed. Now, execution results are sorted by rule execution ID, ensuring that the most recent executions, including those for newly added objects, always appear at the top of the table. This change improves the visibility of recent executions, enhances usability, and provides a more intuitive "latest first" experience regardless of when objects were added to a rule.

      Connectors

      Fixed

      • Fix for DBT Core Connector Crawling Issue
        In Administration > Connectors, an issue where the DBT Core connector failed to crawl datasets when using the DBT Core Repository type as NFS has been fixed. The connector can now successfully crawl datasets.

      New & Improved

      • Improved Lineage Building for Power BI Cloud Paginated Reports
        In Administration > Connectors, an issue in the Power BI Cloud connector caused lineage-building failures for paginated reports due to an unhandled M code expression in the source code. This enhancement ensures that M code expressions are now processed correctly, allowing source details extraction and proper connections between relevant tables.


      Hotfix Release6.3.4.7.1

      This hotfix release includes a bug fix in the Data Catalog Codes page that affected result visualization.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.7.1

      Release6.3.4.7.1.63471.7773be4

      24/03/2025

      Data Catalog

      Fixed

      Visualizing Results in Data Catalog Codes

      In the Data Catalog > Codes page, an issue preventing users from viewing results and displaying an error in the Visualizing Results tab after executing queries has been resolved. Users can now successfully view the results.



      Hotfix Release6.3.4.8

      This hotfix release includes bug fixes in the Data Catalog, Business Glossary, Lineage, Data Stories Migration Job, and Connectors.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.8

      Release6.3.4.8.6348.fe80677

      28 March 2025

      Data Catalog

      New & Improved

      New Filter Option for "Has Lineage" Column in Data Catalog

      In the Data Catalog > Tables Grid View, an advanced filter option (Yes/No) has been added to the "Has Lineage" column, allowing users to filter tables based on their lineage status.

      Sorting and Search Updates

      To improve performance, the following changes have been made to the Data Catalog > List Page:

      Sorting

      • The sorting option has been removed from all columns

      Search

      • The search feature has been removed for date-based columns like Last Crawled Date, Last Modified Date, Last Profiled Date etc., and for count-based columns like Row Count, Null Count, Distinct Count etc.

      These changes are part of ongoing performance optimization efforts.

      Business Glossary 

      Fixed 

      SubCategory Fields in Configure View

      In Business Glossary > Configure View, an issue where subcategory fields were grayed out while configuring or editing views has been resolved. Users can now successfully configure views.

      Detail Description and Custom Fields Duplication

      In Business Glossary, an issue where the Detail Description did not create an entry in the table during the first update has been resolved. Users can now successfully update the Detail Description without issues.

      In Business Glossary, an issue where updating custom fields created duplicate entries instead of replacing the existing ones has been resolved. Users can now update custom fields without duplicates.

      Advanced Tools

      Fixed

      Build Auto Lineage 

      In Lineage, an issue where building a lineage for Carto Vista Connector with a different object type deleted the existing lineage for that object type has been resolved. Users can now build lineage successfully for Carto Vista Connector. 

      Array Index Exception in Lineage Build for Stored Procedures

      In Build Lineage, an array index exception occurred when building lineage for stored procedures, preventing successful lineage generation. This issue caused an error message and disrupted the process. The issue has now been resolved, allowing lineage to be built for selected stored procedures without errors.

      Administration

      Fixed

      Data Stories Migration Advanced Job

      In the Administration > Advanced Jobs, an issue where the Data Stories Migration Advanced Job failed to execute has been resolved. Users can now successfully run the job.

      Connectors

      New & Improved

      Akamai Connector

      OvalEdge integrates with Akamai Identity Cloud using REST APIs to establish a connection with the data source. This integration enables users to crawl system objects and object fields, ensuring seamless data discovery and management of Akamai metadata within OvalEdge.

      Fixed

      Adding Custom Fields for Connectors

      In Administration > Custom Fields, an issue where users with Default Admin permission for a specific connector could not create custom fields has been resolved. Users with Default Admin permission can now successfully create custom fields for the assigned connector. 

      Build Lineage for Delta Lake Connector

      In the Administration > Connectors, an issue with lineage in the Delta Lake Connector has been resolved. Users can now successfully build lineage for the Delta Lake Connector.

      Snowflake Connector Validation Issue After Password Update

      Users could not validate the Snowflake Connector after updating the OvalEdge-Snowflake user password in the Snowflake environment due to repeated account lockouts. This issue has been resolved, allowing successful connector validation after a password update.

      Conditional Update for Reporting Framework Connection (-1) in Connectors

      In Administration > Connectors, previously, the Reporting Framework Connection (-1) Advanced Job was triggered every time, even without modifications to the oasis.properties file. Now, this job will only be triggered when the oasis.properties file is updated or modified.


      Hotfix Release6.3.4.9

      This hotfix release includes bug fixes related in the Business Glossary, Data Catalog, Connectors, and Advanced Jobs. 

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.9

      		 Release6.3.4.9.634915c68c4 10th April, 2025

      Business Glossary

      Fixed

      Rejected Recommendations and Filter Issue

      In the Business Glossary, an issue where rejected recommendations reappeared, and filters in associated data objects did not work correctly has been resolved. If the user rejects the recommendation, it will be considered rejected and won't appear again when the user re-runs the AI model. The rejected recommendation can be viewed in the restore rejected recommendation. Users can now filter the associated data objects accurately. 

      Data Catalog 

      Improved 

      • Sorting and search capabilities for specific columns have been removed from the Data Catalog List View to improve performance.
       

      What’s Changed: In the Data Catalog List View, the sorting feature previously available for specific columns has been removed from all columns to optimize performance. Additionally, the search functionality for all date-based and count-based columns—including Last Crawled Date, Last Modified Date, Last Profiled Date, Row Count, Null Count, and Distinct Count—has been removed. These updates were made to improve the overall performance of the Data Catalog List View.

      Affected Users: All Users 

      Administration 

      Fixed 

      Unsupported Data Type Profiling Issue in PostgreSQL

      In PostgreSQL, an issue where profiling failed for tables containing columns with unsupported data types has been resolved. The system now skips such tables and logs a warning message instead of throwing an error. Users can now run profiling jobs without interruption.

      Azure Key Vault Connection and Job Duplication Issue

      In the Administration > Connectors, during migration, an issue where multiple Azure Key Vault connections were created by default and the "Load Reporting" advanced job ran twice has been resolved. The system now makes a single connection, and the job executes only once, as expected. Users can now manage Azure Key Vault connections and job execution without duplication.


      Multiple Advanced Jobs on Server Restart in Multi-Pod Setup

      In the Reporting Framework, an issue where restarting the server in a multi-pod setup triggered multiple instances of the same advanced job has been resolved. The system now ensures that only a single instance of the job runs after a restart.

      Jira Configuration Through Proxy

      Service Desk tickets can now be integrated into Jira through a proxy connection by configuring the proxy connection details in the system settings.

      Note: This is the beta version of the change coming.

      Hotfix Release6.3.4.10

      This hotfix release includes bug fixes for the Business Glossary, Data Catalog, Data Quality Rules, Governance Catalog, and Administration. 

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.10

      Release6.3.4.10.6341064e669d

      18th April 2025

      Business Glossary

      Fixed

      Term Association Access Issue

      In the Data Catalog, an issue preventing users with Meta Write access on a data object and Meta Read access on a term from adding or removing terms from the object has been resolved. Users can now successfully add or remove terms when they have the required permissions.

      Data Catalog

      Fixed

      Search and Sort Options Disabled in Data Catalog

      In the Data Catalog, an issue where search and sort options were disabled on the List page has been resolved. The configuration key EnableCatalogSortSearch now controls these options. 

      • When set to true, users can perform complete sorts and extended searches, which may impact performance on large datasets. 
      • When set to false, the options remain disabled to optimize performance.

      Data Quality

      Fixed

      Failed Values Not Displayed in Data Quality Rule Notifications

      In Data Quality Rules, an issue where failed values were not displayed in notifications after rule execution has been resolved. The system now includes the failed values in the notifications. Users can now view failure details directly in the notification.

      Governance Catalog 

      Fixed

      Incorrect Audit Logging in Governance Catalog

      In the Governance Catalog, an issue where clicking on the Metadata Curation Score or Popularity Score incorrectly logged curation score updates in the audit trail has been resolved. The system now logs only actual metadata changes, ensuring accurate audit records.

      Administration

      Fixed

      Custom Field Deletion Issue via Load Metadata From Files

      In Custom Fields, an issue where deleting fields through Load Metadata From Files failed has been resolved. The system now allows users to delete custom fields successfully using this method.

      Connectors

      Fixed 

      Incomplete Lineage Display in SQL Server

      In SQL Server, an issue where the data lineage graph did not display all related tables and views has been resolved. Previously, the lineage for views referencing other tables showed only a few source objects, missing full relationships. Additionally, attributes used in calculated fields, WHERE clauses, GROUP BY clauses, or JOINs were not captured. The system now accurately displays all related tables, views, and attributes in the lineage graph.

      Public Schema Not Visible During Redshift Connector Crawling

      In the Redshift connector, an issue with the "public" schema not appearing in the OE application during crawling or profiling has been resolved. The system now correctly displays the public schema after a connector crawl.

      Malformed SQL Statements During Crawling

      In the Redshift Connector, an issue where SQL statements generated during crawling were occasionally malformed has been resolved. The system sometimes generated "SELEC" instead of "SELECT," causing crawl failures. The connector forms valid SQL statements, allowing users to crawl the Redshift connector without errors.

      Report Groups Not Visible After Validation in QlikSense Connector

      In the QlikSense connector, an issue where report groups did not appear on the Crawl/Profile page after successful validation has been resolved. The system now correctly displays the report groups upon crawling or profiling.

      Temporary Lineage Display in SAP BODS

      In the SAP BODS connector, an issue where the system displayed temporary lineage instead of the actual data flow has been resolved. The system now shows the complete transformation path for cataloged objects as expected.

      Schema Crawling Error in SAP BO Universe

      In the SAP BO Universe connector, an issue where crawling failed with a "Problem in crawling schema" error after successful connection validation has been resolved. The system now completes the crawl without errors.

      Missing Sub-Reports in SAP BO Connector

      In the SAP BO connector, an issue where sub-reports were not fetched into the Data Catalog has been resolved. The system now correctly captures and displays sub-reports along with main reports and columns.

      Hotfix Release6.3.4.11

      This hotfix release includes bug fixes in the Tags, Data Catalog, Business Glossary, Data Quality Rules, and Connectors. 

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.11

      Release6.3.4.11.6341106bca56

      02 May 2025

      Tags 

      Fixed

      Delete Tag Option Still Enabled After Deletion 

      In the Tags section, an issue where the "Delete Tag" option remained active even after deleting a tag has been resolved. Previously, the option stayed enabled without selecting a tag unless the page was refreshed. Now, the delete option is enabled only when a tag is selected, as expected.

      Data Catalog

      Fixed

      Incorrect Display of Custom Field Values in Custom View 

      In the Data Catalog, an issue where global custom field values appeared incorrectly in the custom view has been resolved. The connector name was shown in the wrong column, and expected values were missing, causing confusion. Users can now view the correct custom field values displayed in their appropriate columns.

      Pagination Setting Not Retained in System View 

      In the Data Catalog, an issue where the system view displayed only one row instead of the configured 20 rows per page has been resolved. Users can now view 20 rows per page.

      Report Type Filter Missing While Associating Reports

      In the Add Object widget, an issue where all object types—reports, datasets, pages, and charts—were displayed without a filter, making it challenging to associate relevant reports accurately, has been resolved. Users can now use the newly added "Report Type" column with a filter to quickly identify and associate the correct report objects.

      Business Glossary 

      Fixed 

      Custom Field Values Missing in Downloaded Term Template 

      In the Business Glossary, the issue of Code Custom Field values (both Global and Domain-level) not being visible in the downloaded term data template has been resolved. Users can now download the template with the correct custom field values displayed for each term.

      Data Quality Rules 

      Fixed

      Custom SQL Query Retrieval Added in DQ Rules GET APIs

      In the DQ Rules GET APIs, the ability to retrieve associated Custom SQL Queries has been added to provide users with complete rule details and improve data visibility through the API.

      Connectors

      Fixed

      No Lineage Built for Power BI Reports Due to Direct Connection with SSAS

      In Power BI (on-prem), an issue where reports were directly built from SSAS without datasets, preventing lineage from being created, has been identified. Users can now analyze files to determine how lineage can be built from the SSAS model to the Power BI reports.

      Lineage Built for Parse-Failed Procedures – Redshift

      In Redshift, an issue where lineage was being built for stored procedures with parse-failed code has been resolved. Users can now build lineage successfully for the failed procedures.

      Delta Lake Connector Health Issue – SAAS

      In the SAAS application, the issue of the Delta Lake connector health status automatically turning red has been resolved. Users previously encountered a "Connection timeout expired" error when validating the Delta Lake connection with the Bridge. The connector now maintains its health status and functions correctly.

      Unable to Validate HashiCorp Vault with Power BI Cloud Service Principal

      In the OvalEdge application, an issue where the connection between HashiCorp Vault and Power BI Cloud Service Principal could not be validated has been resolved. Users can now successfully validate the connection and securely retrieve secrets for Power BI operations via HashiCorp Vault.

      Schema Crawling Failure in SAP BO Universe

      In SAP BO Universe, an issue where schema crawling failed due to an error in retrieving remote tables from the source JSON file has been resolved. Users can now successfully crawl schemas after validating the connection, with all relevant data being processed without errors.

      Missing Source Descriptions for Table Columns – SQL Server

      In SQL Server, an issue where source descriptions for table columns were not captured in the OvalEdge application during crawling has been resolved. Users can now view the correct column descriptions in OvalEdge as populated from the source.

      Formula Display Support for Semantic Tables – Power BI On-Prem

      In Power BI On-Prem, an issue where formulas from semantic tables were not displayed in the OvalEdge application has been resolved. Users can now use the formula in the column technical description for semantic tables.

      Hotfix Release6.3.4.12

      This hotfix release includes bug fixes for the Business Glossary LMDF upload and download processes, as well as connectors, including Sybase IQ and PowerBI Cloud lineage, SSO - SAML.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.12

      Release6.3.4.12.6341261468cd

      6th April 2025

      Business Glossary

      Added additional loggers for identifying the RC

      Missing Download Link in Job Log During LMDF Upload

      In the Business Glossary, an issue where the job log did not display the download link during Business Glossary template uploads, and occasionally showed the job status as "killed" despite successful term template uploads.

      Missing Descriptions in LMDF Download

      In the Business Glossary, an issue where business descriptions were missing or outdated in the LMDF download file, despite being correct in the UI for some terms.

      Connectors

      Fixed

      Lineage Break Issue – Sybase IQ

      In Sybase IQ, an issue where lineage was breaking due to a schema mismatch for temporary tables during stored procedure processing has been resolved. The lineage previously created temp tables in the “TEMPDB” schema, while similarly named temp tables existed in the “TempDB” schema, preventing correct lineage mapping. Users can now successfully build lineage with accurate schema references.

      Incorrect Lineage Status in Power BI Cloud

      In Power BI Cloud, an issue where lineage was incorrectly marked as "Lineage Partially Built" for reports containing non-data pages like README or INFORMATION has been resolved. Previously, OvalEdge misinterpreted the absence of data fields on these pages as a lineage failure, even though lineage was successfully built for valid data pages. Users can now view the correct lineage status for such reports.

      Added additional loggers for identifying the RC

      Lineage Issue Due to Parse Failures – Sybase IQ

      In Sybase IQ, an issue where lineage was not captured from files to tables due to parse failures in stored procedures has been addressed by adding additional loggers. Previously, 20 procedures failed to parse, preventing accurate lineage generation. 

      SSO Login 

      Improvement

      SAML Login Implementation

      SAML Login has been implemented and can be tested only in the Client Environment. 

      Hotfix Release6.3.4.13

      This hotfix release includes bug fixes in Business Glossary, Data Catalog, and Oracle Analytics Server Connector. 

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.13

      Release6.3.4.13.6341309adcfa

      8th May 2025

      Business Glossary

      Fixed 

      Upload Failure Due to Truncated Domain Names in LMDF Template

      In the Business Glossary, an issue where LMDF uploads failed due to truncated domain names in the Excel sheet tab (caused by Excel’s 31-character limit) has been resolved. The template now uses only the Domain ID during upload, allowing users to upload files regardless of domain name length successfully.

      Data Catalog

      Fixed

      Missing Save Option While Editing Codes

      In the Data Catalog Code page, an issue where the 'Save' button did not appear while editing code names or values has been resolved. Users can now successfully edit and save code details as expected.

      Connectors 

      Fixed

      Incomplete Report and Column Extraction in Oracle Analytics Server

      In Oracle Analytics Server, an issue where only a limited number of reports and report columns were fetched, while several existed in the source, has been resolved. Users can now successfully extract all reports and their associated columns, including those from model-type reports.

      Hotfix Release6.3.4.14

      This hotfix release includes bug fixes in the Data Catalog and Connectors.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.14

      Release6.3.4.14.634141ab556d

      12th May 2025

      Data Catalog

      Fixed

      Save Button Not Appearing While Editing Codes

      In the Data Catalog Code page, an issue where the 'Save' button did not appear while editing code names or values has been resolved. Users can now successfully make and save updates to code.

      Connector 

      Fixed 

      Missing Server Field in DBT Cloud Connector

      In the DBT Cloud connector, an issue where the server field was unavailable, causing the connector to default to a generic server address, has been resolved. Users can now specify a custom server address to support organization-specific configurations.

      Excessive Open SQL Sessions

      In the SQL Database, an issue where some sessions remained open unexpectedly, impacting performance and stability, has been resolved. Users can now connect to the database without excessive open sessions affecting operations.

      Hotfix Release6.3.4.15

      This hotfix release includes bug fixes for the login and connectors.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.15

      Release6.3.4.15.6341542d5f32

      15th May 2025

      Login

      Fixed

      Log-in | Role-Based Access Message Enhancement

      To improve the user experience during login, the system now displays a clear warning message when a user without any assigned roles attempts to access OvalEdge. Previously, such users encountered a generic HTTP error screen, which provided no context and led to confusion. This issue has been resolved, and users will now see the following message: "Your account does not have any valid roles associated to access OvalEdge. Please reach out to your administrator.”

      In Spanish: "Su cuenta no tiene roles válidos asociados para acceder a OvalEdge. Por favor, comuníquese con su administrador."

      Connectors

      Fixed

      Lineage Build Issue for SharePoint and QVD Sources in Qlik Cloud

      In the Qlik Cloud connector, an issue where lineage could not be built for reports using SharePoint files or QVD files as data sources has been resolved. Users can now successfully build lineage for these report types.

      Missing Column Lineage in Power BI

      In the Power BI connector, the issue of renamed columns in M-code functions being correctly mapped from the semantic layer to the source table has been resolved. Additionally, columns with formulas previously missing from column-level lineage are correctly captured, ensuring accurate lineage tracking.

      Dataflow Lineage Issue in Power BI 

      In the Power BI connector, an issue where file names appeared as null in Dataflow lineage has been resolved. The connector now correctly handles file names and supports new expressions using CommonDataService. It also displays an appropriate error message when the dataset source code cannot be fetched for Dataflow objects.

      Lineage Status Mismatch in Qlik Sense (On-Prem)

      In the Qlik Sense (On-Prem) connector, an issue where the Build Lineage page showed a "Lineage Build Success" status even when no actual lineage existed for the report has been resolved. The connector now accurately reflects the lineage status.

      Missing Dashboard Name with Streams Enabled in Qlik Sense

      In the Qlik Sense connector, an issue where the dashboard name was not displayed in the Report Group field when streams were enabled has been resolved. The connector now correctly shows the dashboard name alongside the stream name.

      Hotfix Release6.3.4.16

      This hotfix release includes bug fixes in the Query Sheet, and Connectors. 

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.16

      Release6.3.4.16.63416c61f466

      20th May 2025

      Query Sheet

      Fixed

      SELECT * Not Working as Expected

      In the Query Sheet, an issue where SELECT * queries did not return results unless the table name was fully qualified with a schema has been resolved. Users can now execute SELECT * queries successfully without specifying the schema.

      SQL | SELECT MIN Query Error

      In the Query Sheet, an issue where running SELECT MIN(column) FROM table caused an error has been resolved. Queries using SELECT * FROM table returned results correctly, but the error occurred specifically with the SELECT MIN query. Users can now run SELECT MIN queries without errors.

      Connectors 

      Fixed

      Delta Lake Connection | Crawling Job Error

      In the Delta Lake connection, an issue where crawling jobs failed with the error “exception occurred while fetching remote databases” and “connection test failed for connector” has been resolved. Customers can now run crawling jobs successfully without encountering errors.

      Lineage Build Error in Logs for SSAS On-Prem

      In the SSAS On-Prem connector, an issue where an error message appeared in the job log during lineage build has been resolved. The lineage was successfully built, but the log incorrectly reported an error for the associated query sheet. Users can now build lineage without encountering misleading error messages in the job log.

      Crawling Error in DataPipeline Connector Without GitHub Validation

      In the DataPipeline connector, an issue where crawling failed with a "Bad Credentials" error if the GitHub connector was not validated first has been resolved. Users can now crawl the DataPipeline connector independently without requiring prior GitHub validation.

      Crawling Error After Tableau Upgrade to 2025.1.0

      In the Tableau connector, an issue where crawling failed with the error “Error while retrieving Tableau Domains::User not able to get Sites” after upgrading to version 2025.1.0 has been resolved. The error occurred when users manually initiated a crawl from the connector page. Users can now successfully crawl Tableau reports after the upgrade.

      Validation Error in Cognos Connector

      In the Cognos connector, an issue where an error message appeared during connector validation—“Error while validating connection. Error while validating metadata connection”—has been resolved. Users can now validate the Cognos connector without encountering validation errors.

      Data Pipeline | Crawl Errors: YAML Parse and Bad Credentials

      In the Data Pipeline connector, an issue where YAML parsing and bad credentials errors occurred during crawl actions has been resolved. Users previously faced a YAML parse error followed by a bad credentials error when validating and crawling schemas. Users can now validate and crawl the Data Pipeline connector without encountering these errors.

      QlikSense | Report Columns Not Showing After Validation

      In the QlikSense connector, an issue where report groups did not appear on the Crawl/Profile page after successful validation has been resolved. Logs showed that published app names were missing, and the server did not return a successful (200) response. Users can now see report groups correctly after validation.

      Vertica | Lineage failed

      In the Vertica connector, an issue where the job responsible for building data lineage from Vertica queries failed daily with the status "KILLED" has been resolved. The job did not complete successfully during each run, preventing lineage generation. Users can now run the lineage build job without encountering failure or job termination.

      Tableau Cloud | Validation error

      In the Tableau Cloud connector, an issue where validation failed with the error "Failed to sign in to Tableau Server" has been resolved. This occurred when users attempted to authenticate using valid credentials and token-based authentication. Users can now validate the Tableau Cloud connector successfully without encountering sign-in errors.

      Connector Details | Missing Admin Role Fields

      In the connector details, an issue where the Admin Role fields (Integration Admin, Security Governance Admin) were missing has been resolved. This prevented users from assigning roles during connector setup and triggered the error message: "Cannot read properties of undefined (reading 'value')". Users can now view and assign Admin Roles as expected during setup.

      Hotfix Release6.3.4.17

      This hotfix release includes bug fixes in the Data Catalog APIs and Dell Boomi Connector. 

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.17

      Release6.3.4.17.634176badad7

      22nd May 2025

      API 

      Fixed

      Table API issue

      In the TABLE API, an issue where a typographical error in the request body caused incorrect data formatting has been resolved. The request body has been corrected to ensure accurate API communication and prevent formatting errors.

      Token Generation Issue with USER API

      In the USER API, an issue where access tokens were not generated when using previously downloaded credentials—despite the API returning a 200 OK status—has been resolved. Token generation now functions as expected with valid credentials, ensuring reliable authentication.

      Invalidation of API Credentials After Logout

      In the OvalEdge application, an issue where API credentials downloaded from the "My Profile" section became invalid after a user logged out and back in has been resolved. Users can now reuse previously downloaded credentials across sessions without needing to generate new ones.

      Connector 

      Fixed 

      Database Null Error in Dell Boomi Connector

      In the Dell Boomi connector, an issue where a "Database Null" error occurred during data crawling—preventing the system from connecting to the database—has been resolved. The connector can now successfully crawl the database without errors.

      Hotfix Release6.3.4.18

      This hotfix release includes bug fixes in the Data Quality API and Oracle Analytics Server Connector. 

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.18

      Release6.3.4.18.6341866067ac

      26th May 2025

      API 

      Fixed

      Data Quality API: Unnecessary Parameters Removed from Response

      The getDQRules API previously included $Filter and $ORDER BY parameters in the response, even when they were not used. This issue has been resolved. The response now excludes these unnecessary parameters.

      Connector 

      Fixed 

      Power BI Cloud | Missing Source Descriptions at Dataset Level
       In the Power BI Cloud connector, an issue where column-level descriptions entered in the dataset’s semantic model under the "Source Description" field were not captured has been resolved. The connector now successfully collects and stores these descriptions.

      Missing Reports and Columns in Oracle Analytics Server Connector

      In the Oracle Analytics Server connector, an issue where only some reports and columns were fetched—while certain reports like model-type reports did not display their columns—has been resolved. The connector now retrieves all reports and columns as expected.

      Hotfix Release6.3.4.19

      This hotfix release includes improvements in the Projects and bug fixes in the Data Catalog, Business Glossary, Logs, and Sybase IQ Connector Lineage.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.19

      		 Release6.3.4.19.63419ac03375 29th May 2025

      Business Glossary 

      Fixed

      Business Glossary Description Character Limit Error

      In the Business Glossary, an issue where the term description incorrectly showed a “10,000 characters exceeded” error, despite the text being within the limit, has been resolved. Users can now enter and save term descriptions without encountering this error.

      Data Catalog

      Fixed

      Custom View Corruption After Saving Modified View

      In the Custom View feature, an issue where saving a modified view as a new custom view caused the view to become corrupted has been resolved. This issue prevented users from seeing content under the Table Columns (TC) section. Users can now save modified views without losing visibility in the TC section.

      Projects 

      Improvement

      Task Visualization by Steward Level in Projects Module

      In the Projects module, a new bar chart report, "Number of Data Quality Issues Reported Based on Implemented Data Quality Rules," has been added. The report displays the monthly count of data quality issues resulting from rule failures and allows drill-down by month. This enhancement enables users to track and analyze tasks at the steward level more effectively.

      Connector

      Fixed 

      SybaseIQ | Incorrect Lineage Status and Error Messages

      In the SybaseIQ connector, an issue where lineage status and error messages were displayed incorrectly has been resolved. The system previously displayed a "Parse Failed" error even when lineage was built successfully, incorrectly labelling "Success with Associations" as an error. Users will now see accurate lineage statuses and error messages.

      Hotfix Release6.3.4.20

      This hotfix release includes bug fixes in the Connectors. 

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.20

      Release6.3.4.20.634203c233d4

      30th May 2025

      Connector 

      Fixed 

      Missing Column Lineage in ADF Connector for Azure SQL

      In the ADF connector, an issue where column lineage was not being built for Azure SQL tables, despite valid mappings in the source code, has been resolved. The connector now correctly builds column-level lineage for the tables as expected.

      Incomplete and Duplicate Lineage in ADF Connector for Azure SQL

      In the ADF connector, an issue where the lineage for the Azure SQL table was not fully built and included duplicate entries has been resolved. The connector now accurately builds a complete and unique lineage for the table, as expected.

      Incorrect Lineage Status in Power BI Cloud

      In the Power BI Cloud connector, an issue where reports without a layout file were incorrectly showing a successful lineage build has been resolved. The connector now displays the appropriate error message - "failed to build lineage"- when no layout file or tables are present in the dataset, ensuring accurate lineage status reporting.

      Incorrect Connector Type for Oracle Analytics Server

      In the Oracle Analytics Server Connector, an issue where the Oracle Analytics Server connector appeared under the "RDBMS" type instead of "Reports" in the Connector Type attribute has been resolved. Now, when users select this connector, it correctly appears as a "Reports" type, ensuring accurate categorization.

      Hotfix Release6.3.4.21

      This hotfix release includes bug fixes in the Job Logs and Connectors. 

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.21

      Release6.3.4.21.6342169811f3

      2nd June 2025

      Job Logs

      Fixed

      Log Aggregation Issue in Log Viewer

      In the Job Log Viewer, an issue where job logs were not consistently aggregating into a single file has been resolved. Logs are now consolidated into a single file, improving log tracking and analysis.

      Incorrect Version Display in Connector

      In the connector view, an issue where the version number was not displaying correctly (e.g., 6.3.4.18 or 6.3.4.X) has been resolved. Version details now appear in the correct format.

      Bridge Client Logs Not Transferred to Application

      In the Bridge client, an issue where logs were not transferred to the Application has been resolved. Logs are now included with the response, enabling improved troubleshooting and better visibility into client-server interactions.

      Connector 

      Fixed

      BigQuery Connector Validation and Credential Parsing Issue

      In the BigQuery connector, an issue where the connection could not be validated due to a credentials JSON parsing error has been resolved. The connector now correctly parses the credentials JSON and validates the connection during setup.

      Hotfix Release6.3.4.22

      This hotfix release includes bug fixes in the Advanced Job, Snowflake Connector, and API.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.22

      		 Release6.3.4.21.6342169811f3 04 June 202

      Advanced Job

      Fixed

      Advanced Job | JDEdwards Custom Field Not Updating

      In the "Load JDEdwards manually" advanced job, an issue where the custom field did not update with the long description when attribute 4 was set to false has been resolved. The job now correctly updates the title and description, including the long description in the custom fields.

      Connector

      Fixed 

      Snowflake Sync | Business and Technical Descriptions Not Updating

      In the Snowflake integration, an issue where business and technical descriptions curated in OvalEdge were not syncing back to Snowflake has been resolved. Users can now automatically push descriptions from OvalEdge to Snowflake without manual updates.

      API

      Fixed

      WebFocus Authentication | API Endpoint Updated

      In the WebFocus connector, an issue due to a change in the authentication API endpoint has been resolved. The connector now uses the updated API endpoints for successful authentication.

      Hotfix Release6.3.4.23

      This hotfix release includes improvements and bug fixes in the Connectors module. 

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.23

      Release6.3.4.23.63423eb1ba77

      June 05, 2025

      Connector 

      New & Improved

      Improved Lineage for Parameterized Reports

      In Lineage, the application previously built lineage based on parameterized code, which resulted in temporary tables appearing in the lineage view. Now, the system accurately builds complete lineage even when parameterized values are used, as long as the source table has been crawled in OvalEdge. This enhancement ensures a more precise and more reliable representation of data flow for parameterized reports.

      Bridge Client Logs Accessible in Application

      In the OvalEdge application, logs generated on the Bridge client were not visible, which limited insight into client-side operations and made troubleshooting difficult.

      The system now captures and displays these logs within the application, improving diagnostics and troubleshooting.

      Fixed

      S3 NAR File Update Fix
       In Administration > Connectors > Manage Bridge, an error occurred when updating the NAR file using an S3 link. This issue has been fixed. Users can now update the NAR file through the S3 link without errors.

      Accurate Connector Health Display
       In Administration > Connectors > Delta Lake, the connector health status was incorrectly changing from green to red. The issue has been resolved. The health status now accurately reflects the connector’s validation results, ensuring reliable monitoring.

      Hotfix Release6.3.4.24

      This hotfix release includes enhancements and bug fixes in connector and migration validation metrics.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.24

      		 Reelase6.3.4.24.6342411299bb

      5th June 2025

      Connector

      Fixed

      Auto Lineage Build | Parsing Error for Specific Report Codes
       In the SAP BO connector, a parsing error occurred during Auto Lineage Build for specific report codes. After metadata crawling, some reports failed to generate lineage due to syntax or structural issues in the report code, resulting in a partial lineage build. This issue has been resolved. All supported reports are now correctly parsed and processed during Auto Lineage Build operations.

      Lineage Report Count Mismatch | Built Lineage Page vs. Data Catalog

      In the SAP BO integration, the number of reports displayed on the Built Lineage page did not match the count in the Data Catalog. This caused confusion when validating report metadata and assessing lineage coverage. The issue has been resolved. Report counts are now accurate and consistent across both the Built Lineage page and the Data Catalog.

      Missing Report Column Details Post Lineage Build

      In the SAP BO connector, the lineage build process failed to capture column details, leading to missing columns in the Data Catalog. This was caused by backend errors during the post-processing step. The issue has been resolved. The lineage logic now accurately extracts and displays all column metadata, and the process completes without errors.

      Migration Framework

      New & Improved

      Migration Metrics Database | OETP for Pre/Post Validation

      In the migration framework, a new Migration Metrics Database, called the Operational Execution Tracking Plan (OETP), has been introduced to support accurate and consistent environment migrations. This framework captures snapshots before and after migration to validate system states.

      Key features include:

      • Row count validation and data value change checks
      • Connector validation (status and count)
      • Service Desk status updates (integration and service requests)
      • Project task status validation
      • Business Glossary metrics (domain, category, sub-category totals; draft vs. published terms)
      • DQRs (draft vs. published states and property validation)

      Functional Modules Tracked Include:

      • Service Desk: SR counts, status distribution
      • Templates: SDT master field count, field distribution
      • Integrations: Health verification, future health check logic
      • Approval Workflows: Workflow and actor counts
      • System Settings and External APIs

      Hotfix Release6.3.4.25

      This hotfix release includes bug fixes in the Inbox Notifications, Business Glossary, Oracle Analytics Server, and Power BI Connectors.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.25

      Release6.3.4.25.63425f82c4e0

      10th June 2025

      Inbox

      Fixed

      Missing Notifications for Stewards and Owners 

      In the collaboration workflow, an issue where stewards or owners were not notified of comments or questions posted on their data objects unless directly tagged has been resolved. Stewards and owners now automatically receive notifications for all collaboration activities on their assigned objects.

      Business Glossary 

      Fixed

      Business Glossary Custom Fields Filter Issue

      In the Business Glossary, an issue where filtering custom fields failed to exclude records with None values has been resolved. Previously, even when users applied a filter to exclude None, such records continued to appear in the results. Users can now see the correct results.

      Connector

      Fixed 

      Oracle Analytics Server | Incorrect Connector Type Display

      In the Oracle Analytics Server connector, an issue where the Connector Type attribute is displayed as "RDBMS" instead of "Reports" has been resolved. This incorrect label appeared when viewing the connector details. Users will now see the correct Connector Type as "Reports."

      Power BI | Incomplete Lineage for Workspace

      In the Power BI connector, an issue where lineage for BigQuery sources was not fully built in the workspace has been resolved. Although the lineage build showed a "Success" status, datasets failed to capture complete source lineage due to expression-based references. Users will now see accurate and complete lineage for all BigQuery sources in the workspace.

      Hotfix Release6.3.4.26

      This hotfix release includes enhancements and bug fixes in the connector and lineage mapping.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.26

      Release6.3.4.26.6342606a6cf8

      10th June 2025

      Connector

      Fixed

      Redshift Stored Procedures | Crawl Failure
      In the Redshift connection, some stored procedures were not previously crawled into OvalEdge due to limitations in metadata extraction. This issue has been resolved. The improved extraction process now ensures that all stored procedures are successfully crawled and available in the data catalog.

      Amazon QuickSight | Crawl Job Getting Killed
      In Amazon QuickSight, metadata collection jobs were failing with a 'Killed' status. The process only gathered analysis data, excluding dashboards, datasets, and roles. This occurred when accessing deleted or unpublished dashboards. The updated process now handles these cases effectively.

      Azure Data Factory (ADF) connector | Column Lineage Not Building
      In the Azure Data Factory (ADF) connector, column-level lineage failed to generate for certain Azure SQL tables, even with correct source mappings. This issue has been resolved by validating the lineage build logic and verifying pipeline configurations.

      Lineage

      Fixed

      Redshift to QuickSight | Column Lineage and Code View Missing
      In the Redshift to QuickSight integration, graphical column-level mappings and transformation codes were missing on the Lineage page. This issue has been resolved. Users can now view both graphical column-level lineage and SQL code in the respective tabs.

      Amazon QuickSight connector | Temporary Lineage Correction Not Generating Recommendations
      In the Amazon QuickSight connector, temp lineage merge recommendations were missing for previously uncrawled objects. This issue has been resolved. Users will now receive correct recommendations during the temp lineage merge process.

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