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.

      Hotfix Release6.3.4.27

      This hotfix release includes bug fixes in the Mail Notifications, Global Search Results, Service Request Template, and Users & Roles. 

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.27

      Release6.3.4.27.634273429e47

      11th June 2025

      Inbox

      Fixed

      Broken Links in Metadata Change Notifications

      In metadata change email notifications, an issue where links did not navigate to the intended pages has been resolved. Notification links now open the associated metadata pages correctly.

      Global Search 

      Fixed

      Old Domain Name Displayed in Global Search Filters

      In Global Search, an issue where a renamed domain continued to appear under its old name in the search filters has been resolved. Only the updated domain name now appears in the filter panel.

      Service Desk 

      Fixed

      Missing Business Description Field in Tags SR Template

      In the Tags Service Request template, an issue where users could not provide a business description for tags has been resolved. The template now includes a business description field to capture detailed tag information.

      Hotfix Release6.3.4.28

      This hotfix release includes bug fixes in the Data Classification Recommendations, Connectors, and Build Auto Lineage. 

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.28

      Release6.3.4.28.634289f839c6

      12th June 2025

      Data Classification Recommendations

      Fixed

      AI Model Job Status Mismatch

      In Governance Catalog > Data Classifications Recommendations, an issue where AI Model jobs that were terminated (status: Killed) in the job logs continued to display as 'In Progress' on the Data Classification model page has been resolved.

      Connectors 

      Fixed

      OAS Report Group Crawling Error Resolved

      In Administration > Connectors, an issue occurred while crawling certain report groups from the OAS connection has been resolved. Users will now be able to crawl those report groups without errors.

      Build Auto Lineage 

      Fixed

      Accurate Display of Lineage Status and Error Messages

      In Advanced Tools > Build Auto Lineage, an issue where the Lineage Status and error message were not displayed appropriately has been resolved. Users will now see accurate lineage statuses and relevant error messages.

      Hotfix Release6.3.4.29

      This hotfix release includes enhancements and bug fixes in the Application, Advanced Job, and Tags modules.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.29

      Reelase6.3.4.29.6329ac5d60c

      13th June 2025

      Application

      Fixed

      Spanish Version | Character Encoding Issue

      In the Spanish version of OvalEdge, special characters and accent marks (such as á, é, í) were displayed incorrectly. For example, the word “Políticas” appeared as “Polìticas” in the Helpful Resources section. The issue has been resolved. Now the user can view all special characters correctly across the application.

      Advanced Job

      New & Improved

      Masking Sync for Azure SQL Managed Instance

      In the SQL Server integration, the Masking Sync (Advanced Job) has been reintroduced and extended to support Azure SQL Managed Instance. This enhancement allows OvalEdge to detect masked columns and apply default masking policies within the platform. Due to platform limitations, only column-level masking detection is supported, and authorized roles or users exempted from masking are not automatically captured.

      Tags

      Fixed

      Non-Assignable Tags | “New” Option Missing When Adding Child Tags
      In the Tag Summary Page, users were unable to view the “New” option when attempting to add child tags to a non-assignable tag that already had over 150 child tags. The issue has been resolved. Now the user can add new child tags to non-assignable tags without any limitations.

      Connectors

      Fixed

      Connector Validation Issue Resolved

      In Administration > Connectors, an SSL certificate trust issue that prevented connection validation for Microsoft SQL Server, Informatica PowerCenter, and IBM Cognos Analytics has been resolved. Users can now successfully validate connections for all three connectors.

      Hotfix Release6.3.4.30

      This hotfix release includes bug fixes for Service Desk Ticket Creation, Power BI Cloud Lineage, and Azure Key Vault Connector Authentication.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.30

      		   18th June 2025

      Service Desk 

      Fixed

      Missing Epic Field Prevented Azure DevOps Ticket Creation

      In the Service Desk, an issue where tickets from Data Quality Rules failures were not synced to Azure DevOps after token renewal has been resolved. The system previously failed to create Azure DevOps tickets when the Repost button was used, due to missing Epic field values in the backend. With the backend values corrected, ticket syncing now works as expected.

      Lineage 

      Fixed

      Incorrect Lineage Status Displayed

      In Power BI Cloud, an issue where reports without layout files were incorrectly showing a successful lineage build has been resolved. The system now accurately flags these reports with a "failed to build lineage" message when layout files or dataset tables are missing.

      Connectors

      Fixed

      Azure Key Vault Authentication with Managed Identity

      In Azure Key Vault Connector, an issue where the connector could not be authenticated using Managed Identity has been resolved. The system now supports secure access without requiring explicit credentials.

      Hotfix Release6.3.4.31

      This hotfix release includes bug fixes for My Profile, Data Catalog, Business Glossary, and Lineage.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.31

      		    

      My Resources 

      Fixed

      Improved Dropdown Behavior in My Resources
      In My Resources, an issue caused the dropdown menu to remain visible after accidental hovering has been fixed. The dropdown now opens only when clicked and closes when clicking outside of it.

      Data Catalog 

      Fixed

      Qlik Sense Column Types Now Display Correctly
      In Data Catalog > Reports, an issue where report column types (Measure, Dimension) did not appear for the Main Report after crawling data from the Qlik Sense (On-Prem) connector has been resolved. The Data Catalog now displays these column types correctly.

      Azure SQL Lineage Mapping Issue Resolved
      In Data Catalog > Object Summary > Lineage, an issue where column lineage was not generated for Azure SQL tables, even when mappings existed in the source code, has been resolved. The system now correctly builds column lineage in these cases.

      Business Glossary

      Fixed

      Updated Curation Score Logic for Governance Roles
      In the Business Glossary > Term Summary, an issue occurred where the metadata curation score for Governance Roles of a term did not increase if the steward or owner had the OE_Admin role. This has been resolved. Now, if the steward or owner (user) is the configured default admin principal, the governance roles score remains unchanged. If they are different, the curation score of governance roles will increase by 5 points.

      Hotfix Release6.3.4.32

      This hotfix release includes bug fixes in the Data Catalog, Data Quality, Lineage, and Connector modules.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.32

      Release6.3.4.32.634328d2c11c

      20th June 2025

      Data Catalog

      Fixed

      Reference Data Management | "@" Functionality Not Working in Description Field

      In Reference Data Management, the "@" mention feature was not functioning as expected in the description field. When users attempted to insert "@" while editing, the expected behavior was not triggered. This issue has been resolved. Now, the "@" functionality operates correctly within the description field.

      Data Quality

      Fixed

      Result Value | Incorrect Status Display for DQ Rules

      In the Data Quality module, an issue in the result evaluation logic caused DQ rules to display a “Passed” status even when the pass percentage was slightly below 100%, and failed records were not shown. This issue has been fixed. The Result Value now correctly displays a “Failed” status when any records fail, and all failed records are shown as expected.

      Lineage

      Fixed

      PowerBI | Missing Tables in Semantic Layer

      In the Power BI integration, two important tables were missing from the semantic models. Additionally, lineage was not generated for one of the tables, despite the presence of a data flow. These issues have been resolved. All missing elements are now correctly reflected in the semantic models and lineage views.

      Connectors

      Fixed

      SharePoint | SharePoint Assets Not Loading in File Explorer

      In the File Explorer, users were unable to access SharePoint assets beyond the first-level folders within the application. Attempting to open subfolders resulted in continuous loading without displaying contents. This issue has been resolved. Users can now browse and access SharePoint folders and assets as expected.

      Teradata | Incomplete Column Retrieval for Views

      In the Teradata connector, crawling a view resulted in only a partial set of columns being retrieved. The crawl process has been corrected to capture complete column metadata. All columns in Teradata views are now accurately retrieved and reflected within the application.

      Hotfix Release6.3.4.33

      This hotfix release includes bug fixes in the Advanced Jobs and Connectors modules.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.33

      Release6.3.4.33.63433120a24f

      23rd June 2025

      Advanced Jobs

      Fixed

      Job Killed During Queries extraction from the source to build the lineage

      In the Advanced Jobs module, the job “Extract Queries from the Source to Build Lineage” consistently failed with a status marked as KILLED when executed as part of a scheduled workflow. However, it mostly completed successfully when run manually. The issue has been resolved, and the job now runs consistently without termination across both scheduled workflows and manual executions.

      Vertica Connector | Lineage Build Job Failing with Status 'Killed'

      In the Vertica connector, the advanced job “Build Lineage from Extracted Queries” consistently failed during execution, with the job status marked as “KILLED”. This behavior was observed under Administration > Advanced Jobs, where each run of the job ended with failure. The issue has been resolved, and users can now execute the job successfully, completing the lineage build process without interruption.

      Connectors

      Fixed

      DataStage Connector | Lineage Generation Failure

      In the DataStage connector, the process of building lineage was not functioning as expected, which affected the visibility of the data flow. The issue has been resolved, and users can now successfully build and view lineage for the DataStage connector without any interruption.

      Hotfix Release6.3.4.34

      This hotfix release includes bug fixes in the Jobs and Power BI Connector.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.34

      		   25th June 2025

      Jobs

      Fixed

      Connection Failures After Running the "ReEncrypt DB Data" Job

      In the SaaS environment, some Secret Manager connections stopped working after running the "ReEncrypt DB Data" advanced job. This issue has now been resolved. After running the job, all configured connections continue to function correctly and authenticate without any issues.

      Connectors 

      Fixed

      Incorrect Lineage Status for Bulk Reports

      In the Power BI Connector, some reports built in bulk showed incorrect lineage status. This issue has been fixed. Now, all reports display the correct lineage without the need to rebuild them individually.

      Support has also been added for new data source types, such as SharePoint.Files and sentinelDailyIncubatedAlerts, to ensure complete and accurate lineage across all supported report types.

      Hotfix Release6.3.4.35

      This hotfix release includes bug fixes for Data Catalog, Connectors, Lineage, and Load Metadata from Files modules.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.35

      Release6.3.4.35.63435243ed03

      26th June 2025

      Data Catalog 

      Fixed

      Archived Tags/Terms History Now Retrievable
      In the Data Catalog > Object summary, an issue with the missing terms and tags history due to archival has been resolved. An advanced job named ‘Restore Archived Data’ is introduced to retrieve historical data related to tags and terms that were previously archived and not visible in the application.

      QlikSense Lineage Flow Displays Completely
      In Data Catalog > Report Summary, an issue where the complete QlikSense lineage flow was not visible in the Lineage tab has been resolved. The complete lineage flow is now visible.

      Load Metadata from Files 

      Fixed

      Table Column Template Upload Now Handles -1 Values
      In Advanced Tools > Load Metadata from Files, an issue related to uploading the Table Column template has been resolved. Previously, setting the ColumnLength field to -1 triggered an error message: "Only numeric values are accepted for ColumnLength -1." The system now correctly processes -1 as a valid input, and the error no longer occurs during file uploads.

      Connectors

      Fixed

      Improved API Support for Dell Boomi Connector
      In Administration > Connectors, the Dell Boomi connector has been enhanced to support API calls retrieving more than 100 datasets per call. The previous limitation, which restricted retrieval to only 100 datasets, has been resolved.

      Tableau Connector Validation Issue Resolved

      In Administration > Connectors, the gateway timeout error that occurred during Tableau connector validation has been fixed. The Tableau connector now validates successfully without encountering this issue.

      Hotfix Release6.3.4.36

      This hotfix release includes bug fixes in the Business Glossary, Data Quality, Lineage, and Connectors modules.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.36

      Release6.3.4.36.63436dd38cac

      27th June 2025

      Business Glossary

      Fixed

      Glossary Term | AI-Generated Business Description Auto-Filled

      In the glossary term module, the system auto-filled the Detailed Description with the AI-generated Business Description after refreshing the summary page, even without user action. The issue has been resolved. The Detailed Description now remains empty until the user chooses to generate the content.

      Data Quality

      Fixed

      Table Column View | Incorrect Data Quality Rules Count

      In the Data Catalog, rule counts in the table column view failed to align with the applied data quality rules. The issue has been resolved. The rule count now shows the correct value for each column.

      Lineage

      Fixed

      Tableau Connector | Lineage Build Job Delayed for Specific Report Group

      In the Tableau On-Prem connector, the lineage build for a report group failed to run as expected. The issue has been resolved. The lineage build now completes successfully without interruption.

      Connectors

      Fixed

      Qlik Sense Connector | Missing StreamID and AppID in Report Group Details

      In the Qlik Sense connector, the Crawl and Profile page showed only Report Group names and crawl status. It now shows StreamID and AppID with each Report Group for clear identification and accurate selection.

      Hotfix Release6.3.4.37

      This hotfix release includes bug fixes in the DQR, File Manager, and Connectors.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.37

      		   02nd July 2025

      DQR

      Fixed

      DQR Custom Fields Display Issue

      In Data Quality Rules, an issue where undefined custom fields were appearing in the rule configuration has been resolved. Previously, custom fields not available in the system were still visible in the rule editor. Now, only valid and configured custom fields are displayed.

      File Manager 

      Fixed

      Data Lake OvalSight - File Size Mismatch

      In Data Lake OvalSight, an issue where file sizes in the File Size Ranges tab did not match those shown in the File Manager has been resolved. File size values are now consistent across both views.

      Connector

      Fixed 

      DataStage Lineage Generation Issue

      In the DataStage connector, an issue that prevented lineage from being generated in Release6.3.4.1 has been resolved. Lineage generation now works as expected, consistent with the functionality available in Release6.2.1.18.

      MicroStrategy Cloud Connector 

      The MicroStrategy connector has been enhanced to support integration with MicroStrategy Cloud. This update enables organizations migrating from MicroStrategy On-Premise to Cloud to establish a seamless connection between their cloud environment and the OvalEdge platform for metadata extraction and lineage building.

      Hotfix Release6.3.4.38

      This hotfix release includes bug fixes in the Connectors and Lineage modules.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.38

      		  

      1st July 2025

      Connectors

      Fixed

      MicroStrategy Connector | Validation Passed with Invalid IServer Value

      In the MicroStrategy connector, the system validated the connection even when an invalid IServer value was provided. This issue appeared in both Cloud and On-Prem environments. The issue has been resolved, and the validation process now correctly identifies and blocks invalid IServer values.

      Column Prioritization | Mechanism for Important Columns

      In the profiling module, the mechanism for identifying and prioritizing essential columns based on their importance score has been removed. The profiling now follows a standard order without prioritization.

      Lineage

      Fixed

      Oracle Connector | Incomplete Lineage for Triggers

      In the Oracle connector, the lineage for certain triggers was either incomplete or missing during the build process. The system now builds accurate and consistent lineage for all triggers through the advanced job execution.

      Hotfix Release6.3.4.39

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

      Release6.3.4.39.6343948e4800

      3rd July 2025

      Data Catalog

      Fixed

      Tables - Relationships

      • In Data Catalog > Tables > Relationships, an issue occurred where accessing the relationship code triggered an "Invalid Query" error due to an incorrect URL. Although the code was accessible through the Data Catalog Codes search, direct access from the Relationships section failed. This issue has been resolved, and relationship codes are now accessible as expected from the Relationships section.
      • Users were unable to delete relationships from the Entity Relationships table, as the delete action failed silently without any error or confirmation message. This issue has been resolved. Delete actions now function as expected with the appropriate system response.

      Connectors 

      Fixed

      Quick Sight Crawling Issue 

      In the QuickSight Connector, while crawling, errors were generated in the logs that caused the job to terminate before completion. This issue is now resolved. Crawling jobs complete successfully without interruption, and metadata is extracted as expected.

      ADF Schema - Crawling

      In the ADF Schema, crawling failed due to improper exception handling when retrieving remote datasets. The response from the server caused the process to stop before completion. The issue is resolved. Crawling now completes without errors, and metadata is retrieved as expected.

      Dell Boomi | Incomplete Dataset Crawling

      In the Dell Boomi Connector, the API failed to retrieve all datasets and did not capture source codes for some datasets during the crawling process. This issue has been resolved. All datasets are now successfully retrieved, and source codes are accurately captured.

      Hotfix Release6.3.4.40

      This hotfix release includes bug fixes in the Data Catalog, Connectors, Advanced Jobs, and File Explorer modules.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.40

      Release6.3.4.40.634406cc5764

      4th July 2025

      Data Catalog

      Fixed

      Valid SQL Queries Now Run After Format Edits

      In Data Catalog > Code Summary, an issue occurred where formatting a valid SQL query (such as adding spaces or line breaks) resulted in an "invalid query" error. This issue has been resolved, and users can now format and execute valid queries without encountering any errors.

      File Explorer

      Fixed

      SharePoint Access Issue Resolved

      In File Manager > File Explorer, an issue occurred that prevented access to SharePoint files. This issue has been resolved, and SharePoint files can now be accessed and browsed without any problems.

      Advanced Jobs

      Fixed

      Consistent Object Counts in ADL Catalog Job Output
      In Advanced Jobs > Intelligent ADL Catalog, the number of objects listed in the master sheet did not match the number of files cataloged after job execution. This issue has been resolved, and the object counts in the master sheet now correctly reflect the number of cataloged files.

      Connectors

      Fixed

      Dell Boomi Connector Retains Auto Lineage Selection
      In Administration > Connectors > Dell Boomi, an issue where the Auto Lineage checkbox appeared unchecked on the connector edit page, even after it was enabled and validated during the connector validation process, has been resolved. Now, the checkbox stays checked as expected after validation.

      Include/Exclude Unpublished Apps Drop-down Option
      In Administration > Connectors > Qlik Sense On-Prem, a new dropdown option has been added to the connector edit page, allowing users to include or exclude unpublished apps during configuration. This provides better control over the data fetched from Qlik Sense On-Prem environments.

      Hotfix Release6.3.4.41

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

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.41

      Release6.3.4.4.1.6344141d2178

      7th July 2025

      Data Catalog

      Fixed

      Data Catalog | Business Description Overlap in Full Screen Mode

      In the Business Description editor, the issue with content overlapping in full screen mode on the Data Catalog page has been resolved.

      Connectors

      Fixed

      Connector | Database Account Lockout Due to Credential Mismatch

      In the Connectors module, job pods used outdated credentials after users updated passwords in the UI pod. Repeated connection attempts caused the database account to lock. The system now syncs credentials before attempting connection requests to prevent this issue.

      Hotfix Release6.3.4.42

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

      Release6.3.4.42.63442272d3e6

      9th July 2025

      Data Catalog 

      Fixed

      Synapse | Missing Tables 

      In Synapse Connector, tables were missing in the production environment but were visible in the development environment. This occurred because the firewall blocked API calls from the Tableau Server. The issue has been resolved by adding the User-Agent header to the API request. All expected tables now appear correctly in the production environment.

      Connectors 

      Fixed

      Qlik Cloud | Missing Columns in Master Objects

      The Qlik Cloud connector was not fetching columns or expressions for master objects, leading to incomplete metadata and broken lineage. This issue has now been resolved. Columns and expressions related to master objects are now correctly retrieved.

      Hotfix Release6.3.4.43

      This hotfix release includes bug fixes in the Lineage, Connectors, Integrations, and Projects modules.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.43

      Release6.3.4.43.63443ced9036

      10th July 2025

      Lineage

      Fixed

      Informatica Lineage | Incorrect Status Displayed for Mappings

      In the Lineage module, most mappings displayed incorrect success messages despite missing lineage. The system now accurately detects the presence of actual lineage and updates the status accordingly.

      Qlik Sense Lineage | Gaps Caused by Dropped Tables and SQL Variants

      In the Qlik Sense lineage, dropped table references and inconsistent SQL formats created incomplete lineage paths. The system now supports more SQL patterns and detects dropped objects to provide complete lineage.

      Integrations

      New & Improved

      Jira Integration | Create issues or browse projects in Jira

      In the Jira integration setup, the security model has been enhanced to streamline the configuration process. Users with permission to access projects or create issues in Jira can now configure the integration directly within the application. This makes it easier to manage and track service requests across both platforms.

      Projects

      Fixed

      Assigned Task | Navigation Failure to Associated Objects

      In the task assignment workflow, navigation from the homepage or notifications to linked objects failed with an error message. The system now routes the user correctly to all supported object types, including columns and APIs.

      Connectors

      Fixed

      Credential Manager | Missing Governance Role Assignment

      In the Connectors module, governance roles such as Owner, Steward, Custodian, and custom roles did not appear for credential-based connections. The system now displays and applies these roles as expected.

      Hotfix Release6.3.4.44

      This hotfix release includes bug fixes in the Data Catalog, Elastic Search, Connectors, Service Desk, and Jobs modules.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.44

      		    

      Data Catalog

      Fixed

      Governance Roles Filter Now Returns Correct Results
      In Data Catalog Objects Grid View, an issue where the Governance Roles filter did not display the selected data has been resolved. The filter now displays the corresponding results correctly.

      Schema References Can Now Be Added Successfully
      In Data Catalog, an issue that prevented adding object references to schemas has been resolved. Object references can now be successfully added to schemas.

      Elastic Search

      Fixed

      Search Function Restored with Correct Index Mapping
      An issue where Elastic search results failed due to empty index mappings has been resolved. Searches now return accurate results as expected.

      Service Desk

      Fixed

      Unwanted Tag Removed from JIRA Description
      An issue occurred where an extra, unintended HTML tag (a class =”make_bold” href) appeared in the JIRA ticket description after a Data Quality Rule (DQR) failure triggered a service request. This issue has been resolved. The Jira description now displays only the relevant information without this additional tag.

      JIRA Redirect Now Shows Correct Request ID URL
      An issue occurred where a dot (“.”) appeared in the service request ID URL after redirecting from a JIRA ticket generated by a failed Data Quality Rule (DQR). This issue has been resolved. The redirect now correctly displays the service request URL without the extra character.

      Jobs

      Fixed

      Azure SQL Managed Instance Jobs Now Run Successfully
      An issue where crawling and profiling ‘Azure SQL Managed Instance’ connector jobs terminate unexpectedly without displaying any error message has been resolved. Jobs now run and complete without interruption.

      Connectors

      Fixed

      BigQuery Connector Now Validates with Secret Managers
      In the connectors, an issue that caused a "404 not found" error when validating the BigQuery connector with HashiCorp Vault, AWS Secret Manager, and Azure Key Vault has been resolved. The system now successfully reads data from these credential managers during this connector validation.

      Bridge Update Message Now Displays Correctly
      In Bridge, an issue where updating the NAR file through the "Manage Bridge" option displayed an incorrect success message has been resolved. The system now shows the correct confirmation message after the update.

      Power BI Connector Now Downloads Layout Files Correctly
      In the Power BI (on-premise) Connector, an issue that caused a “Layout file not found” error during report crawling has been resolved. The connector now successfully downloads the required layout files to the specified directory.

      Hotfix Release6.3.4.45

      This hotfix release includes bug fixes in the Governance Catalog, Advanced Jobs and Connectors.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.45

      Reease6.3.4.45.634450010f66

      15th July 2025

      Governance catalog

      Fixed

      Primary Term Displayed as Auxiliary Term

      In the Governance Catalog, a Primary Term under the VSP domain was incorrectly displayed as an Auxiliary Term in the Data Classification Recommendations after running the AI model. This issue has now been resolved. Primary Terms now appear correctly in the recommendations.

      Advanced Jobs

      Fixed

      Extract Queries Job Failed with OutOfMemoryError

      The job 'Extract Queries from Source to Build Lineage' was failing due to a java.lang.OutOfMemoryError: GC overhead limit exceeded, caused by memory overload during execution. This issue has now been resolved. The job now runs successfully without memory errors.

      Connectors 

      Fixed

      Redshift | Profiling Job Failed for Large Tables

      Profiling failed for large Redshift tables due to a SQL syntax error caused by unquoted reserved keywords in the LIMIT ? OFFSET ? clause. This issue has now been resolved. Profiling now runs successfully on large Redshift tables.

      QlikSense (On-Prem) | Crawling Job Stuck with No Progress

      The crawling job for QlikSense (On-Prem) was running without progress for nearly two days after initiation. Validation confirmed that the job was stuck with no advancement. This issue has now been resolved. The crawling job now completes successfully within the expected time.

      Hotfix Release6.3.4.46

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

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.46

      Reelase6.3.4.46.634461591bf9

      16th July 2025

      Lineage

      Fixed

      Dataset Mapping | Missing Table in Power BI Lineage

      In the Power BI integration, a source table was missing from the dataset mapping after the connection was set up. The system now includes all connected tables as defined in the source. After crawling and building the lineage, the mapping view shows the complete set of tables.

      Data Catalog

      Fixed

      View Profile History | Displays Blank Page

      In the profile history view, the page failed to open for certain large tables due to an issue with the data ordering. The system now processes the data correctly and displays the profile history page as expected.

      Hotfix Release6.3.4.47

      This hotfix release includes gap enhancements and bug fixes in the Query Sheet and Data Quality Rules.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.47

      Reelase6.3.4.47.63447790dd4f

      18th July 2025

      Advanced Jobs

      Fixed

      An issue was identified where the 'Extract Queries from Source to Build Lineage' job was failing due to an exception, and has now been handled through the enhanced logic.

      Data Quality Rules

      Fixed

      Performance Issue with Data Quality Queries
      An issue was identified where certain queries were causing a high load on database tables due to poor indexing. These queries, used for calculating average scores across various data quality dimensions, resulted in performance degradation due to extensive table scans.

      The queries have now been optimized to improve efficiency and reduce scan load, and the system is now performing as expected.

      Query Sheet

      New & Improved

      SQL Query Formatting

      In the Query Sheet and Data Catalog, saved SQL queries now retain their original formatting as written.

      • Previously, saved queries were automatically reformatted when viewed in the Query Sheet collaboration window or the Data Catalog’s code summary.
      • This reformatting altered critical aspects of SQL structure, such as indentation, line breaks, and alignment. As a result, complex queries became difficult to read, interpret, and debug.
      • The automatic reformatting feature has been removed. Saved queries now display exactly as initially written and saved, maintaining all original line breaks, indentation, and alignment.

      Note: Please ensure that commenting out the first line of a SQL query has been identified as a known gap, where execution should ideally not proceed. Please share the information with the client.

      Hotfix Release6.3.4.48

      This hotfix release includes bug fixes for the Data Catalog and Qlik Sense On-Prem Connectors.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.48

      Release6.3.4.48.634486a5dc7c

      21st July 2025

      Data catalog

      Fixed

      Incorrect Spanish Translation for Report Terminology

      The term 'Report' was incorrectly translated as 'Informe' throughout the application, rather than being translated as 'Tablero'. Additionally, the 'Parent Report' field in Data Catalog > Report was not translated into Spanish. This issue has now been resolved. The application now consistently uses 'Tablero' for 'Report', and the 'Parent Report' field is translated correctly.

      Connectors 

      Fixed

      Partial Success in Crawling Report Groups in Qlik Sense (On-Prem)

      The crawl operation for a report group in Qlik Sense (On-Prem) resulted in partial success due to a synchronization issue. This issue has now been resolved by limiting the crawl to a single report. Crawling of report groups is now completing successfully.

      Incorrect Lineage Mapping in Qlik Sense (On-Prem)

      The lineage was displaying alias names instead of actual source names and linking unrelated elements because variables were not replaced with actual values during extraction. This issue has now been resolved. The lineage now reflects correct source names and valid relationships.

      Hotfix Release6.3.4.49

      This hotfix release includes bug fixes in the Lineage and Business Glossary modules.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.49

      Release6.3.4.49.63449a726c1c

      22nd July 2025

      Business Glossary

      Fixed

      Business Glossary | Issue with Endorsement Search

      In the Business Glossary list view, the endorsement search failed to return accurate results when using a custom view. The system now processes search queries correctly and shows accurate results without errors.

      Lineage

      Fixed

      Power BI | Lineage Status Not Handled Properly

      In the Power BI lineage view, the status was not matching with the lineage when multiple statuses appeared in the query results. The system now handles multiple statuses correctly and displays the correct lineage status.

      Hotfix Release6.3.4.50

      This hotfix release includes bug fixes for the Business Glossary, Dashboards, and Lineage.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.50

      Release6.3.4.50.634506621847

      24th July 2025

      Business Glossary

      Fixed

      Clone Term Option for Published Glossary Terms

      In the Business Glossary Term Summary, an issue prevented published terms from being cloned after a specific period, causing the "Clone Term" option to appear greyed out. This issue has been resolved. Published terms can now be cloned as expected.

      Dashboards 

      Fixed

      Edit Icon Display Corrected in Security Dashboards

      In Security Dashboards, an issue caused edit icons to appear misaligned when hovered over dashboards with special characters in their names. This issue has been resolved. Special characters are now validated during dashboard creation, and edit icons display correctly when hovered over.

      Lineage

      New & Improved

      Lineage Support for Amazon QuickSight Unsupported Datasets

      In both Remote and Local Amazon QuickSight environments, certain dataset types are not supported by the SDK API for metadata extraction during crawling. To enable lineage building, the OvalEdge now constructs lineage for these unsupported table objects that are crawled from the Amazon QuickSight source.

      Note: Due to API limitations, column-level lineage will not be generated for these dataset types.

      Hotfix Release6.3.4.51

      This hotfix release includes bug fixes for the Business Glossary, Data Catalog, Audit Trails, Custom Fields, and Connectors. 

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.51

      Reelase6.3.4.51.63451781383b

      24th July 2025

      Business Glossary 

      Fixed

      Incorrect Error Message Displayed When Saving Text in Number Field

      On the Business Glossary > Term Summary page, the system displayed an incorrect error message when users entered text into a number-type custom field and attempted to save. This issue is now fixed. The application now blocks invalid entries and displays the correct error message.

      Data Catalog 

      Fixed

      Improper Display of Dashboard Names in Report Addition Flow

      In the Reports dashboard, names were not displaying correctly when adding reports to a dashboard. Two issues were identified:

      • Long dashboard names were not shortened with ellipses, resulting in text overflow.
      • Dashboard names with special characters did not display correctly.

      These issues have been resolved. Long names are now neatly truncated with ellipses, and special characters are displayed correctly.

      Audit Trails 

      Fixed

      Missing Timestamps When Restoring Backup from CSV Archive for a_wiki Table

      While restoring backup data from archival CSV files, the lastupdatetime column for the table was missing. This occurred because the backup job did not populate the lastupdatetime field when storing data in CSV format. This issue has now been resolved. The backup process has been corrected to include the lastupdatetime field in the CSV output. 

      Custom Fields 

      Fixed

      Spelling Error for Table Column Object Type

      In the Administration > Custom Fields, when selecting the object type as Table Column and navigating to the System Fields tab, the field Null Value Percentage was incorrectly displayed as Null Percentage (spelling mistake). This issue has now been resolved. The field label is correctly displayed as Null Value Percentage.

      Connectors 

      Fixed

      Incorrect Tooltip Text for Oracle Analytics Server Connector

      The tooltip for the Oracle Analytics Server connector displayed 'Oracle Analytics' instead of 'Oracle Analytics Server'. This issue has been resolved. The tooltip now correctly displays Oracle Analytics Server as intended.

      Hotfix Release6.3.4.52

      This hotfix release includes bug fixes in the Data Quality, Lineage, and Advanced Jobs modules.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.52

      Release6.3.4.52.63452781383b

      25th July 2025

      Data Quality

      Fixed

      Data Quality | Missing Cataloged Queries from query sheet

      In the Data Quality page, queries written in the Query Sheet for custom rules were missing from the associated objects section. These queries appeared in Global Search but showed an "Access Denied" error when opened. This issue has been resolved, and the queries are now visible and accessible without errors.

      Advanced Jobs

      Fixed

      Advanced Jobs | Job displayed Killed status without errors

      In the Advanced Jobs module, the 'Build Lineage from Extracted Queries' job was displayed as "killed" even though it continued to run in the backend. No errors were logged, leading to confusion about the job’s progress. This issue has been fixed. The job now displays the correct status and logs throughout execution.

      Lineage

      Fixed

      Lineage Jobs | Incorrect Status Display for Snowflake Lineage Jobs

      In the Lineage Jobs section, Snowflake lineage jobs incorrectly displayed a 'killed' status, and execution timestamps were not recorded during runtime. This issue has been fixed. Job status and execution details now update correctly throughout the process.

      Lineage | Issue in Query Details During Report Group Re-Crawl

      In the lineage process, expected query details were replaced with incorrect values during each report group re-crawl, resulting in "Invalid Params" errors on the Lineage Build page. This issue has been resolved. The expected details are now retained during re-crawls, and lineage rebuild executes as expected.

      Hotfix Release6.3.4.53

      This hotfix release includes bug fixes & improvements for the Job Workflow, Lineage, Advanced Jobs, and Connectors.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.53

      		    

      Lineage

      New & Improved

      Enhanced Lineage Support for SAP BODS Workflows
      The lineage construction in the SAP BODS connector was limited to Dataflows. With this enhancement, lineage is now built based on workflows as well, providing a complete and accurate representation of data movement and dependencies.

      Job Workflow 

      Fixed

      Job Workflow Selection Issue Resolved
      In Job Workflow, an issue occurred where selecting all items on one page and navigating to the next would cause checkboxes to appear deselected. However, the Delete option in the 9 Dots action menu remained enabled. This issue has been resolved. Now, the Delete option is correctly disabled when no items are selected.

      Connectors

      Fixed

      SQL Server Crawl Failure Due to Collation
      In the SQL Server connector, an issue occurred when initiating the crawling process for SQL Server databases due to collation differences within the database. This issue has been resolved by handling collation mismatches during the crawl.

      Advanced Jobs

      Fixed

      Optimized Build Lineage Job Performance
      In Advanced Jobs, an issue occurred where the 'Build Lineage from Extracted Queries' job was taking excessive time to complete, with several codes remaining in the Unprocessed status after execution. This issue has been resolved by optimizing the job execution logic to ensure that all extracted query codes are processed efficiently within a reasonable timeframe. 

      Hotfix Release6.3.4.54

      This hotfix release includes bug fixes in the Lineage and Connectors. 

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.54

      Release6.3.4.54.6345471ee5579

      29th July 2025

      Lineage

      Fixed

      Lineage Not Established Between BigQuery Table and Tableau Report

      In the Tableau connection, a BigQuery table used in the Insights, detailed report was not parsed in the lineage, despite being present in the Data Catalog and correctly configured with the BigQuery dialect. This issue has now been resolved. The BigQuery table now appears correctly in the Tableau report lineage.

      External Data Source Misclassified as Internal in Tableau Report

      In the Global dashboard, the report’s data source was incorrectly classified as internal due to system checks based on the repository location and the fields. This issue has now been resolved. Data sources with an HTTPS connection channel are now correctly identified as external and treated as original assets for lineage building, even when the repository location is missing.

      Extra Upstream Table Displayed in Unity Catalog Lineage

      In Unity Catalog, the lineage incorrectly displayed two upstream tables, although only one upstream table was present in the JSON. This issue has now been resolved. The lineage now accurately reflects a single upstream table as defined in the source.

      Connectors 

      Fixed

      HTTPS Issue in Unity Catalog API Source Code

      In Unity Catalog, the API did not return the correct source code when the server name included the HTTPS protocol in the connection details. This issue has now been resolved. The connection now works correctly without requiring manual removal of the protocol from the server address.

      Hotfix Release6.3.4.55

      This hotfix release includes bug fixes in the Advanced Tools and Lineage modules.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.55

      		 Release6.3.4.55.634551bob724 30th July 2025

      Advanced Tools

      Fixed

      API | Missing Associated Objects in Bulk DQ Rules Response

      In the API response for bulk Data Quality rules, the associated object data was missing. This created a mismatch with the response for individual DQ rules. The issue has been resolved. The response now includes all associated object data consistently.

      Lineage

      Fixed

      Informatica Cloud | Incomplete Lineage build

      In the lineage view, specific source codes from Informatica Cloud failed to build lineage as expected. The system displayed incorrect target mappings, affecting lineage accuracy. The issue has been resolved. The lineage now builds successfully with correct target mappings.

      Qlik Cloud | Lineage Build Issues

      In the Qlik Cloud connector, lineage did not generate as expected for multiple spaces. The system failed to capture accurate lineage paths. This issue has been resolved. The lineage now builds correctly across all spaces.

      Hotfix Release6.3.4.56

      This hotfix release includes bug fixes in the Lineage, Audit Trials, and Connectors modules.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.56

      Release6.3.4.56.63456d4cb8ad

      31st July 2025

      Lineage

      Fixed

      Accurate Lineage Now Builds for ADF Fact Table
      In the ADF connector, an issue occurred where the lineage for the Azure SQL fact table "f_job_actual_from_fcast" was not building correctly. The system generated only partial lineage and included duplicate paths. This issue has been resolved. The lineage now builds completely and accurately without duplication.

      Audit Trials

      Fixed

      Object Type Now Displays Correctly as 'Code'
      In the Audit Trials Catalog Description, an issue occurred where the object type filter displayed as 'Code', but the object type column showed 'Query' instead. This mismatch has been corrected, and the object type column now accurately displays 'Code' as expected.

      Connectors

      Fixed

      Power BI Report Group Job Now Completes Successfully
      In connectors, an issue occurred after crawling the Power BI Report Group; the job logs displayed a partial success status with errors such as "error while fetching remote databases" and associated warnings. This issue has been resolved. The Power BI Report Group job now completes successfully and crawls as expected.

      Hotfix Release6.3.4.57

      This hotfix release includes bug fixes in the Elastic Search, Data Catalog, Business Glossary, and Connectors.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.57

      Release6.3.4.57.634570dd6c8a

      1st Aug 2025

      Elastic Search 

      Fixed

      Elasticsearch Results Not Displayed in Results Tab

      In the Elasticsearch Results tab, results were not displayed after running the Elastic Advanced Job, despite successful schema insertion into the mounted path. The issue was specific to an environment where only the UI Pod was available, while another environment with both UI and Job Pods functioned as expected. This issue has now been resolved. The Results tab correctly displays the Elasticsearch results as intended.

      Data Catalog 

      Fixed

      Informatica Connection Not Displayed in Connector Name Filter

      In the Data Catalog → Codes page, the Informatica connection was not displayed in the Connector Name filter, although it appeared correctly in the Schema filter with the associated schema name. This issue has now been resolved. The Connector Name filter correctly displays the Informatica connection as intended.

      Business Glossary 

      Fixed

      Primary Term Incorrectly Displayed as Auxiliary Term 

      In the Governance Catalog, a Primary Term under the domain was incorrectly classified as an Auxiliary Term in the Data Classification Recommendations generated by the AI model. This issue has now been resolved. The AI model correctly identifies and displays Primary Terms as intended in the recommendations.

      Connectors 

      Fixed

      Parse Failed Errors in Snowflake Connector

      Several SQL queries in the Snowflake connector failed to parse correctly. These errors impacted the successful extraction and processing of metadata from Snowflake. This issue has now been resolved by handling the syntax. All reported queries are parsing successfully, and metadata is being extracted as expected.

      'Has Lineage' Advanced Job Not Automatically Triggered After Lineage Build

      The "Has Lineage" advanced job was expected to run automatically after each lineage build to update lineage status. This functionality is partially implemented—it currently applies only to manual lineage builds. For auto lineage, the advanced job still needs to be run manually due to some technical complications. 

      Performance 

      Fixed

      Slow Query Impacting Database Performance

      A slow-running query was identified as the cause of a database performance issue. The query involved calculating null density by joining multiple metadata tables and was not performing efficiently. The issue has now been resolved, and the query executes as expected.

      Hotfix Release6.3.4.58

      This hotfix release includes bug fixes in the Connectors and Advanced Jobs modules.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.58

      		 Release6.3.4.58.6358caf9d9 4th Aug 2025

      Connectors

      Fixed

      Google BigQuery | Missing Definitions

      In the Google BigQuery connector, definitions failed to appear after a successful crawl. This happened due to a gap in handling schema metadata during crawling. The system now fetches and displays all definitions correctly.

      Power BI | Missing Report Pages

      In the Power BI connector, reports under the Project Review Center workspace showed incomplete pages and missing visuals. This occurred because the crawling process failed to capture multi-page report structures. The system now displays all report pages and visuals without issues.

      Advanced Jobs

      New & Improved

      Informatica | Automated Parameter File Extraction

      In the advanced job setup, the system now reads Informatica parameter files directly from a folder path and moves them to the target server. This setup ensures accurate data movement and reduces manual work.

      Hotfix Release6.3.4.59

      This hotfix release includes bug fixes in the Business Glossary, Data Classification, Data Quality Recommendation Center, and Jobs.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.59

      Release6.3.4.59.63459250ad29

      5th Aug 2025

      Business Glossary 

      Fixed

      Bulk Action Button Not Disabled

      In the Business Glossary, the Delete Terms button remained enabled even after unchecking the Select All checkbox. This occurred because the system failed to disable the bulk action button when no terms were selected. Attempting to delete without a selection caused an error. The system now correctly disables the Delete Terms button when no terms are selected.

      Data Classification

      Fixed

      Incorrect Replacement of Primary Term by Auxiliary Term

      In the Data Classification module, approving a recommendation using the 👍 icon incorrectly replaced the existing Primary Term with a recommended Auxiliary Term. This happened because the system failed to distinguish between term types during approval. As a result, Auxiliary Terms were allowed to overwrite Primary Terms without confirmation. The system now correctly preserves the Primary Term and only adds Auxiliary Terms. A confirmation pop-up is displayed when replacing a Primary Term with another Primary Term.

      Data Quality Recommendation Center 

      Fixed

      Data Quality Remediation Center Status Change Issue

      In the Data Quality Remediation Center, the Change Status option remained enabled even when no records were selected. This happened when users selected all items, navigated to a different page, and returned; the selection was lost, but the system still allowed status changes. The system now correctly disables the Change Status option when no items are selected in the UI.

      Jobs 

      Fixed

      Manage Button Enabled Without Selection

      In the Jobs module, the Manage Jobs button was incorrectly enabled after selecting a job on one page and navigating to the next, even when no job was selected on the new page. This occurred because the system did not clear the previous selection across pagination. The system now correctly disables the Manage Jobs button when no jobs are selected on the current page.

      Hotfix Release6.3.4.60

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

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.60

      Release6.3.460.63460227b891

      6th Aug 2025

      Data Catalog 

      Fixed

      Table Column Details Now Download Successfully
      In Data Catalog Table Columns, an issue occurred where downloading Table Column details from the Job Logs failed due to a backend query error. This issue has been resolved, and users can now successfully download the Table Column details.

      Data Quality

      Fixed

      DQ Summary Page No Longer Breaks on Cancel Action
      In Data Quality, an issue occurred within the Data Quality Summary when users entered the purpose and activated the rule without saving, which triggered a pop-up, and canceling this pop-up caused the page to break. This issue has now been resolved. The pop-up no longer appears unnecessarily, and the page functions correctly after cancellation.

      Connectors 

      Fixed

      Oracle Crawl Now Extracts Table Metadata Correctly
      In Oracle Connector, an issue occurred where the crawl process failed to retrieve the list of tables from the Oracle source database, despite the correct GRANT permissions on data dictionary views. The job completed without errors, but did not extract any table metadata. A warning in the job logs indicated that no tables were found. This issue has been fixed, and the crawl process now correctly retrieves table metadata.

      Informatica Connector Now Displays Source Filter Query
      In Informatica Connector, an issue occurred where the source filter query was not displayed in the Data Catalog summary during crawling and lineage building. This issue has been resolved, and the source filter query is now visible.

      Hotfix Release6.3.4.61

      This hotfix release includes bug fixes in the Data Catalog, Business Glossary, and Lineage modules.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.61

      		 Release6.3.4.61.63461ca091a9 7th Aug 2025

      Data Catalog

      Fixed

      Table Columns | Download Failure

      In the Table Columns section, downloads failed when column names followed a specific pattern with multiple words. The system now supports all column name formats, and the download feature works without interruption.

      Business Glossary

      Fixed

      Domains | Missing Meta-Write Access
      In the Domains section, a role with viewer permission was tagged in the authorized users and roles of a domain. A user who had this role was assigned as a steward but did not receive Meta-write privilege and was unable to update metadata. The issue has been resolved. Now, when a user is assigned as a steward, Meta-write privilege is provided on the domain, even if the role has viewer permission.

      Lineage

      Fixed

      Tableau | Missing Data Sources

      In a key dashboard, data sources were missing due to incorrect or broken connections in the source configuration. This issue has been resolved, and now the system connects to the intended sources, and the dashboard loads the data as expected.

      SAP BODS | SQL Not Detected

      In the lineage workflow, some SQL was missing due to code parsing issues with non-standard scripts. This affected lineage generation for workflows using data manipulation logic or unsupported SQL operations. The system now identifies these patterns and includes them in the lineage where possible. For workflows that cannot be parsed automatically, manual lineage will be created.

      Hotfix Release6.3.4.62

      This hotfix release includes bug fixes in the Data Catalog, Data Quality Rules, Schedule, and Data Classification modules.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.62

      Release6.3.4.62.63462d45baff

      8th Aug 2025

      Data Catalog

      Fixed

      Data Catalog Grid View Simple Download
      In Data Catalog Grid View, an issue occurred where selecting a specific column filter in Simple View and downloading the results incorrectly exported the entire catalog table. This issue has been resolved. The download now correctly includes only the data matching the selected column filter.

      Data Quality Rules

      New & Improved

      New Filter Column Shows Rule Scheduling Status
      The Data Quality Rules Grid View now includes a ‘Has Schedule’ filter column, enabling users to determine the scheduling status of each rule.

      • When the filter is set to “Yes”, only rules that have an automated schedule configured will be displayed.
      • When set to “No”, only rules without an automated schedule will be shown.

      Schedule

      Fixed

      Bulk Selection Limit in Schedule Module
      In the Schedule module, an issue occurred where selecting more than 350 Data Quality Rule schedules in bulk via the cron entry filter resulted in a 401 error. This issue has been resolved, and users can now bulk-select and schedule over 350 rules without any issues.

      Data Classification

      Fixed

      Auxiliary Term Approval Behavior Corrected
      In Data Classification, an issue where approving a recommendation by clicking the 👍 icon incorrectly replaced the existing Primary Term with the Auxiliary Term from the recommendation. This behavior has been corrected. Approving an Auxiliary Term recommendation no longer replaces the Primary Term defined in the glossary.

      Hotfix Release6.3.4.63

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

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.63

      Release6.3.4.63.634633de8f8f

      11th Aug 2025

      Data catalog

      Fixed

      Report Preview Tab Fails to Load for Tableau Reports

      In the Data Catalog, the report preview tab for Tableau reports failed to load and remained in a continuous loading state. This occurred because the Host Name in the connection details included the protocol (http://). This issue has now been resolved. The report preview tab now loads Tableau reports as expected.

      Lineage 

      Fixed

      Exclude Relationship Generation from Lineage Building

      The lineage building process experienced severe performance degradation when processing datasets exceeding 100,000 records due to the inclusion of relationship generation. This issue prevented successful lineage builds for large datasets. The process has now been optimized by excluding relationship generation for all relevant connectors.

      Advanced Job 

      Fixed

      Conversion of Object Description URLs

      During metadata migration through an advanced job MigrateDescriptionsFromAlation, object descriptions contained clickable links referencing other objects in the source system’s format. These URLs required conversion to the target system’s format to maintain references. A logic was implemented to parse and update the URLs during migration. This issue has now been resolved.

      Build Lineage from Extracted Queries 

      The advanced job Lineage.build.relationships experienced significant delays in execution. After completion, some codes still remained in an Unprocessed status. The job also showed a killing status while continuing to run in the backend without visible errors in the logs. This issue has now been resolved. The job now completes within the expected time and processes all codes successfully. The job now correctly converts all URLs to maintain valid references in the target system.

      Connectors 

      Fixed

      Dell Boomi | Lineage Build Errors for Certain Components

      In the Dell Boomi Connector, the lineage build has failed for certain components due to REST API calls in the lineage job. The issue was limited to specific tables and could not be tested earlier due to a lack of access to the client’s service account. The REST API calls have now been moved to the connector crawl job. This issue has now been resolved, and the lineage build completes successfully.

      BigQuery | Parse Failures During Lineage Build

      During the lineage build for the BigQuery connector, some SQL queries failed to parse while others processed successfully with associations. The failures occurred because certain keywords and functions are not currently supported in OvalEdge. This issue has now been resolved, and the lineage build completes successfully.

      Hotfix Release6.3.4.64

      This hotfix release includes bug fixes in the Governance Catalog and Connector modules.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.64

      		 Release6.3.4.64.634641c17667 13th Aug 2025

      Governance Catalog

      Fixed

      Data Classification Recommendations | Incorrect Term Replacement

      In the Data Classification Recommendations section, the primary term in the glossary is replaced with an auxiliary term after approving an AI recommendation using the thumbs-up icon. The system now keeps the existing primary term when an auxiliary term is recommended. This fix also ensures consistent term handling across related modules, including Business Glossary and Data Catalog.

      Connectors

      Fixed

      MicroStrategy Cloud Connector Now Connects Successfully

      In Connectors, an issue occurred where a NullPointerException error prevented the MicroStrategy Cloud Connector from validating and establishing a server connection. This issue has been resolved, and the connector now validates and connects successfully.

      Hotfix Release6.3.4.65

      This hotfix release includes bug fixes in the Data Quality Rules, Data Classification, Lineage, and Connectors.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.65

      Release6.3.4.65.634654c8f1fb

      14th Aug 2025

      Data Quality Rules

      Fixed

      Count Missing for Codes Objects in Data Catalog

      The Data Catalog page failed to show the Data Quality Rules count for Codes objects due to inconsistent display logic for existing and new data. Counts either appeared as 0 or stayed blank. This issue has been fixed, and the correct counts now display for all relevant Codes objects.

      "Oops Technical Error" When Creating Custom View with "Has Schedule" Column 

      In the Data Quality Rules (DQR) page, creating a custom view that included the "Has Schedule" column caused an "Oops technical error" and prevented the page from loading. This occurred due to incorrect handling of the column in custom views. This issue has now been resolved, and the DQR page loads as expected when creating views with the "Has Schedule" column.

      "Is Scheduled" Field Displays Incorrect

      In the Data Catalog, when users added a schedule to Data Quality Rules from the Rule Recommendations or Rule Summary pages, the "Is Scheduled" field for the Recommended Rules incorrectly displayed as "NO" after creating a view with that schedule. This occurred due to incorrect display logic for scheduled recommended rules. This issue has now been resolved, and the "Is Scheduled" field correctly reflects the schedule status.

      Automated Scheduling Missing for Some Data Quality Rules

      In the Data Catalog, some Data Quality Rules did not have automated scheduling enabled. This occurred due to gaps in job-level configurations across modules. This issue has now been resolved, and automated scheduling is now applied to all relevant Data Quality Rules.

      Data Quality Rules Not Displayed for Objects in Field-Level Query Parameters

      In the Data Catalog, Data Quality Rules were not displayed at the object level when the object was added to field-level query parameters, even though the rule count appeared at the catalog level. This issue has now been resolved. Data Quality Rules are correctly displayed for all relevant objects.

      Data Classification

      Fixed

      Unable to Identify Users Who Accepted or Rejected Recommendations in Data Classification Reports

      In the Governance App’s Data Classification module, users could not identify who accepted or rejected recommendations from reports. The only way to find this information was by manually checking each term individually. This issue has now been resolved. The system now displays the associated user directly in the Data Classification Reports screen, allowing quick identification of who accepted or rejected each recommendation.

      Lineage 

      Fixed

      Lineage Gaps for Dashboards Not Connecting to Sources

      In some cases, dashboards showed lineage gaps where source connections were missing. This happened due to issues like resident tables not linking to some files, and temporary objects being used as sources instead of the intended data warehouse. This issue has now been resolved. Lineage is now correctly established, and source connections display as expected.

      Connectors 

      Fixed

      Incorrect Source Selection in Power BI Lineage

      The lineage process in Power BI incorrectly identified temporary tables as the main source instead of the original tables. This caused inaccurate source mapping in the lineage view. The logic has now been corrected to ensure that the original tables are consistently identified as the main source.

      Salesforce Profiling Errors in SaaS Environment

      Profiling the Salesforce connector schema through Bridge in the SaaS environment failed due to invalid JSON parsing. When certain column properties (not aggregatable, filterable, or groupable) triggered a 400 error, the system expected a JSONObject but received a JSONArray. This handling gap occurred only with Bridge and caused profiling errors for affected columns. The issue has been fixed by updating Bridge logic to handle the JSONArray response and improving validation to display clear error messages.

      Hotfix Release6.3.4.66

      This hotfix release includes bug fixes in the Data Catalog, Business Glossary, Data Classification, Data Quality, Load Metadata from Files, and Connectors.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.66

      Release6.3.4.66.634660e0c60a

      18th Aug 2025

      Data Catalog

      Fixed

      Business Description Save Error Resolved in Data Catalog

      In Data Catalog (Files, File Columns, Reports, and Report Columns), an issue occurred where saving a business description after tagging a data object displayed the message "Oops, Technical error." This issue has been resolved, and business descriptions can now be saved successfully after tagging.

      Reports Sorting by Last Modified Date Now Accurate

      In Data Catalog Reports, an issue occurred where sorting by Last Modified Date was not functioning correctly. This issue has been fixed, and sorting now displays results in the correct order.

      Business Glossary

      Fixed

      Custom Field Filter Issue Resolved

      In Business Glossary List View, an issue occurred where filtering a Custom Field column excluded entries with "None" values, but the results still displayed those entries. This issue has been fixed, and the Custom Field column filter now functions correctly as expected.

      Data Classification

      New & Improved

      User Identification for Accepted Recommendations

      In Data Classification, users could not identify the user who accepted recommendations from the Recommendations page or the Data Catalog Reports Grid View. To check this status, users had to open each term manually. 

      Data Classification Reports objects Grid View now displays ‘Associate By’ (user list) and ‘Associated Method’ (E.g., AI Recommendation, Manual), with filtering options to identify who accepted or rejected recommendations.

      Data Quality 

      Fixed

      Accurate Row Counts in Custom SQL Data Quality Rules

      In Data Quality Rules, an issue occurred where a custom SQL Data Quality Rule returned incorrect values for passed, failed, and total row counts after execution. This issue has been resolved, and the rule now displays accurate counts.

      Function Filter Now Works Correctly

      In the Data Quality Rules Grid View, an issue occurred where the Function column filter displayed duplicate entries when both Null Data Density and Data Density were selected. Additionally, the selected functions could not be unchecked after applying the filters. This issue has been resolved, and the filter now works correctly without duplicates and allows selections to be removed.

      Load Metadata from Files

      Fixed

      Multiple Values Blocked When Single-Select Is Set

      In LMDF | Table Columns | Code Custom Fields, an issue occurred where multiple values could be uploaded through the template even when Multiple Select was set to 'No.' These values appeared on the Data Catalog summary page without restriction. This issue has been fixed. When Multiple Select is set to No, uploading multiple values is prevented, and an alert message appears.

      Connectors

      Fixed

      MicroStrategy Connector Now Crawls Successfully

      In Connectors, an issue occurred where the MicroStrategy Cloud Connector failed to crawl due to a system error. This issue has been resolved, and the connector now crawls successfully.

      Hotfix Release6.3.4.67

      This hotfix release includes bug fixes in the Governance Catalog, Data Catalog, Lineage, and Impact Analysis modules.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.67

      Release6.3.4.67.6346e907765

      20th Aug 2025

      Governance Catalog

      Fixed

      Duplicate Entries in Certification Metrics

      In the Governance Catalog, duplicate entries appeared for some certification reports, leading to inaccurate certification metrics. The issue occurred when multiple certification requests were triggered simultaneously. The system now handles concurrent actions correctly and maintains accurate certification data.

      Data Catalog

      Fixed

      Text Custom Field “Equals” Filter Option

      In Data Catalog, the “Equals” condition was missing for custom text fields in certain filter views, limiting exact match searches. This inconsistency between standard and custom filter menus has been resolved, enabling precise filtering for all custom fields.

      Endorsement Field Filter Conditions

      In Data Catalog, filter conditions for the endorsement field were not applied correctly, preventing accurate filtering. The system now applies all conditions in the filter interface, enabling precise filtering for all endorsement scenarios.

      Lineage

      Fixed

      MicroStrategy | Delta Lineage Job Includes Reports

      In MicroStrategy, reports with a failed lineage status were not included in the delta lineage job. These reports now appear in the advanced job process, allowing lineage to be built from the interface.

      Informatica | Query Parsing

      In Informatica mappings, specific queries could not be parsed, preventing lineage from being built. The parsing logic has been improved, ensuring all queries are processed correctly and lineage generation succeeds.

      Informatica PowerCenter | Connection Info Display

      In Informatica PowerCenter, connection information was missing at the mapping level when query parameters were present. The system now displays connection names correctly for all mappings.

      Impact Analysis

      Fixed

      Source Object System Schema Display

      In Impact Analysis, the Source Object System previously displayed connection information instead of the schema. The system now shows the correct schema while retaining connection details for accurate impact analysis.

      Hotfix Release6.3.4.68

      This hotfix release includes bug fixes in the Login, Data Catalog, ROPA, and Connectors modules.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.68

      Release6.3.4.68.634688eeb0fc

      21st Aug 2025

      Login

      New & Improved

      Session Expiry Enforced for Closed Tabs

      During session handling, all sessions remained active even when the browser tab was closed without logging out. When the application was reopened, users were redirected to the home page without entering credentials, which created a security risk.

      Session handling has been improved to enhance security. If a browser tab is closed without logging out, the session is now terminated, and users are required to log in again when reopening the application.

      Data Catalog

      Fixed

      File Column Data Now Displays Correctly

      In Data Catalog, an issue occurred where data in the File Column tab appeared corrupted after opening it in the newly created view. This issue has been resolved, and the File Column tab now displays data correctly.

      ROPA

      Fixed

      Associated Data Displays Correctly After Back Navigation

      In ROPA | Processing Activity | Associated Data | Databases, an issue occurred where clicking Quick View in the schema and then using the browser’s Back button caused the associated data to disappear, even after refreshing the page. This issue has been resolved, and the associated data now displays correctly after navigating back.

      Connectors

      Fixed

      Accurate Metadata Sync Date for Reports

      In Connectors, an issue occurred during report connector crawling where the Last Metadata Sync date field in the Data Catalog report summary was incorrectly updated for all reports, even when only one report had actual changes on the remote server. This issue has been resolved. The Last Metadata Sync date now updates only for reports with actual remote changes.

      PowerCenter Connector Builds Lineage as Expected

      In Connectors, an issue occurred where the Informatica PowerCenter connector failed to crawl successfully, and lineage for mappings was not built as expected due to errors in queries feeding into the parser. This issue has been resolved, and mappings with queries now parse correctly without errors.

      Hotfix Release6.3.4.69

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

      Release6.3.4.6963469eb18f33

      22nd Aug 2025

      Connectors 

      Fixed

      Catalog File Option Not Working in SharePoint File Explorer

      In the SharePoint connector, the "Catalog File" option in File Explorer was not working. When users selected a file to catalog, the screen kept loading continuously, and the file was not cataloged. This issue has now been resolved. Users can now catalog files from the SharePoint File Explorer and view the data.

      BigQuery Profiling Jobs Stopping Automatically

      In the BigQuery connector, profiling jobs stopped automatically after running for 24 hours. When users retried profiling with the Profile Unprofiled option, the jobs still took more than 24 hours and showed several errors and warnings. This happened because errors during large-scale profiling were not handled properly. This issue has been resolved. Profiling jobs now finish within the expected time, and all errors are clearly logged for easy troubleshooting.

      Snowflake | Nullable Property Displayed Incorrectly in Data Catalog

      The Data Catalog always showed the Nullable property as "No" for all connector columns. This happened because the mapping logic did not check the actual schema definition (NULL or NOT NULL). The issue has been fixed, and the Nullable property now correctly reflects the database schema.

      Hotfix Release6.3.4.70

      This hotfix release includes bug fixes in the Data Catalog, Governance Catalog, Lineage, and Connectors modules.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.70

      Release6.3.4.70.6347071de882

      25th Aug 2025

      Data Catalog

      Fixed

      Technical Description Update Error Message

      In Data Catalog, an error occurred while updating specific columns using the Table Column template. The system displayed an action failure message related to the “Technical Description” field, even though the field was configured as "No Action." The update process now completes successfully without errors.

      Data Quality Score Sorting

      In Data Catalog, while sorting the Data Quality Score in descending order from the Data Catalog > Columns tab, decimal values were not considered. The system now considers decimal values and sorts the scores accurately.

      Lineage

      Fixed

      Column Lineage Error After Page Load

      In the Lineage module on the Lineage > Column Lineage page, an error occurred when the page took longer to load. This error stopped the column-level lineage details from displaying. The system now loads the Column Lineage page without errors and displays all details correctly.

      New & Improved

      Expanded Test Coverage for Connectors

      The test framework has been updated to include new scenarios for recent changes in connector functionality. It now covers end-to-end workflows, error handling, and performance checks for RDBMS, ETL, and reporting connectors. These enhancements help maintain accurate results and consistent connector behavior.

      Governance Catalog

      Fixed

      Steward Display in Governed Data Query

      In the Governance Catalog > Governed Data Query page, when editing an existing Governed Data Query using the Edit option from the actions menu, the Steward field appeared empty, making it challenging to confirm ownership. The system now displays the correct Steward information during the edit process to ensure clarity and accuracy.

      Connectors

      Fixed

      DataStage Query Parsing

      In the IBM InfoSphere DataStage connector, specific queries failed to parse, which resulted in job errors and incomplete lineage. The parsing logic now handles these queries correctly, allowing all jobs to run without errors and lineage to build as expected.

      BigQuery Lineage Build Parse Failures

      In the BigQuery connector, some views with complex SQL structures failed during lineage build and displayed a "Parse Failed" status. The parser now supports BigQuery-specific SQL syntax and complex view structures, ensuring lineage builds without errors.

      Oracle Lineage Build Parse Failures

      In the Oracle connector, certain views failed to parse during lineage build and returned a "Parse Failed" status. The parsing logic now supports complex SQL structures in Oracle views, enabling complete lineage generation.

      Redshift Lineage Build Parse Failures

      In the Redshift connector, some views failed to parse during lineage build due to unsupported patterns such as NOTNULL and specific token usage. The normalization and parsing logic have been improved to handle these patterns, ensuring successful lineage generation.

      Hotfix Release6.3.4.71

      This hotfix release includes improvements & bug fixes in the Jobs and Connectors modules.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.71

      Release6.3.4.71.63471ccca048

      28th Aug 2025

      Jobs

      Fixed

      Jobs Start in Proper Order with Concurrency Limit
      In Jobs, an issue occurred when multiple jobs triggered simultaneously. If one job was running and another was in the INIT state, starting a new job caused the INIT job to transition to the RUNNING state, while the new job entered the INIT state. This created a repeating cycle where each new job waited in INIT until an existing job finished.

      The scheduling logic has been corrected. Jobs now start in the proper order based on the configured concurrency limit.

      Connectors

      New & Improved

      Enhanced Session and Mapping Metadata Display
      In Informatica Connector, the metadata at the session level did not display any override queries or source filters applied, which prevented users from seeing the full context of the data and potentially led to confusion or misinterpretation. 

      Now, the metadata visualization has been enhanced at both the session and mapping levels, providing a clear tabular representation of all collected information. Required queries are now displayed directly in the session and mapping summary, eliminating the need to navigate multiple levels in the OvalEdge application. 

      Metadata from the source is appended (subject to availability) with clear separation between session and mapping levels, while transformations are linked at the mapping level without modifications. 

      Crawl Captures SELECT Statements in Mapping Associations
      In Informatica Connector, certain SELECT statements in session tasks were not displayed in the mapping associations after the crawl. As a result, users were unable to view the complete lineage of data transformations. 

      Now, the crawling process has been enhanced to check the source code of session tasks. During lineage building, all relevant SELECT statements are now correctly captured and displayed in the mapping associations.

      Fixed

      Duplicate Objects Removed During Crawl
      In the ADF Connector, an issue occurred where duplicate ADF objects appeared when the connector was crawled. Duplicate Factories and Pipelines were created, especially after migration to the AKS environment. This issue has been resolved, and crawling now captures objects without duplication.

      Hotfix Release6.3.4.72

      This hotfix release includes bug fixes in the Lineage, Connectors, Advanced Jobs, and Security.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.72

      Release6.3.4.72.63472bcd7606

      1st Sep 2025

      Lineage 

      Fixed

      Errors While Building Lineage for Dell Boomi Components

      Lineage building for Dell Boomi components previously failed due to undeployed processes, XML parsing errors, and API timeouts. This issue has been resolved by implementing retry logic for 503 errors, enhancing XML parsing, and handling undeployed processes during the crawling process. Lineage for Dell Boomi components now builds successfully without errors.

      Performance Issue During Lineage Build for Tableau Reports

      Lineage building for Tableau report groups previously experienced severe performance degradation, taking 18–46 hours to complete. The issue was caused by inefficient processing of column-level lineage during extraction. The issue has been resolved by optimizing query execution and improving the lineage build logic. Lineage for Tableau reports now completes within expected timeframes.

      Amazon QuickSight Lineage Support

      Datasets in Amazon QuickSight built on Athena, PostgreSQL, and Redshift sources, including file-based and custom SQL datasets, previously lacked end-to-end lineage visibility. This issue has been resolved by enabling independent crawling of dashboards, datasets, and analyses to ensure all assets are captured. Lineage now extends to both file-based and custom SQL sources with initial support at the object level. Users can view the complete lineage from source systems into Amazon QuickSight.

      Build Lineage from Extracted Queries Fails on New Syntax Patterns

      The Build Lineage from Extracted Queries job failed to complete successfully due to exceptions triggered by newly introduced syntax patterns that the parser could not process. The job ended with a partial success status. The parser has been enhanced to handle these syntax patterns, ensuring the job now runs to full completion with accurate results.

      Reports Lineage Build Failure

      In the Data Catalog, lineage building for reports previously failed during execution when creating a connection and generating lineage. This issue has been resolved, and lineage for reports now builds successfully.

      Connectors

      Fixed

      Redshift | Parse Failed Codes

      In Redshift, several queries previously failed with parse errors because the parser did not handle cases with only CALL statements and procedures with nested associations. All failed queries were analyzed, and fixes were applied. The parser now processes these queries correctly.

      DataStage | Files Not Processed During Crawling

      In DataStage, files were not processed during the crawling operation, resulting in excluded metadata from the results. The issue occurred because the crawler did not recognize file types. The crawler now identifies and processes files, ensuring the metadata is included in the crawl results.

      Advanced Jobs 

      Fixed

      SQL Server | Advanced Job Failure

      The Mapping Between User Interface and Database Advanced Job failed to execute for SQL Server, even though all required custom fields were verified and the DBO schema was successfully crawled. Execution logs displayed errors during job processing. This issue has been resolved, and the Advanced Job now runs successfully for SQL Server without errors.

      Hotfix Release6.3.4.73

      This hotfix release includes bug fixes in the Data Catalog, Jobs, and Data Quality modules.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.73

      Release6.3.4.73.634739d59a66

      2nd Sept 2025

      Jobs

      Fixed

      Download Logs for Jobs with Large Output

      In the Jobs module, downloading logs for jobs with large output was not working. The download button became disabled and displayed a loading indicator for an extended period without completing the process. This issue has been resolved, and logs can now be downloaded successfully without delays.

      Data Quality

      New & Improved

      Data Quality Rule | Scheduling Column

      In the Data Quality module, there was no clear way to verify whether a rule had scheduling enabled, which resulted in additional effort during the review process. A new column has been added to display the scheduling status of each rule, making it easier to identify and manage scheduling configurations.

      Data Catalog

      Fixed

      Custom Field Filter Issue Resolved

      In the Data Catalog > Tables, filtering data using a custom field did not work as expected. When a filter was applied, no results were displayed even though matching values existed in the column. This issue has been resolved, and the filter now accurately returns results based on the selected custom field.

      Endorsement Search Feature Fixed

      In the Data Catalog module, searching for endorsements in reports and report columns was not functioning correctly. The search returned no results, even when matching data was available. This issue has been resolved, and the search now works as expected, providing accurate and complete results.

      Missing Conditions in Advanced Search

      In the Data Catalog module, the advanced search filter did not include options for exact match conditions, limiting the ability to perform precise searches. This issue has been addressed by adding Equal and Not Equal conditions, enabling accurate filtering based on specific values.

      Hotfix  Release6.3.4.74

      This hotfix release includes bug fixes in the Data Catalog, Jobs, and Data Quality modules.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.74

      Release6.3.4.746347406fe202

      3rd Sept 2025

      Data Catalog

      New & Improved

      Filter Option for Report Columns

      In the Data Catalog > Report Column tab, the Term column did not provide a filter option, which limited search and navigation efficiency. A filter option has now been added, enabling easier access and filtering for report columns.

      System Settings

      Fixed

      Audit Data Archival | Tables

      In the System Settings > Audit Data Archival screen, some tables were missing from the dropdown list, which made it difficult to configure the required retention rules. This issue has been resolved, and the required tables are now available for selection, allowing archival retention settings to be configured as expected.

      Lineage

      Fixed

      Parse Errors in DB2AS400

      In the Lineage module, certain views from the DB2AS400 connector were failing with a Parse Failed status during lineage building. This issue occurred due to a missing validation step in the connector’s crawl logic. The issue has been resolved, and lineage is now built successfully without errors.

      Qlik Sense Lineage Gaps

      In the Lineage module, dashboards in the Qlik Sense connector displayed gaps where some sources were not connected correctly. These gaps occurred in scenarios involving QVDs, resident tables, and temporary objects. The issue has been resolved, and lineage now accurately reflects all source connections.

      Informatica Auto Lineage Performance Issue

      In the Lineage module, the auto lineage process for Informatica was taking longer than expected to complete, even for smaller subsets of mappings. The issue has been resolved, and processing time has been optimized to ensure lineage runs complete efficiently.

      Connectors

      Fixed

      MicroStrategy Cloud Connector Crawl Issue

      In the Connectors module, the MicroStrategy Cloud Connector was failing to crawl in specific environments, preventing lineage and metadata extraction. This issue has been resolved, and the connector crawl now functions as expected.

      Error Message for BigQuery File Authentication

      In the BigQuery connector, an unclear error message was displayed when an invalid JSON file path was provided for authentication. The error message has been improved to be more user-friendly, clearly indicating that the JSON file path should be checked.

      Hotfix  Release6.3.4.75

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

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.75

      Release6.3.4.75.634754026b0e

      4th Sep 2025

      Data catalog

      Fixed

      Search with @ Annotation and Schema Selection Not Working

      The search functionality using the @ annotation with schema selection did not work. The Help Center showed that users could search with connectionname.schemaname, and the * operator, but no results were returned. This issue has been fixed. Searches with @ annotation, schema names, and the * operator now return results as expected.

      Missing Filter Option for “Term” Column in Report Columns Tab

      In the Data Catalog, the “Term” column in the Report Columns tab previously did not provide a filter option. This prevented users from filtering report columns based on associated business terms. The issue has been resolved, and the “Term” column now includes a functional filter option, allowing users to filter and refine results as expected.

      Lineage

      Fixed

      Lineage Gaps for SAP BO Universes Aliases

      Lineage building for SAP BO reports previously failed to connect aliases to their corresponding data warehouse tables. Aliases were treated as standalone objects, rather than being mapped to the actual tables. This resulted in incomplete lineage, where traceability stopped at the alias level. The issue has been resolved by correcting the logic to recognize and link Universe aliases with their corresponding warehouse tables. Lineage for SAP BO reports now connects aliases to the true sources, providing complete traceability.

      Lineage Build Failure for SAP BO Reports

      In SAP BO reports, lineage failed to build even though source queries were available. No error messages appeared, but lineage generation did not complete. The issue was caused by incorrect handling of schema and table names containing dots (.) and by intermittent null pointer exceptions. This issue has been resolved. Fixes were applied to ensure that schema-table parsing is handled correctly, and additional logging was added for improved debugging. Lineage now builds successfully without failure.

      Advanced Job for Temporary Lineage Correction in Bulk Merging

      Lineage correction for tables linked through temporary schemas previously required manual fixes. After rebuilding, tables from temporary schemas reappeared as temporary lineage even when matching tables existed in the target schema. An advanced job has now been introduced to handle bulk merging. The job automatically matches tables from temporary schemas with corresponding tables in the target schema when names align. If names do not match, those entries remain unchanged. This enhancement enables accurate and efficient correction of large-scale lineages.

      Hotfix  Release6.3.4.76

      This hotfix release includes bug fixes in the Data Catalog, Jobs, Data Classification Reports, and Lineage modules.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.76

      Release6.3.4.76.634765d766e0

      6th Sep 2025

      Data Catalog

      Fixed

      No Logout During Detailed Download File Access from Jobs
      In Data Catalog and Business Glossary, an issue occurred where, after the Detailed Download job completed successfully, clicking the file listed in the Jobs section caused an unexpected logout. This issue has been resolved. Accessing the file now works without logging out the session.

      Assigned Tags Visibility in File Columns Grid View
      In Data Catalog | File Columns, an issue occurred where tags assigned to File Column objects were not visible in the File Column Tags filter Grid View. This issue has been resolved. Assigned tags now display correctly in the filter view.

      Accurate Filtering for Empty and Non-Empty Date Fields
      In the Data Catalog | Tables Grid View, an issue occurred when applying the Empty or Non-Empty filters to Last Crawl Date, Last Modified Date, and Created Date, displaying the error message “Invalid Date.” This issue has been resolved. The filters now correctly display records based on whether the date fields are empty or non-empty.

      Date Range Filters Work Correctly in Tables Grid View
      In the Data Catalog | Tables Grid View, an issue occurred where applying the 'Within Range' or 'Not Within Range' filters displayed "Invalid Date," even when valid input was provided. This issue has been resolved. Filters now correctly display records that fall within or outside the specified date range, and valid input no longer triggers "Invalid Date" messages.

      Text Search Restored for Business Description in Report Columns
      In Data Catalog | Reports Column Grid View, an issue occurred where the Business Description field in the Report Columns tab displayed a filter option (such as “Equals” or “Is Empty”) instead of allowing direct text search. This issue has been resolved. The field now supports direct text search for business description values.

      Business/Technical Description Saves Without Extra Text

      In the Data Catalog Object Summary, there was an issue where saving an updated Business or Technical Description appended unwanted text. For example, entering a description like "Customer purchase data for Q3 analysis" would incorrectly save as "Customer purchase data for Q3 analysis powered by Froala Editor." This issue has been resolved now and only the user-entered text is saved and displayed.

      Jobs

      Fixed

      Large Job Logs Download Without Errors
      In Jobs, an issue occurred where downloading logs for jobs with large output failed due to memory exhaustion and timeout errors when processing large log files. This issue has been resolved, and large job logs can now be downloaded successfully.

      Data Classification Reports

      Fixed

      Business Description Empty Filter Behavior Corrected
      In Data Classification Reports under the Reports tab, an issue occurred where the empty filter in the Business Description field did not function correctly. Objects with no business description were incorrectly displayed as "No Data Exists." This issue has been fixed. Applying the empty filter now correctly displays objects that do not have a business description.

      Lineage

      Fixed

      Denodo Lineage Job Code Visibility Corrected
      In Advanced Tools | Build Auto Lineage, an issue occurred where the Denodo lineage job did not display the corresponding code in the Query Sheet, and the same code was missing from the lineage records. This issue has been resolved. The code now appears correctly in both the Query Sheet and the lineage records.

      Unity Catalog Column-Level Lineage Displays Accurately
      In Advanced Tools | Build Auto Lineage, an issue occurred where selecting the Unity Catalog connector caused column-level lineage to display incorrectly. This issue has been resolved. Column-level lineage now appears accurately.

      Hotfix Release6.3.4.77

      This hotfix release includes bug fixes in the Login, Data Catalog, Lineage, and Connectors modules.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.77

      Release6.3.4.77.634777379285

      10th Sep 2025

      Data Catalog

      Fixed

      Profiling Status Column Sorts Alphabetically
      In the Data Catalog | Tables Grid View, an issue occurred where the Profiling Status column did not sort in alphabetical order. This issue has been fixed, and the column now sorts correctly in alphabetical order.

      Enhanced Search in Object Summary Descriptions
      In Data Catalog | Object Summary Descriptions, an issue occurred where the search functionality did not work when using the @ annotation in combination with schema selection, “connection name.schema” format, or the * operator. This issue has been resolved, and the search now functions correctly with these options.

      Search and Sort Functions Work as Expected
      In the Data Catalog Objects Grid View, an issue occurred where the Search and Sort functions did not work as expected for specific fields. This issue has been resolved, and these functions now work correctly for all fields.

      No Expansion of Column Field on Sort
      In the Data Catalog | Report Column Grid View, an issue occurred where the "Column" field expanded unexpectedly when sorted by Popularity or Importance. While sorting worked correctly, the field size changed during the action. This issue has been fixed, and the "Column" field no longer expands when sorting by either Popularity or Importance.

      Lineage

      Fixed

      Lineage Details Show Query and Mappings
      In Quicksight Dashboard Lineage, an issue occurred where clicking the lineage details link displayed column mappings but did not show the associated query. This issue has been resolved, and the query now displays correctly, along with the column mappings.

      Duplicate Lineage Entries Eliminated
      In the Quicksight Dashboard | Lineage tab, an issue occurred where the lineage from the dashboard was displayed twice. This duplication issue has been fixed, and the lineage now appears only once for the correct sheet.

      S3 File Locations Restored for Lineage
      In Quicksight, an issue occurred where S3 parameters were available, but file locations appeared as 0 in Job Logs, preventing lineage from being built for the data source files. This issue has been fixed, and file locations now display correctly, enabling lineage to generate as expected.

      Connectors

      Fixed

      HashiCorp Vault Connector Now Validates Successfully
      In Connectors, an issue occurred where validation of the HashiCorp Vault connector failed with the error message “Exception occurred while connecting to the Bridge Server.” This issue has been resolved, and the connector now validates successfully.

      Hotfix Release6.3.4.78

      This hotfix release includes bug fixes in the Login & SSO, Data Catalog, Data Quality Rule, Advanced Job, Lineage, and Connectors. 

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.3.4.78

      		    

      Login & SSO

      Fixed

      SailPoint Integration | User Provisioning to OvalEdge

      A customer required an integration to authorize user provisioning actions from SailPoint to OvalEdge. The request included the ability to add, update, and remove users directly through SailPoint. The integration has been implemented and verified. It now supports user provisioning from SailPoint to OvalEdge as expected.

      Data catalog

      Fixed

      Sort and Search Not Working for Certain Fields

      In the Data Catalog list page, the Sort and Search functionalities did not work for specific fields.

      • Tables: Created Date
      • Table Columns: Profile Date, Last Crawl Date, Created Date, Last Modified Date
      • File Columns: Data Quality Score, Created Date, Last Modified Date
      • APIs: Created Date
      • API Attributes: Created Date, Last Modified Date

      The issue has been resolved. Sort and Search now work correctly for all affected fields.

      Data Quality Rule 

      Fixed

      "Last Run On" & "Duration" Columns Sorting Not Working

      The "Last Run On" and "Duration" columns did not sort correctly. Sorting showed as applied, but the data appeared unordered or displayed gaps between results. The issue has been fixed, and the columns now sort dates correctly in both ascending and descending order.

      Advanced Job 

      Fixed

      Alation URL Conversion Failed Due to Missing Double Quotes

      When running an Alation URL conversion advanced job, links failed to migrate correctly because double quotes were missing between the attributes in the HTML. The issue was resolved by correcting the link format, re-uploading the descriptions, and re-running the migration advanced job. URLs now convert successfully into the OvalEdge format.

      Lineage 

      Fixed

      Redshift Views | Lineage Parse Failed

      During lineage build for the Redshift connector, some complex views failed to parse and were marked with “Parse Failed” status. The issue occurred when views contained leading comments, non-standard NOTNULL usage, or the := operator. This resulted in invalid SQL during normalization, and lineage for those views was therefore skipped. The parsing logic has been updated to handle comments, normalize NOTNULL to IS NOT NULL, and process the := operator correctly. Lineage now builds successfully for all affected views.

      Lineage Not Built for Views

      In Denodo, lineage was not built for views because the raw view code was missing. This prevented the accurate generation of lineage and limited the traceability of view-level dependencies. This issue has been resolved. Lineage for views now builds correctly, and the raw view code is included as expected.

      Lineage Displayed as Manual After Automatic Build

      In Informatica, when lineage was automatically built for jobs using the Build Lineage option, the lineage was displayed as "Manual" after the build completed. This created confusion in identifying whether lineage was generated automatically or added manually. This issue has been resolved. The lineage built through the Build Lineage option now displays correctly as 'Automatic'.

      Connectors

      Fixed

      DBT Cloud Connector Crawl Failure

      While crawling the DBT Cloud connector, the job failed with the error “Dataset not found or Dataset access denied.” This occurred despite the service account having Admin-level permissions on all projects. As a result, metadata ingestion was not completed, and the datasets were not fetched into the catalog. This blocked data discovery, lineage, and catalog visibility. This issue has been resolved. Crawls now complete successfully, and datasets are fetched into the catalog without errors.

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