Knowledge Base

Architecture, Security & Releases

OvalEdge Releases

Release6.1.1.1

The latest OvalEdge Release6.1.1.1 brings substantial enhancements to various modules and licenses. Users can now efficiently manage data through improved Data Catalog features, enhanced Lineage visualization, a more user-friendly Business Glossary, and streamlined Service Desk operations. The system also offers advanced Data Quality Rule customization, updated Advanced Tools functionality, and numerous administrative enhancements for improved system performance and security. New connectors expand data source accessibility, while additional system settings provide users with additional control over application behavior. Furthermore, a set of new advanced jobs empowers users to perform diverse data management tasks with precision.

This release also resolves critical and significant bugs in various areas, ensuring a smoother experience.

Release Type

Release Version

Build

<Release. Build Number. Release Stamp>

Build Date

Hotfix Release

Release6.1.1.1

Release6.1.1.1.6111.06c9918

26 September 2023

Improvements

OvalEdge Licenses

The Contributor License type for users, introduced in Release6.1, is being discontinued. Existing Contributor License users will be upgraded to Author License users.

Global Search

When a term was created without adding a Business Description and later if that term was associated with multiple objects, searching with Business Descriptions did not display the associated search terms in the elastic search results. The improvement now ensures that the search terms related to Business Descriptions are accurately shown in the elastic search results.

Data Catalog

In the Data Catalog, a filter has been added to facilitate searching for null density, density percent values, masking, and restriction. By incorporating these filters, users will have the ability to easily identify data objects based on their null density, density percent values, and masking attributes.
In the Data Catalog, users were unable to apply the Domain filter to the system view while exploring datasets. This functionality has been enhanced, and now users can apply the domain filter to the system view.
In the Data Catalog, a download option was not available on the References Pages of all Data Objects. Users were unable to access the download option in the reference tab of the code section. This has been improved, and users can now download the references of the code from the Data Catalog.
In the Data Catalog, the "9 dots" menu included an option to apply certification to an object. The certification popup lacked a history icon. Now, the enhancement introduces a history icon in the certification popup. This addition allows users to track and view changes made to the certification status of objects over time, providing improved transparency and auditability.
In both the Data Catalog and Security, there was a lack of consistency in terminology when referring to databases and schemas. While it mentioned 'Database' in some contexts, it actually displayed 'Schemas' in those instances. This has been enhanced, and a 'Database' column has been added in table plugins.
In Data Catalog > Reports, users encountered a limitation where visual representation of SSRS and Power BI reports was not possible. The same issue was also present in the 'Dashboard > All Reports' section. This functionality has been enhanced and users can now access visual representations of these reports by selecting the 'open in SSRS' and 'open in Power BI' options available in the '9 dots' menu.
In the Data Catalog, users encountered session timeout issues when attempting to download table column data from the data catalog into a .CSV file. The session timeouts occurred while navigating to the table column tab in the data catalog and clicking on the Download button. To resolve this problem, changes have been implemented to optimize the download process. As a result, users can now download table column data from the data catalog into a .CSV file without experiencing session timeout issues.
In the Data Catalog > Reports, when users added downstream objects to reports, the importance score did not increase as expected. The functionality has been enhanced by changing the configuration (lineage.creation.increase.object.importance) in system settings to True. Now, when users add downstream objects to reports, the importance score is accurately calculated and increased. The improvement ensures that the importance score reflects the addition of downstream objects, providing better data management.
In the Data Catalog, the Reporting Framework pertains to the visibility of bar charts when there are fewer associated data objects, the chart is not visible. This has been improved, and now the bar charts are visible even when there are fewer data objects associated with them.
In the Data Catalog > Tables, when downloading table metadata from the summary tab, special characters did not appear in the downloaded file. The issue impacted the accuracy and completeness of the downloaded metadata file. This has been improved and users can now download table metadata from the summary tab in the Data Catalog's Tables section, and the downloaded file will include special characters as expected.
In the Data Catalog > Configure View, the display of "TRUE" values in the data classification column will be consistent for all object types, including Table Columns, when users create views after selecting a classification. After the improvement, users will be able to see the accurate "TRUE" values in the Classification Column for all object types, including Table Columns, when creating views after selecting a classification in the Data Catalog's Configuration View.
In the Data Catalog > Files, a new configuration has been added to enable users to hide the "Profile All Files" feature located under the 9 dots menu. With this configuration, users gain increased flexibility in managing access and visibility to the "Profile All Files" functionality within the Data Catalog. This enhancement allows users to customize their Data Catalog experience according to their specific needs and preferences.
In the Data Catalog > Objects > Summary > Tags, there was a need to display tag descriptions in the tooltip for child tags, along with their tag hierarchy. This functionality has been enhanced, and now the tag descriptions are displayed in the tooltip for Tags.

Lineage Enhancements

Here are the enhancements made to the Lineage feature in the Data Catalog,

Data Catalog - A new column named "Has Lineage" has been added to the List View, which displays a lineage icon for data objects that have lineage and remains blank for those without lineage. Users can filter lineage information by applying "Yes" or "No”.
Data Catalog > Codes, Introduced a graphical view of lineage alongside the existing tabular view for codes to display source and destination lineage information for specific codes. Also, introduced a new column named "Has Associations" to display whether a code has associations (Yes or No), allowing users to filter results accordingly.
Data Catalog > Lineage Tab

- Introduced a Tabular View for all data object types to list source and destination objects associated up to the first level.
- Made lineage information downloadable, with options to select upstream, downstream, or all lineage levels using radio buttons.
- Implemented a tabular view within the column mapping window for viewing. A download icon has been provided to download the source and target columns.
- Added a Certification Icon on data objects within the lineage, providing information about the certification status. Users can click on the Certification Icon to view the certification history in a pop-up window.
- Displays Data Quality (DQ) scores on data objects involved in the lineage. Users can click on the DQ score to access a detailed DQ dashboard.
- Enabled zoom-in, zoom-out, and full-screen options for improved navigation and interpretation of lineage diagrams.
Lineage Maintenance, Added a "Lineage Source" column that displays the lineage building type (e.g., auto, manual, API) for better understanding and tracking of lineage sources.

Business Glossary

In the Business Glossary, users now have the option to exclusively view 'PUBLISHED TERMS' when accessing a domain, with 'All Terms' being hidden. This functionality is managed via a toggle button, with the default setting set to 'yes.' When the toggle button is disabled, users will only have visibility of draft terms.
In the Business Glossary, users were unable to retrieve DATA and Pattern Scores when running AI Recommendations. The functionality has been enhanced, and now DATA and Pattern Scores are retrieved when running AI recommendations.
In the Business Glossary, the Category & Sub Category did not have any description fields; in the enhanced version, description fields have been added for both Category & Subcategory enabling users to provide detailed information and descriptions for the categorized business terms and concepts.
In Business Glossary > Tags, requiring manual tagging created the potential for errors. This functionality has been enhanced by running an advanced job "AssosciateTermTagsToObjects"; users can now assign tags to terms and their associated columns automatically.
In the Business Glossary, users now suggest a term within their preferred category. When submitting a service request, if a domain is selected, the associated steward for that domain will receive a request for service request approval. However, if a category is chosen, the associated steward at the category level will be sent a service request for approval.
In the Business Glossary, a request was made to implement color coding for terms during the creation process. This functionality has been enhanced, allowing users to assign specific colors to different terms in the Business Glossary, providing visual differentiation. To change the color of the domain, users need to go to the Security > Domains and edit the domain name, and select a color.
In the Business Glossary, users can now conveniently select governance roles in bulk under Terms. This feature is available within the Load Metadata from Files module, enabling streamlined management of governance roles while loading metadata from files and facilitating more efficient data management and governance processes.

Dashboard

In Dashboard > All Reports, the report group name was previously not visible when users hovered over reports, making it challenging to identify the group to which the report belonged. This enhancement now displays the report group name when users hover over any report.

Service Desk

The Service Desk Template Approval Workflow was enhanced to highlight duplicate entries in red. When users enter the mandatory details and add multiple teams and users as approvers, the system automatically highlights any duplicate entries in red, making it easier to identify and correct them promptly.
In the Service Desk, the Ticket Closing option was implemented, causing some templates to have it available while others did not. Users could see the close option for resolved tickets when accessing specific tables, but it was missing for schema access request tickets. The functionality has been improved, and the Ticket Closing option is now fully implemented in the Service Desk. Users can now see the close option for all tickets with Final Status, including both resolved tickets (indicate action taken to address an issue) and successfully fulfilled tickets (confirming both technical resolution and customer satisfaction).
In the Service Desk, all new term creation requests were automatically directed to domain owners/stewards, causing an overload of requests. This functionality has been enhanced, and users can now specify the "Category" and, if applicable, "Subcategory" of the term in the request form. This ensures that new term creation requests are correctly routed to the appropriate stewards/owners, reducing the overload of requests sent to domain owners/stewards.
In the Service Desk, the error messages have been revised to make them clearer and more accurate, preventing user confusion or misinterpretation.
In the Service Desk, the "Bring your own fulfillment" allows users to integrate their own fulfillment processes and systems with the Service Desk platform. This enhancement enables organizations to customize and streamline their fulfillment workflows, leveraging their existing tools and processes to manage service requests efficiently.
In the Service Desk, multiple tickets used to be generated for the same Data Quality rule when it failed multiple times, leading to ticket accumulation. This issue has been addressed by introducing a feature that allows bulk selection and management of "Violated Data Quality Rule" tickets. Users can now approve or reject all tickets related to one rule simultaneously, making ticket handling more efficient.

Data Quality

In the Data Quality > Data Quality Rules module, a modification was made with the main objective of enabling users to effectively utilize custom SQL rules by leveraging a pre-established stored procedure. This enhancement provides users with the capability to define and execute their specific SQL rules, making use of the functionalities offered by the system's existing stored procedure.
In the Data Quality > Data Quality Rules module, enhancements have been made to enable query execution support for the Athena connector, including the query sheet and GDQ (Governed Data Query) support that was not available before.
In the Data Quality > Data Quality Rules module, when a Data Quality Rule failed, it used to create multiple tickets upon re-running the same rule for the same issue. Users were required to approve or reject all these tickets associated with one rule at once. This functionality has been improved, and now only one ticket is raised for the same issue, streamlining the process.
In the Data Quality > Data Quality Rules module, previously when users removed additional associates, the Data Quality Score did not update. This issue has been resolved, and now the Data Quality Score correctly updates when users remove additional associates from association. The "Additional Associations Count" field has been implemented to display the count of associations with the Data Quality Rule. Moreover, the Service Request (SR) Score Donut chart now accurately represents the SR score by filling proportionally to the numeric value.
In the Data Quality > Data Quality Rules module, previously when a Custom SQL Rule failed and had Associated Objects with Additional Associations, Service Requests (SRs) were not being generated for each of these Additional Associations, instead generating a service request for the root Associate objects. This functionality has been enhanced, and now, each Additional Association object generates a service request.

My Resources

In My Resources > My Watchlist, in the context of Data Quality Rules (DQR), when users previously checked the 'Metadata changes' tab, terms were displayed for DQRs, even though the latest system version didn't utilize terms at the DQR level. This functionality has been enhanced, and users can no longer see terms in the metadata changes in Data Quality Rules, My Watchlist.
In the "My Resources" section of "My Permissions," we have added a flag or rating feature to both the table column and the file. Prior to this enhancement, users were unable to mark or rate specific table columns or files within the "My Resources" section. With the new improvement, users now have the ability to flag or rate individual table columns and files.
In My Resources > Inbox and Service Desk, previously the reminders only displayed time remaining in hourly and minute intervals, which caused limitations in understanding the remaining time precisely. This functionality has been improved, and users can now view the exact timestamp, showing the remaining time down to the seconds, for all tabs in inbox and Service Desk.
In My Resources > My Watchlist > Tables and Table Columns, there was previously no "Tags" column. This made it difficult to identify the tags and terms associated with items. This functionality has been enhanced by adding a "Tags" column, which provides users with a clear and organized view of the origin of each item.
In My Resources, integration of the Collaboration Messaging system with a teams/email/slack application has been implemented to facilitate seamless communication and collaboration between these different platforms. This integration enhances overall efficiency and promotes teamwork within the organization.

Query Sheet

In the Query Sheet, users did not previously receive error messages in the result pane when SQL queries failed. This required users to manually check logs for error details. This functionality has been enhanced, and users can now appropriately see error messages in the result pane.

Advanced Tools

In Advanced Tools > Impact Analysis, the "Source Objects" heading previously appeared as if it was clickable, causing confusion for users. It was positioned close to other interactive buttons. The functionality between the "Source Objects" heading and other interactive buttons has been enhanced, improving the user experience by reducing confusion and making it clearer that the "Source Objects" heading is not an interactive element.
In Advanced Tools > Load Metadata from Files, previously when users uploaded terms for the first time using the 'Load Metadata' feature, the Governance roles associated with these terms were not updated as expected. This functionality has been enhanced, allowing users to assign Governance roles to terms created for the first time.
In "Advanced Tools" > "Load Metadata From Files" of "Business Glossary," the downloaded template had inconsistent sheet names. They did not match the names used in the application, i.e., "Related objects" and "Associated Data." This functionality has been enhanced, and the downloaded template in "Advanced Tools" > "Load Metadata From Files" of "Business Glossary" now has consistent sheet names that match the names used in the application, i.e., "Related objects" and "Associated Data."
In Advanced Tools > Build Auto Lineage, when users previously validated a query on the "Correct Query" screen after building lineage, there was no loader symbol to indicate whether the validation was in progress. This issue has been resolved, and users can now see a loader symbol while validating a query.
In "Advanced Tools > OvalEdge API's > Business Glossary API," there is a requirement to modify an existing API by making certain fields invisible for Term Search. This enhancement aims to enable the retrieval of term details using a term ID.
In Advanced Tools > OvalEdge APIs> Business Glossary API > In ADD Terms endpoint, users were previously unable to perform update and delete operations. The new enhancement has been implemented in such a way that a new endpoint is developed as Add or Modify Term where users can perform both add and update operations. Also, the delete functionality was deleted from these endpoints.

Administration

In Administration > Connectors > ADF (Azure Data Factory), lineage flow is commonly established between data sources and destinations, like tables and files. It is equally crucial to construct lineage connections between activities, including their names, to fully comprehend the lineage flow. Previously, users were unable to search unstructured data files. This issue has been successfully addressed, empowering the team to scan and extract pertinent title information from unstructured data files. This enhancement significantly bolsters data search and analysis processes through the utilization of the CIFS (Common Interface File System) Protocol.
Within the Administration > Connectors framework, a recent addition has been made to the Connector page for Salesforce integration. This new feature introduces the option to set a KeyStore password and alias, thus enhancing the security of data transfers through Key Pair authentication.
The Administration > Connectors > Dell Boomi Connector has undergone several improvements to enhance its functionality and usability,
- Relationship enhancement between the process and sub-process.
- Building the lineage between the map component's source and destination
- Relationship enhancement between Boomi SQL and the process.

In Administration > Connectors > RDAM, the masking policy was not effectively restricting VIEW access after being disabled for objects or tables and their columns, compromising data security and privacy. The masking policy has been enhanced, to ensure that the masking policy is effectively restricting VIEW access and protecting data security and privacy.
In Administration > Connectors, The Looker reports previously involved missing lineage details for specific report types, Looker Dashboards using merged queries. This functionality has been enhanced, and the lineage reports are now correctly generated, which allows users to track the lineage of data in these reports.
In Administration > Connectors, Salesforce Row count permission, Users were encountering difficulties in accessing the Row count due to the mandatory high-level permission. This functionality has been enhanced, and now users can access the necessary data while adhering to the client's permission constraints.
In Administration > ADM Connectors > The auto lineage option previously remained enabled for connectors like MongoDB, Cassandra, and others that did not have any lineage information. This configuration potentially caused inaccuracies in data management and could have affected the user experience. The functionality has been enhanced; the auto lineage option will now be disabled for connectors like MongoDB, Cassandra, and others that do not have any lineage information.
In Administration > Connectors > NIFI Bridge, performance timing instrumentation was added to bridge crawling and profiling jobs. This feature captured and recorded the time taken for different stages of the processes, providing valuable insights into job efficiency and execution speed. The functionality in Configurations > NIFI Bridge is enhanced by adding performance timing instrumentation to bridge crawling and profiling jobs.
In Administration > Connectors > ADL Connector > Profiling, Azure Data Lake with Azure Key Vault integration, users previously encountered an issue where they couldn't view data under the Data tab after profiling a file. The functionality has been enhanced in the ADL Connector > Profiling, Azure Data Lake with Azure Key Vault integration. Users can now access the profiled data under the Data tab for analysis and insights.
In the Administration > Connectors > ADM Connectors, the process of validating the connection with Admin APIs for Power BI and Tableau ensured seamless integration between the Admin APIs and these third-party platforms. The validation process has been enhanced for further improvement in seamless integration.
In the Administration > Connectors > ADL Connector > Profiling > Azure Data Lake with Azure Key Vault, users previously encountered an issue where data was not visible under the Data tab after profiling any file. The Data tab was not displaying the profiled data, hindering users from analyzing and gaining insights from the profiled information. This functionality has been enhanced, and users can now access the profiled data under the Data tab for analysis and insights.
In Administration > Connectors > RDAM, the functionality of creating Roles, groups, and Users in the remote system was not working when OvalEdge was set as the master in the connection settings. The functionality has been enhanced, and now, when OvalEdge is set as the master in the connection settings, Roles, groups, and Users are correctly created and synchronized in the remote system.
In Administration > Connectors > "JSON Advance Job," an issue occurred where schema became inactive during the database recrawl as temp schema was not present in the remote system. The improvement involved making the temp schema always active during re-crawl, ensuring that codes remain functional and accurate.
In Administration > Connectors > Azure Data Factory (ADF), there was previously a challenge with transferring "Pipeline_Run_params" objects to OvalEdge in the production environment. This functionality has been addressed and users can now transfer data functions without any problems.
In Administration > Connectors > API, specifically, when making a GET request to the endpoint /api/user/getUserList to retrieve all users, there was an issue with the response status. Instead of receiving the expected response, the API returned a status of 404 error. The functionality has been enhanced, and the system successfully implements the offset and limit parameters for the API - GET /api/user/getUserList, ensuring that all users are retrieved and displayed correctly in the system.
In Administration > Connectors > ADM, User Preferences, there was an "Edit" pencil icon next to the user name field, but users could not change the username using this icon. This created confusion as users may think they can modify the username, which is not the case. This functionality has been enhanced, and the "Edit" option has been moved to the 9 dots menu, making it clear that the username cannot be changed from this field.
In Administration > Connectors > RDAM, the absence of a module for tracking user access to data objects posed challenges in managing data access control and raised concerns about potential security vulnerabilities. This functionality has been enhanced and designed specifically to track user interactions with data objects and generate detailed reports displaying user privileges.
In Administration > Connectors, we tuned the Tableau APIs and applied filters to reduce hits on the remote server. This optimization addressed the issue of the Tableau server receiving millions of hits from the Tableau account used in OE. As a result, the Tableau server's performance improved significantly, handling a large number of workbooks, data sources, and folders for the Life Solutions Tableau site.
In Administration > Connectors, a significant enhancement has been made through the implementation of Credential Manager. This addition strengthens the security of client credentials, ensuring a secure system for managing connector credentials.
In Administration > Connectors > S3, the OvalEdge application previously encountered limitations in supporting all data types within Parquet files, leading to difficulties parsing columns and displaying them in the OvalEdge application. This enhancement has been implemented and now, the application lists and skips unsupported data columns in the job log, while displaying the supported columns in the Data Catalog across the Summary tab, Data tab, and Column Details tab.
The Oracle Service Cloud Relationships | Previously, the connector contained table columns with additional sub-column data that was not being fetched into OvalEdge, leading to missing data and row count discrepancies. To address this issue, sub-columns have now been incorporated under the respective table columns, ensuring that the crawled data objects now align with an accurate row count. Also, the Entity Relationships are now shown between columns and their associated sub-columns. As a result, users can gain a more comprehensive understanding of the data structure, with relationships clearly depicted in the entity relationship view.
In Administration > Connectors, OvalEdge has significantly improved its lineage visibility from S3 to AWS Glue to Redshift. To achieve this, AWS Glue crawler integration is introduced, offering the ability to crawl various data sources, including those containing CSV, Parquet, and AVRO files.
Previously, in AWS Glue ETL, lineage building relied solely on crawling glue crawlers and storing them as datasets. The classifiers used in remote glue crawlers were added directly to the source code. We have enhanced the current functionality by storing the entire remote crawler object in the source code and when the crawler source is an S3 File, the lineage is built between the source S3 File and the glue table created.

It's important to note that several crucial steps must be executed before building a lineage,
- Crawling and Cataloging, Crawl the connection and catalog the files used by the crawler. This step ensures that all data sources are properly identified and prepared for lineage tracking.
- Profiling Files, To facilitate column lineage, profile the files and extract key information about their structure and content.
Once these preparatory actions are completed, the comprehensive lineage from S3 to AWS Glue to Redshift is built.

In Administration > Job Workflow > Schedule, an additional scheduling option for monthly job execution, particularly for the Job Workflow page is provided. This enhancement allows selecting specific days of the month, like the last day of every month .
In Administration > Security > Connectors, users previously encountered an issue where they could view the status (success, partial success, or killed) of connectors, but there was no filter option available to specifically view connectors with a desired status. The functionality has been enhanced by implementing the filter option for status. Users can now view the status of connectors and have the ability to filter and see connectors with their desired status.
In Administration > Security > RDAM system, the permissions tab previously exclusively displayed Role names, leaving out the associated Users' names. Our recent enhancement addresses this limitation by introducing a significant improvement. Now, within the permissions tab, you'll find a comprehensive view that includes both User and Role names. In the Administration > Audit Trials > Catalog, a new 'Descriptions' label has been introduced. Audit Trials now comprehensively record changes to Business and Technical descriptions at the object level, whether they are added manually or automatically through methods like 'Load Metadata,' API interactions, or Service Desk actions.
In Administration > Security, the "Edit Authorized Roles and Users" feature has been enhanced to provide greater clarity and accuracy during permissions editing. Users will now see both User and Role names, facilitating easier identification and association in the "Update Permissions" process. This enhancement leads to a more precise and informative representation of permissions within the OvalEdge platform.
In Administration > Advanced Jobs > Build Auto Lineage, the process of building lineage between SAP HANA and Redshift connectors has received significant enhancements. These improvements empower the system to effectively handle tables or columns with distinct names, particularly when the "/" character is present. During the lineage process, the system now automatically substitutes "/" with "_" to facilitate uninterrupted data tracing and comprehension between these two connectors. Users can now establish precise lineage connections even when names vary, ensuring efficient data management and comprehensive analysis capabilities.
In Administration > Advanced Jobs, functionality previously lacked the capability to replace the character '/' with '_' in table names while building lineage for tables that share the same name across different connections. This functionality has been enhanced, and users can now replace the character '/' with '_' in table names to enable seamless lineage building and distinction between tables with identical names.
In Administration > Advanced Jobs > Build Auto Lineage, there was a job assigned to extract queries for lineage construction. The presence of duplicate queries had caused a performance issue, leading to an extended job execution time. This issue has been resolved, and the job currently extracts unique queries for lineage construction, thereby reducing the execution time.
In Administration > Advanced Jobs > Extract queries from source to build lineage, the issue of duplicate queries previously caused performance problems and prolonged job execution times. This functionality has been enhanced and the job now ensures that only unique queries are extracted. In the subsequent advanced job, build lineage from extracted queries, these unique queries are utilized for lineage construction, resulting in reduced execution times.
In Administration > Advanced Jobs > Download Powerbi Pbix files > Enhanced Power BI advanced job to export reports using parameters first, and if unsuccessful, it retries with report IDs and group IDs.
In Administration > Advanced Jobs > Download Powerbi Pbix files, an improvement was implemented to enhance the capability to execute a job for multiple individual workspaces by specifying the domain names with comma separation or leaving it empty to run the job for all workspaces.
In Administration > Advanced Jobs, "Download Powerbi Pbix files'' task, an enhancement has been implemented to handle scenarios where exporting reports may require multiple iterations. An additional parameter has been introduced, which allows users to specify whether failed iterations should be rerun by providing "true" along with the number of iterations, or if they should be ignored by specifying "false."
In Administration > JSON Advance Job, users were previously getting duplicate views when executing a job. This occurs due to fetching views from both the Delta Lake and JSON. This error was resolved; the JSON Advance Job now prevents duplicate views.
In Administration > System Settings > SAAS environment addresses the issue of downloading templates, data, and ADL profiling, which previously required different temporary paths. Users had to manually change these paths every time they performed these actions. To improve this, two separate path configurations have been implemented in the bridge. One path configuration is designated for temporary path downloads, and the other is for ADL profiling of files in the SAAS environment.
In Administration > System Settings > Users & Roles, users could assign a single role to the ovaledge.tag.role configuration, but the system did not support adding multiple roles to the value. The current functionality has been enhanced and now users can add multiple roles to the ovaledge.tag.role configuration.
In Administration > System Settings > PK-FK relationships job feature > pkfk.relation.job.rowcount.check, the system now has the option to configure a matching row count check before building relationships. This allows users to validate the number of matching rows between the two columns before establishing connections, ensuring data quality and accuracy in the system.
In Administration > System Settings, SMTP validation has been improved by implementing OAuth for token generation. This enhancement eliminates the requirement for client ID and credentials.

Logs Backup

OvalEdge generates logs within the Tomcat environment to help diagnose issues when they occur. These logs are stored as "ovaledge.log" files in the "<Tomcat>\logs" folder, with each file limited to a maximum size of 10 MB. When a log file surpasses this size limit, it is automatically renamed to "ovaledge.log.1," and this process continues for up to 50 backup files.

In log4j.properties, the default configuration of the "log4j.appender.logfile.MaxBackupIndex" key value was set at 50. It has now been decreased to 25, and customers have the flexibility to adjust this number based on their specific hard disk size requirements in their environment. This modification effectively reduces the number of log files generated and stored by half, leading to a 50% reduction in the necessary log storage space for each pod.

New Connectors

CIFS
The CIFS (Common Internet File System) connector is a specialized file connector designed to streamline the process of crawling files and folders. This connector leverages SMBJ, a powerful library for accessing files and resources over the Server Message Block (SMB) protocol. OvalEdge uses SMBJ protocols to connect to the data source, which allows users to crawl and profile data objects (folders, files, files data, etc.). No lineage is present for CIFS.
Network Drive Scan
The Network Drive Scan is a file connector that shares similarities with the CIFS (Common Internet File System) connector. Like the CIFS connector, it utilizes SMBJ, a robust Java library, to effectively crawl files and folders.
GitHub File Connector

The GitHub File Connector is a specialized repository file connector designed for streamlined file access and management within GitHub repositories.
Unity Catalog

Databricks Unity Catalog is a leading solution for unified data and AI governance in lakehouse environments. It enables organizations to seamlessly manage data, models, notebooks, and more across cloud platforms. Users can securely access and collaborate on trusted assets, boosting productivity with AI. Unity Catalog offers centralized access control, auditing, lineage tracking, and data discovery for Azure Databricks workspaces. OvalEdge uses a JDBC server to connect and perform data crawling, profiling, query execution, and lineage building.
IBM Datastage

IBM Datastage is a powerful Extract, Transform, Load (ETL) connector. It excels in seamlessly connecting various components and executing complex data integration jobs.
Cognos 10.2

IBM Cognos Analytics is an On-Premises/Cloud connector that seamlessly integrates reporting, modeling, analysis, dashboards, storytelling, and event management capabilities to enable informed and impactful business decision-making through comprehensive data insights.

AWS Secrets Manager Redesign

The redesign of AWS Secrets Manager introduces a change in how secrets are structured and named. Now, secrets are generated by including both the connection name and the connection ID as part of their naming convention. This adjustment enhances the organization and management of secrets, providing a more structured and efficient approach to secret management within AWS Secrets Manager.

Oracle Service Cloud Redesign

The Oracle Service Cloud Connector has been redesigned to streamline metadata access, data crawling, and profiling through REST APIs. This update enables users to retrieve essential table information, create parent and sub tables, establish primary and foreign key relationships, manage data movement, and conduct data profiling.

New System Settings

The latest release introduces a set of new configurations that provide users with even greater control over the application's behavior. The newly added configurations are listed in the following Table.

System Setting Keys	Description
load.data.from.cache	This setting specifically pertains to the Azure Data Lake connector to control the visibility of file data and file columns when profiling is performed. Parameters, If set to "true", this option enables the display of file data and file columns. If set to "False" results in the exclusion of file data and file columns.
bridge.temppath	This configuration is used to specify the file system path where temporary or intermediate files related to the bridge functionality are stored. Parameters, Input the tempath in the field provided.
profile.all.files.enable	This configuration allows the user to enable or disable the "Catalog and Profile All Files" option in the Data Catalog > Folders, accessible through the nine dots icon. Parameters, If set to "true", the option gets displayed in the Data Catalog > Folders, under the nine dots menu. If set to "False", the option is disabled from the Data Catalog > Folders, under the nine dots menu.
bridge.server.host	This enables the configuration of the host or URL of the bridge server, allowing the system to establish connections and communication with the specified server. Parameters, Input the bridge server's URL into the provided field.
bridge.server.port	This configuration enables the user to specify the port number associated with the bridge server to communicate with the bridge server through the defined port. Parameters, Enter the bridge server's port number into the provided field.
pkfk.relation.job.rowcount.check	This configuration allows the user to specify the minimum row count that a table must meet to qualify as a primary key. When set to a value such as 100, primary key columns will only be identified for those rows that equal or exceed this threshold. Parameters, The default value for this criterion is set at 100. Enter the value in the field provided.
pkfk.relation.job.max.fk.count	This configuration specifies a limitation on the number of foreign keys that must be identified to calculate relationships. When set to a value such as 20, relationships will only be constructed if the count of identified foreign keys is equal to or less than 20. If, for example, 25 foreign keys are identified, relationships will not be established. Parameters, Enter the value in the field provided.
relationjob.min.match.count.from.topvalues	This setting defines the minimum number of matches needed between the top values of two columns to qualify for a potential relationship. For instance, if set to 10, at least 10 matches among the top values of the two columns are required to initiate a relationship. If this threshold is not met, the columns won't be considered for relationship building. Parameters, Enter the value in the field provided.
show.draft.terms.to.viewers	This setting enables a toggle button in the Business Glossary to toggle and display either Published/All Terms (Published and Draft) terms in the Tree View and List View of the Business Glossary. Parameters, The default value is set to 'true'. If set to "true", it allows viewers to switch the toggle between published and All terms (Published and Draft). In the list view, the term status filter can be used to filter out draft and published terms. If set to "false" it restricts viewers from seeing draft terms in both tree and list views.
allreports.pagination.limit	This configuration is used to specify the number of reports displayed on a single page within the Dashboard > All Reports. Parameters, Input your desired value into the designated field. For instance, if set to 20, only 20 reports will appear on a single page for improved navigation and readability.
tag.multiple.parent.hierarchy	This configuration setting provides users with the flexibility to create tags with the same name under different root tags. Parameters, If set to "true", Users can create tags with the same names under different root tags. If set to "false", It mandates unique tag names, disallowing the use of identical tags or duplicates.
servicedesk.request.bulk.approval.limit	This configuration is used to define the maximum number of tickets that can be approved in bulk using the "Approve/Reject" button located within the Service Desk's "Waiting Approval" tab. Parameters, Default Value, The default maximum limit is set at 50 tickets. Maximum Value, The maximum allowable limit is restricted to 100 tickets. Input Field, Users are expected to enter their preferred value within the designated field.
microstrategy.custom.fields	This configuration is used to activate or deactivate the custom fields 'Owner name' and 'Report created date' for the Microstrategy connector. When set to 'true,' they are enabled. The value can be either 'true' or 'false'. Parameters, If set to "true", it enables the custom fields 'Owner name' and 'Report created date' for the Microstrategy connector. If set to "false", the custom fields are deactivated.
entityrelationip.max.limit	This is used to configure the maximum limit for the number of nodes displayed in the entity relationship graphs within the Data Catalog. Maximum limit - 100. Parameters, The default setting is 50, which means that initially, up to 50 nodes are shown in these graphs. Enter the value in the field provided.
smtp.oauth2.tenantid	Enter Client ID for OAuth Token Validation and SMTP Server Authentication. Parameters, By default, this setting is empty. Enter a Client ID in the field provided to validate an OAuth token and set up SMTP Server Authentication.
smtp.oauth2.clientid	Enter Client ID for OAuth Token Validation and SMTP Server Authentication. Parameters, By default, this setting is empty. Enter a Client ID in the field provided to validate an OAuth token and set up SMTP Server Authentication.
smtp.oauth2.clientsecret	Enter Client Secret for OAuth Token Validation and SMTP Server Authentication. Parameters, By default, this setting is empty. Enter a Client Secret in the field provided to validate an OAuth token and set up SMTP Server Authentication.
smtp.oauth2.cloud.name	Enter Cloud Name for OAuth Token Validation and SMTP Server Authentication. Parameters, By default, this setting is empty. Enter a Cloud Name in the field provided to validate an OAuth token and set up SMTP Server Authentication.
oe.store.source.data	This configuration allows the user to determine whether the application should store source data or not. Parameters, The default setting is set to "true," which means the application will store the source data. If set to "false," the application will not store the source data. Additional Information, If you choose "false," please be aware of the following implications, AI Recommendations, Recommendations will be solely based on object names. Data Quality Control Center, Remediation tools will not be available. Data Quality Failed Values, You will not be able to view failed values. Governed Data Query, Results of the governed data query will not be visible. Query Sheet, Real-time data will be accessible but with some latency. It's important to note that selecting "false" will result in the removal of all stored source data from the system, and this data will be irrecoverable.

New Advanced Jobs

The latest release introduces a set of new advanced jobs that provide users with even greater control over the feature's behavior. The newly added advanced jobs are listed in the following Table.

Job Name	Description
DbtFileParseAndUpdatDescription	This job allows the user to copy and update the business description from the DBT connector (Manifest JSON file) to the matching data objects in the specified source connector. Additionally, this job creates new custom fields in the source connector based on the test custom fields provided in the DBT connector. Attributes, Source Connection Id DBT Connection Id
Build Lineage from Python JSON config Files	This job allows the user to build lineage on manually added JSON files which are connections, flows, and objects files in the Config folder. This is achieved by identifying matching source and target names within flows and objects, facilitating the lineage-building process. Attributes, RootFilePath Source ConnectionInfo id Destination ConnectionInfo id
ALERT FILE CHECK VALIDATION	This advanced job is developed for a client to validate their HDFS file system. It's intended to confirm whether the specified file is present in the designated folder for the specified time frame. Attributes, HDFS connection ID and the file path.
Update Schedule Next Execution Date Time	The purpose of this job is to update the next execution date & time in the database > "Schedule" table > "Next Execution date" column. This gets updated only when the "Next Execution date" field is empty or null. It is important to note that it is mandatory to run this advanced job for the first time when the database is new or updated. Attributes not needed.
PopulateCCFValuesinConfigureViewService	This advanced job enables the display of custom code fields within the Data Catalog's "Configure View" pop-up settings window. Attributes not needed.
Delete duplicate codes	The purpose of this job is to delete the duplicated drop-down options for code custom fields. The system does not permit the creation of duplicate drop-down options, executing this job effectively removes any existing duplicates. Attributes not needed.
Talend Java Variables	The purpose of this job is to build a lineage by taking the talend connection ID and query connection ID to replace the java global variables with actual values. Attributes, Talend connection id Query connection id
DQ Score calculation for 61	The primary objective of this job is to ensure that users migrating from the previous version to the 6.1.1 release can access the most up-to-date Data Quality (DQ) score. This is imperative due to recent adjustments made in the score calculation process. Attributes not needed.
Snowflake Tag Syncing Service	This job is created for a client (GreenSky) to synchronize tags between Snowflake and OvalEdge bidirectionally. If left blank, the initial synchronization will occur from Snowflake to OvalEdge, followed by the propagation of OvalEdge changes to Snowflake. Attributes, Connection Id (Attr 1) - Synchronization is limited to the metadata within this connection. Global Domain (Attr 2) - A global domain will be established using the provided name (e.g., GOVERNANCE). Category (Attr 3) - Specify the schema name (e.g., GOVERNANCE_DEV) from which the tags should be retrieved. Sync Type (Attr 4) - Indicate whether you want to synchronize Snowflake to OvalEdge (SF2OE) or vice versa (OE2SF).
Snowflake Tag Syncing Service V2	This job is created for a client (VSP) to synchronize tags between Snowflake and OvalEdge bidirectionally. If left blank, the initial synchronization will occur from Snowflake to OvalEdge, followed by the propagation of OvalEdge changes to Snowflake. Attributes, Connection Id (Attr 1) - Synchronization is limited to the metadata within this connection. Global Domain (Attr 2) - A global domain will be established using the provided name (e.g., GOVERNANCE). Category (Attr 3) - Specify the schema name (e.g., GOVERNANCE_DEV) from which the tags should be retrieved. Sync Type (Attr 4) - Indicate whether you want to synchronize Snowflake to OvalEdge (SF2OE) or vice versa (OE2SF).
Snowflake Delete tags Service	The purpose of this job is to delete all of the tags from Snowflake. Attributes, Attribute 1, List of Snowflake connection IDs separated by commas Attribute 2, List of Snowflake Schema IDs separated by commas
Update Tag Hierarchy	This advanced job is executed to generate distinct identifiers or IDs for identical tag names. The job ensures proper functioning of the system configuration setting > key name > tag.multiple.parent.hierarchy which grants users the capability to create tags with identical names under different root tags. No attributes are needed.
PROCESSRELATIONNAMETYPE	This job helps to process relation-type names in the glossary_relation table.
Term Masking Migration Job	Starting from Release6.1, OvalEdge has been upgraded to offer improved support for multi-masking schemes specifically at the Business Glossary Term level. This job migrates the existing masking scheme associated with the term to accommodate and support multiple masking functions. No Attributes are required for this job to run. Note, If you do not use the masking functionality, there's no need to execute this job.

Bugs Fixes

The following bugs have been fixed in this release, and the application is working as expected.

Global Search

In the Global Search with Left Panel Filter, users previously encountered an issue where attempting to select tags resulted in an undefined response for the drop-down options. This problem has been rectified, and now, users can successfully view and select tags from the drop-down list.

Data Catalog

In Data Catalog, the row count, which should have indicated the number of records in a file, was not displayed previously even when data was present in the data tab. The issue has been resolved. Users can now view the accurate row count after profiling.
In Data Catalog, an error was encountered previously when attempting to un-catalog files and folders using the "9 dots" menu. The issue has been resolved, and users can now un-catalog files and folders without encountering the error.
In Data Catalog, users previously observed an issue where certain tables displayed an "unknown column name" in their column details. The issue has been resolved, users no longer encounter the "unknown column name" problem when inspecting column details in the Data Catalog for tables.
In Data Catalog > Column details, users previously reported a problem where the column titles in the Data Catalog did not match those displayed in the Tableau Server dashboard. The issue has been resolved, and users now see consistent column titles in the Data Catalog, matching those displayed in the Tableau Server dashboard.
In Data Catalog, duplicate options for code custom fields in Table Column settings were previously caused by users creating global code custom fields at the Table Column level with specific options (e.g., 1, 2, 3). This issue resulted in duplicate entries not only in the Code Custom Fields section but also in the Data Catalog at the Table Column level. The issue has been resolved. Users should no longer encounter duplicate options for code custom fields in Table Column settings. The problem has been fixed both in the Code Custom Fields section and in the Data Catalog at the Table Column level.
In Data Catalog > Reports, users previously encountered an error when clicking on the text associated with an object. Specifically, when they navigated to the RFW (Reporting Framework) Reports, selected any report, and clicked on the object text, an error occurred. The issue has been resolved. Users can now click on the text associated with an object in the Reports section of the Data Catalog without encountering any errors.
In Data Catalog, the function to select a report, change its associated governance role, and modify a role (specifically, changing "steward" to "QA") was not working as expected. The issue has been resolved, and users can now successfully change governance roles for reports in the Data Catalog application, including updating the "steward" role to "QA," and these changes are being applied as expected.
In Data Catalog, previously, when users attempted to download data from the bottom of the Tables summary page, they encountered a problem. Specifically, the technical description information was not visible in the downloaded CSV file. The issue has been resolved, and users should now be able to download data from the bottom of the Tables summary page, and the technical description information should be visible in the downloaded CSV file.
In Data Catalog, previously when users modified the label within governance roles and configured a view, they subsequently used that view. When attempting to download data within the Data Catalog using the "Simple Download" option, the downloaded file did not include the labels as expected. The issue has been resolved, and users can now modify labels within governance roles, configure views, and successfully download data within the Data Catalog using the "Simple Download" option with the expected inclusion of labels.
In Reporting Framework, a specific challenge previously arose when dealing with custom-created reports and their associated bar charts. The problem is apparent when there is a limited number of associated data objects, resulting in the bar charts within these reports not being visible as expected. The issue has been resolved, and users should now be able to see the bar charts in custom-created reports, even when there are fewer associated data objects.
In Data Catalog, the "Open in new tab" link, which was supposed to allow users to open a code-related item in a new browser tab, was not functioning as expected. The issue has been resolved, and the "Open in new tab" link in the Data Catalog now functions as expected, allowing users to open code-related items in a new browser tab without any problems.
In Data Catalog, "Add to Impact Analysis" from the 9 dots menu was not clickable, after adding the Chrome plugin, when users went to the Data Catalog and attempted to add a table to an impact analysis that had been created, the option to do so was unresponsive or non-functional. The issue has been resolved, and users can now click on "Add to Impact Analysis" from the 9 dots menu, and the option to add tables to an impact analysis should be responsive and functional, even after adding the Chrome plugin.
In Data Catalog, duplicate API calls on the codes page resulted in two invocations of the same API when accessing the page. The issue has been resolved, meaning that the duplicate API call on the codes page has been addressed, and users no longer experience two invocations of the same API when accessing the page.
In Data Catalog> List view, the 4th governance role occasionally did not appear in the "Update Governance Roles" pop-up. The issue has been resolved, and users can now consistently see the 4th governance role in the "Update Governance Roles" pop-up.
In Data Catalog's Custom View, when users created a custom view, changed the display row count, and then accessed the view's configuration again, it defaulted to displaying the saved raw value of the last created user view, which was added during creation time. This occurred for all views, regardless of the specific row count users set for each view. The issue has been resolved, and users can now create custom views in the Data Catalog, change the display row count, and when they access the view's configuration again, it correctly displays the row count.
In Data Catalog's Custom View, previously, changing the display row count for a created view didn't persist when configuring the view again. Instead, it used to default to displaying the saved raw value of the last created user view, which was set during its initial creation, rather than maintaining the last configured page size. This issue has been resolved and users can see the last configured page size in the configure view.
In Data Catalog > Tables > Summary, when users previously updated a text custom field, it was saved as HTML code. Downloading the data containing this field retrieved HTML code instead of the intended text value. This problem was noticed when updating text custom fields for terms in the Business Glossary. The issue has been resolved, and users can now update and download the intended text value as expected.
In Data Catalog > Table > Summary, users previously could not access the associated ticket using the service request count feature, even after the ticket had been approved. The issue has been resolved and now users can access the associated tickets from the tables service request count feature without any errors.
In Data Catalog, objects were duplicated with identical IDs, which led to data catalog integrity problems. This issue has been resolved, with unique IDs assigned, and duplicate objects removed.
In Data Catalog > Codes, query pages were not loading or were experiencing significant delays, leading to timeouts and rendering the feature unusable. This issue has been resolved and users can now load the query pages in a timely manner.
In Data Catalog's Viewer module, two issues were identified, After users added objects to the access cart, the objects did not appear on the access cart page; and the access cart incorrectly displayed "Add Schemas" for all connector types, instead of displaying appropriate terms like "Add Tables" or "Add Folders" based on the connector type. Both issues have been resolved. Now, objects added to the access cart correctly appear on the access cart page. Additionally, the access cart displays appropriate terms like "Add Tables" for connectors like Snowflake, Redshift, and Databricks, and "Add Folders" for S3, based on the connector type.
In Data Catalog, a challenge was previously encountered where relationships could not be built for specific schemas in the attribute during the "Adv Job, Discover Primary and Foreign Key Recommendations Auto" process. Instead, relationships were being created for all schemas in the connection, leading to inaccuracies in data analysis and management tasks. The issue has been resolved. The process now correctly builds relationships only for the given schemas, ensuring accurate data analysis and management in the data catalog.
In Data Catalog, when data objects are added to the access cart, they were successfully added but did not previously show up on the access cart page. This issue has been resolved and the data objects are now showing up in the access cart.
In Data Catalog, the system was previously unable to build relationships for specific schemas in the attribute. This was due to incorrect labels, configuration, and validation handling. This issue has been resolved and the relationships are built for specific schemas in the attribute.
In Data Catalog > Databases, the advanced search operator "greater than" was not working correctly for the "Row count" column. This issue has been resolved, and users are now able to get accurate search results when they apply the "greater than" operator to the row count column.
In Data Catalog, an issue displayed assigned terms in the tags column for both reports and report columns. This issue has been resolved, with the tags column showing assigned terms only for reports.
In Data Catalog > Table, a profiling status column was previously missing. This issue has been resolved, and the users can now easily see the profiling status of tables in the Data Catalog.
In Data Catalog, the SAAS application was displaying duplicate schemas and tables. This duplication was visible in the data catalog, where multiple instances of the same objects were being displayed. The issue has been resolved, and the data catalog now displays a single instance of each schema and table.
In Data Catalog, blank and empty values were not supported, which prevented users from creating objects with these values. The issue has been resolved and users can now create objects with blank and empty values.
In Data Catalog, a request has been raised to introduce a new download option for business descriptions. This feature aims to provide users with the capability to download specific business descriptions selectively, rather than downloading all business descriptions at once. The load metadata download option in the data catalog allows users to update fields based on their requirements.
The Data Catalog, previously had an issue where the "Update Roles" popup would persistently display even after users moved to another module without closing the popup. This behavior caused disruption to the user's workflow and led to inconvenience. The issue is resolved in the Data Catalog. The "Update Roles" popup no longer persists across other modules. Now, when users open the popup to update roles and navigate to another module, the popup automatically closes.
In Data Catalog > Reports, users previously faced a 504 Error while trying to download data, particularly the list of documented columns. This issue has been resolved, and now, when a user clicks on the download plugin, it initiates a job. Once the job is completed, a clickable link is generated, allowing users to download the file to their local devices as expected.
In Data Catalog > Configure View, Codes, there was a performance problem associated with the filter icon when dealing with governance roles, which included Custodian, Steward, and Owner. The issue has been resolved, and there are no longer any performance problems when dealing with the filter icon for governance roles.
In Data Catalog, users encountered difficulties accessing the Reports page in the Data Catalog. The problem has been resolved, and users can now access the Reports page without encountering any errors.
In Data Catalog, When users applied a certification type to the same data object multiple times in the Data Catalog > Files, they would encounter an error message stating "data object has been designated as certified." This issue has now been addressed, and instead of an error message, a warning message is displayed with the same information, "data object has been designated as certified”.
In Data Catalog, the scrolling didn't function correctly on summary pages, negatively impacting the user experience. This problem has been resolved, and scrolling now works as intended on summary pages.

Business Glossary

In Business Glossary, the "String_Alphanumeric" scheme, designed to handle alphanumeric strings (combinations of letters and numbers), was not working as expected. The issue has been resolved, and now the "String_Alphanumeric" scheme in the Business Glossary is functioning as expected, effectively handling alphanumeric strings.
In Business Glossary, users were not receiving a popup message when adding tags to a term. The issue has been resolved and users now receive a popup message when adding tags to terms.
In Business Glossary, users previously had inconsistent permissions for publishing and drafting terms. They could perform these actions in the list view but encountered access issues when trying to do the same within individual term pages. The issue has been resolved, and users now have consistent permissions for publishing and drafting terms in both the list view and individual term pages.
In Business Glossary > List View, after creating a term, the fields "Approval by" and "Approval Date" were not populated correctly when users attempted to view the custom view of the term. This issue has been resolved, and users can now see the "Approval by" and "Approval Date" only after publishing the term.
In Business Glossary > List view > Terms, users were encountering an issue where duplicate terms were being added when attempting to establish related objects. The issue has been resolved and users can no longer add duplicate terms when establishing related objects.
In Business Glossary, while working with security table columns, there was a requirement for a new Boolean data type to facilitate content masking. The issue has been resolved, and users can now include the need for a Boolean Data type. This update is particularly important because it introduces a new masking scheme specifically designed for Boolean data types, where data masking is done based on masking schemes.
In Business Glossary > Summary page, clicking one checkbox in the "Manage Data Association" section erroneously checked all other checkboxes instead of masking them. A refresh was required to display the correct options. The issue has been resolved such that clicking one checkbox in the Business Glossary's Summary Page will no longer check all other checkboxes incorrectly.
In Business Glossary, "See More" was displayed for related objects even when there were no more objects to show. Additionally, the behavior of relating terms to objects was inconsistent, sometimes showing unexpected relationships when editing. These issues have been resolved, and in the Business Glossary, "See More" will no longer be displayed when there are no more related objects to show.
In Business Glossary, when users clicked on any term and related a report column to it, clicking on "report columns" resulted in an error. The issue has been resolved, and users can now click on related report columns as expected.
In Business Glossary, users encountered several issues with term relationships. The count of related terms was inaccurate, even when there were more than 30 related terms associated with a particular term. They were unable to access additional related terms beyond the initial set. The process of removing terms did not function as expected. The issue has been resolved, and users can now see the accurate counts of related terms, even when there are more than 30 related terms associated with a particular term. Users can also access additional related terms beyond the initial set, and the process of removing terms is working properly.
In Business Glossary > List View, when users added objects in the 'Associated Data' section for a term and then deleted objects from the second page, it displayed an empty page instead of returning to the first page. The issue has been resolved, and users can now see the associated data redirecting to the first page.
In Business Glossary, the Load meta from files previously did not allow managing Governance Roles in bulk. This issue has been resolved and users can now manage Governance Roles in bulk by specifically selecting checkboxes for Governance Roles under Terms.
In Business Glossary, some existing tags were not visible to users when attempting to apply them to terms, resulting in incorrect tagging. The issue has been resolved, ensuring that terms are now properly tagged and the tagging system functions as intended.
In Business Glossary, Admin users were initially unable to download Business Glossary templates. The issue has been resolved, and Admin users can now easily access and download the templates from the Business Glossary.
In Business Glossary, users were unable to update the Governance role for a term using the modify action when loading metadata from files using the data template. This issue has been resolved and users can now update the Governance role using the data template.
In Business Glossary, upon creating a term in the Configure View, all values were visible except for the Critical Configuration Field (CCF) values. This occurred because the CCF values were not being displayed in the Configure View. The issue has been resolved and the CCF values are now correctly displayed in the Configure View, ensuring comprehensive visibility of all relevant term information.
In Business Glossary, Previously, when a term with a masking policy was associated with data objects, the data remained visible despite applying a masking policy for the term. Now, this issue is resolved and the term masking is applied to the data object as expected.
In Business Glossary > Term Summary section, users encountered an issue when attempting to add a tag to a term. An error message, "Something went wrong," appeared, preventing users from successfully assigning tags to the selected terms. This issue has been resolved. Users can now effortlessly assign tags to selected terms without encountering any issues.

Projects

In Projects > List View, when users added 20 objects to the project, it worked as expected. However, when users attempted to add an additional 20 objects to the same project, it was not possible to add them. The issue has been resolved, and users can now add objects as required to the projects.
In "Projects,", after selecting an object and viewing its details, the tab did not close automatically, requiring users to refresh the page manually to close the tab. The issue has been resolved. Now, in "Projects," when users select an object and view its details, the tab closes automatically as expected, improving data management and navigation efficiency.
In Projects, the project count was not updating accurately after object deletions. This issue has been resolved and the project count is shown accurately even after the object deletion.

Dashboards

In Dashboards, the count of "All Reports" displayed didn't match the count in the data catalog under Reports. The issue has been resolved, and now the count of "All Reports" displayed in Dashboards matches the count in the data catalog under "Reports.
In Dashboards, users attempting to open "Dashboard > All Reports", previously encountered a "Problem Occurred" error message. This issue has been resolved, and users can now seamlessly view all the reports without any disruptions.

Service Desk

In Service Desk, all new term creation requests were previously automatically directed to domain owners/stewards, causing an overload of requests. The issue has been resolved, and users can now specify the "Category" and, if applicable, "Subcategory" of the term in the request form. This ensures that new term creation requests are correctly routed to the appropriate stewards/owners, reducing the overload of requests sent to domain owners/stewards.
In Service Desk, the custom service request templates and their approval process were the focus of improvement. Particularly, when a custom service request template had an expiration date set, it was not prevented from being approved once it had crossed that expiration time. Custom service requests with expired templates could still be approved. The issue has been resolved and now, when a custom service request template has an expiration date set, it is correctly prevented from being approved once it has crossed that expiration time, ensuring proper functionality and compliance with the intended process.
In Service Desk, notifications for service requests were not consistently displaying the correct label for the requestor previously. Instead of consistently showing the requestor's identity, these notifications sometimes displayed various users' names or even the admin's name. The problem also affected system alerts. The issue has been resolved. Users now consistently see the correct label for the requestor in notifications for service requests in the Service Desk. The problem affecting system alerts has also been addressed.
In ServiceDesk > SLA, even after an SLA had expired, the system previously continued to send notifications to the SLA user regarding the associated ticket. Furthermore, after a ticket had expired in the Service Desk, the "Approve" and "Reject" options were expected to be disabled, but they remained active despite the ticket's expiration. The issue has been resolved and indicates users should no longer receive notifications for expired SLAs, and the "Approve" and "Reject" options should now be correctly disabled after a ticket's expiration in the Service Desk.
In Service Desk system, users encountered a situation where, after clicking on a service desk ticket, they were presented with a blank page instead of the expected ticket details or information. The issue has been resolved, and users no longer encounter a blank page when clicking on a service desk ticket. Users can now access the ticket details and information as expected.
In Service Desk, there was an issue with the system failing to send email notifications when a service request was rejected. The issue has been resolved, and users can now receive email notifications when a service request is rejected in the Service Desk.
In Service Desk, SLA (Service Level Agreement) reminders previously occurred when a service request (SR) had two approvers, and the first approver rejected the request. Members of the team assigned as the second approver continuously received alerts to approve the request, even though it had already been rejected by the first approver. The issue has been resolved, and users will no longer experience SLA reminders for service requests with two approvers when the first approver rejects the request. The problem of continuous alerts to the second approver after rejection by the first approver has been fixed.
In Service Desk, users previously received excessive email notifications, both before and after ticket expiration, despite SLA settings. Approved service requests also caused email overload. The issue has been resolved, and users no longer receive multiple email notifications simultaneously. SLA notifications are sent according to the configured 1-hour interval, and approved service requests do not generate excessive email notifications, ensuring a more streamlined email experience.
In Service Desk, when users previously created a service ticket with a low priority, the corresponding status in Jira consistently displayed as medium, irrespective of the ticket's actual priority level. This inconsistency in status reporting between the two systems affected the accuracy of priority tracking and caused confusion. The issue has been resolved, and users no longer encounter the problem of the Jira status erroneously displaying as medium. The status reporting between the two systems now accurately reflects the priority level, improving tracking and clarity.
In Service Desk, there was previously an issue where changes made by an approver to a ticket were not saved if the ticket was rejected. This caused data loss as the changes would be lost once the page was refreshed. The issue has been resolved now. Changes made by an approver in a ticket are now saved even if the ticket is rejected. After editing the ticket and rejecting it, the changes will be retained when the approver returns to the ticket.
In Service Desk, tables generated were automatically deleted upon crawling the specific schema. This issue has been resolved, and now the tables created via the service desk remain intact even after the crawling process.
In Service Desk, when raising a "Suggest a Term" service request, there was previously an issue where the 'Category' field in the user interface did not update when assigning the category-level steward to the service request. This issue has been resolved and the specified category is displayed for the term suggested.

Data Quality

In the Data Quality > DQR (Data Quality Rules) module, users previously could not view the associations in the Association tab, even after executing the code, uploading the file, and having a successful job run. The issue has been resolved, and now users can see the related associations in the associations tab in DQR.
In the Data Quality > DQR, DQ Execution Details were missing for old rules, while they were available for new rules. The issue has been resolved, and users can now see the DQ Execution Details for both old and new rules, ensuring consistent access to this information.
In the Data Quality Scores Dashboard, the search functionality was not working as expected when users tried to search for specific columns. The issue has been resolved, and the search functionality within Data Quality Scores now works as expected, allowing users to effectively search for and locate specific columns within the dataset.
In the Data Catalog, there were concerns about missing business descriptions for tables in the new production environment. These descriptions were previously present but had disappeared. The issue has been resolved. The missing business descriptions for the tables in the new production environment have been restored, and the descriptions are now visible.
In Data Quality (DQ) Rules, the user previously faced an issue with the import file, as the schedule was incorrect. The user's intention was to schedule the DQ Rule to run on a specific day and time. After importing the file, the schedule only displayed the time without specifying the day of the week. Consequently, the rule did not execute as intended on the desired day. The issue has been resolved, and now users can import the file and accurately specify the day of the week for scheduling the DQ Rule.
When creating and running a Data Quality rule in the OE Application, adding contacts previously resulted in the generation of three alerts for both successful and failed rule executions. This redundancy in alerts needed rectification. This issue has been resolved and the alerting system has been streamlined.
In Data Quality > Data Quality Rules, users encountered an issue where adding Data Quality Contacts for email notifications triggered multiple alerts for each rule, regardless of its outcome (success or failure). This led to redundant alerts that were overwhelming and confusing for users. The issue has been resolved, and now users receive only email notifications indicating the rule's status (Passed or Failed).
In Data Quality > DQR, there was an issue where users couldn't view the scheduled action. The issue has been resolved, and users can now view and access the scheduled action in the DQR (Data Quality Rule) module. They can click on the schedule toggle button to see the schedule available in the schedule module with the respective DQR name.

My Resources

In My Resources > My Profile, users previously encountered an error while attempting to update their phone numbers. The issue has been resolved, and now users can save their phone numbers without encountering any errors.
In My Resources > My Watchlist, email notifications for metadata changes were not functioning as expected. Although inbox notifications within the application were working, email notifications were not being sent when metadata changes occurred, causing inconvenience to users who rely on email alerts for updates. The issue has been resolved, and users can now receive email notifications for metadata changes.
In My Resources > My Watchlist, the count for table columns was missing, and there was an alignment issue with tables. The issue has been resolved, and the object count for table columns displays correctly when hovering over them, and the alignment with tables is working as expected.
In My Resources > Application's text boxes, there was an issue where the "Decrease Indent" and "Increase Indent" functionalities were switched, resulting in the icons being paired with the wrong words. The issue has been resolved. Now, in the application's text boxes, the "Decrease Indent" and "Increase Indent" functionalities are correctly aligned, and the icons are paired with the appropriate words.

File Manager

In File Manager, when attempting to open the File Manager, users previously encountered an internal server error. The issue has been resolved, and users can now open the File Manager without encountering an internal server error.
In File Manager, when users accessed and clicked on the ADL (Azure Data Lake) Connector, and then proceeded to click on 'View Data' or 'Download Files' from the 9 dots menu option, they previously encountered an error. The issue has been resolved and users can now view the data and download files for the ADL Connector as required.
In File Manager, when users attempted to open the File Manager previously, they encountered 500 errors. This problem has been successfully resolved, and users can now access and view the File Manager page without any issues.

Query Sheet

In Query Sheet, the ‘join’ operation was not functioning as expected. Although there was common data present in both of the tables involved in the join, the results were not being displayed as they should have been. The issue has been resolved; users can now perform join operations in the Query Sheet, and the results are displayed correctly even when there is common data present in both of the tables involved in the join.
In Query Sheet, when users previously selected a connector and then chose a schema, the selected connector's name should have been displayed when hovered over. It continued to display 'Select Connector' instead. The issue has been resolved, and users can now see the selected connector name when they hover over the connector's name.
In Query Sheet, while querying a table in Azure Synapse, users were previously encountering an error. The error resulted in the query operation failing and not yielding the desired results. The issue has been resolved and users can now see the desired results.
In Query Sheet, users faced an issue where, even after selecting the connector, schema, and table, they were unable to execute queries. Instead, they received an error message stating, "Getting error in query execution, Please check the query or job logs." This problem has now been rectified, and users can successfully execute their queries without encountering any errors.
In Query Sheet, for the selected connector and schema, the "Auto SQL" mode was previously switching unexpectedly to "Advanced" mode and preventing users from selecting tables that have been resolved. Now, users can successfully stay in "Auto SQL" mode and are able to select tables without any issues.

Jobs

In Jobs, there was an issue where, during the crawling of a connector, the job logs had null errors and displayed the job status as "Partial Success". This issue has been addressed and now the job logs are working as intended and displaying the appropriate status.
In Jobs, there was an issue where the job log displayed zero datasets, even when the connector contained data objects. This issue has been resolved, and now the job log correctly displays all datasets as expected.

Advanced Tools

In Advanced Tools > Impact Analysis, the previous process involved running an Impact Analysis (IA) on a large set of source objects, which resulted in a substantial number of impacted objects (over 10,000). When users attempted to view these impacted objects, a blank page was displayed, and they encountered a 504 error. Additionally, when Impact Analysis was run again on the same set of objects the next day, a 502 error occurred, leading to a system crash. The issue has been resolved, and users can now successfully view the impacted objects without encountering the 504 error, and running Impact Analysis on the same set of objects no longer leads to a 502 error or system crash.
In Advanced Tools > Impact Analysis, duplicate queries were identified previously after running an impact analysis for a Looker report column. The responsible code for these queries was identical, and the only variation was in the date field within the queries. The issue has been resolved and when running an impact analysis for a Looker report column, no duplicate queries are generated.
In Advanced Tools > Impact Analysis, users previously encountered an error with HTTP status 500 - Internal Server Error when using the Impact Analysis feature. This issue prevented them from performing the desired Impact Analysis and understanding the potential impact of changes in the system. The issue has been resolved, and the users no longer encounter the HTTP status 500 - Internal Server Error when using the Impact Analysis feature in Advanced Tools.
In Advanced Tools > Build Auto Lineage, the Redshift system was failing to build lineage for stored procedures, resulting in a "parse failed" error. This error indicates that there are syntax or structural issues within the stored procedures, which are causing inaccurate data flow representation. This issue has been resolved helping users better understand the flow of their data and improve data management and analysis capabilities.
In Advanced Tools > Build Auto Lineage, Power BI was experiencing an issue with incomplete lineage for reports in the reports group. It failed to capture all data sources and dependencies on one of the model reports. The issue has been resolved, and users can now rely on accurate data tracing and have a better understanding of data dependencies in the reports
In Advanced Tools > Build Auto Lineage, users faced challenges while attempting to build the Redshift lineage. Certain SQL conditions caused complications, resulting in an inability to trace the origin and flow of data within Redshift. The issue has been successfully resolved with the implementation of fixes from the OvalEdge Lab. Users can now effectively trace the origin and flow of data within the Redshift data platform.
In Advanced Tools > Build Auto Lineage, users faced an issue while attempting to build lineage for Power BI reports. They encountered a "string out of index" error message, indicating a problem with string manipulation or indexing within the lineage-building process. The issue has been resolved. The necessary adjustments have been made to the string manipulation and indexing processes. Now, users can successfully build lineage for Power BI reports without encountering the "string out of index" error.
In Advanced Tools > Build Auto Lineage > Teradata lineage, there was an issue with the "Replace" functionality during query validation without spaces in the query correction process. This problem was impacting the crawl of Teradata and the process of building lineage for all the source codes. The issue has been resolved. The "Replace" functionality now works as expected during query validation and correction, even for queries without spaces. The crawl of Teradata and the lineage-building process now function smoothly without any problems, and the status filter accurately reflects the validation results.
In Advanced Tools > Build Auto Lineage > Azure Synapse lineage, some source code procedures were previously unable to parse correctly, resulting in the failure to build lineage for those codes. This issue was causing difficulties for users in building lineage for codes. The issue has now been resolved. All source code procedures parse correctly, enabling users to build lineage successfully for all codes.
In Advanced Tools > Build Auto Lineage, some reports faced challenges building lineage due to variations in the format of the data source caption and ID, leading to incomplete lineage information. To address this, logic has been added to handle the variations in the data source caption and ID formats, enabling accurate lineage building for all reports, including those previously affected.
In Advanced Tools > Build Auto Lineage > Azure Synapse, previously, building lineage for source codes sometimes encountered challenges in parsing the query. This impacted the ability to build lineage for these specific code segments in Azure Synapse. The issue has been resolved, and users can now successfully build lineage for these specific code segments without any issues.
In Advanced Tools > Build Auto Lineage, previously, the lineage could not be built for specific source codes because procedures could not be parsed or analyzed successfully during the process. This issue has been resolved and the lineage can be built successfully.
In Advanced Tools > Build Auto Lineage, there was a previous inability to access the complete source code and missing data source information in the source code lineage. The issue is resolved, and users can now access the complete source code.
In Advanced Tools > Build Auto Lineage, Power BI tables were not included in the lineage construction process, even though validation, crawling, and user-provided source connection names were implemented. This issue has been resolved, and users can now successfully create lineage and retrieve tables from the specified source connection names during crawling without encountering any errors.
In Advanced Tools > Load Metadata from Files, users previously encountered an error message in the job logs after attempting to create a role with specific permissions. In the user interface (UI), the role was seemingly created with default permissions. The issue has been resolved, and users can now create roles with specific permissions in the LMDF within the Advanced Tools without encountering error messages in the job logs.
In Advanced Tools > Load Metadata from Files, users were previously unable to upload Data Quality Rules (DQRs) that included Data Templates. Users were unable to upload values like business descriptions, tags, and custom field data (text, code, number, date) along with the DQR in the job logs. The issue has been resolved, and users can now upload Data Quality Rules (DQRs) with Data Templates without any errors in the job logs.
In Advanced Tools > Load Metadata From Files, users previously faced an issue where they couldn't upload Term Names and Custom field values from the "Load Metadata from Files" feature, even after creating a domain with 32 characters and adding terms to it. The upload process would fail when using the downloaded Business Glossary template, causing difficulties in data management. The issue has been resolved, and users can now successfully upload Term Names and Custom field values from the "Load Metadata from Files" feature in Advance Tools.
In Advance Tools > Load Metadata From Files > Schema Template, previously users encountered a situation where custom fields were not updating through the template when associated with data. Users expected the ability to add and modify custom fields through the Schema Template and have them reflected in the UI, but this was not happening. This issue has been resolved, users can now successfully add and modify custom fields through the Schema Template, and these changes will be reflected in the UI when associated with data.
In Advanced Tools > Load Metadata from Files, previously users could not map lineage information to table columns when using the uploaded lineage template, causing functionality issues. The issue has been resolved, and users can now map lineage information to table columns by uploading the lineage template.
In Advanced Tools > Load Metadata from Files, previously when users attempted to download the Users template with a data file, they encountered a 'Problem Occurred' error. The issue has been resolved and users can now download the Users template with a data file.
In 'Advanced Tools' > 'Load Metadata from Files,', previously when users clicked twice on a selected object's radio button, it deactivated the 'Next' button. The issue has been resolved, and users can now select objects twice, and the 'Next' button remains enabled.
In Advanced Tools > Load Metadata from Files, users previously encountered an issue while attempting to update table terms using the downloaded template data for tables. This problem caused difficulties in managing table-related terms effectively. The issue has been resolved, and users can now update table terms seamlessly using the downloaded template data for tables in the Load Metadata from Files.
In Advanced Tools > Load Metadata from Files > Data Quality Rules (DQR), there was a previous issue where users attempting to download the template for DQR with data found that the custom fields were not arranged in series. The issue has been resolved. Users can now download the template for DQR with data from the "Load Meta Data from files" feature in Advance Tools, and the custom fields are arranged in series.
In Advanced Tools > Load Metadata from Files, when using the "Load Metadata" functionality to update the Business Glossary template with existing data, neither custom fields nor business descriptions could not be modified previously. This issue has been resolved; custom fields and business and detailed descriptions can now be modified using the "load metadata from files" functionality.
In Advanced Tools > Load Metadata from Files, the DQR with Data Template feature was previously disabled by default. This prevented users from loading metadata from files. The issue has been resolved by re-enabling the feature.
In Advanced Tools > Load Metadata from Files, users couldn't previously enable a data download button under the DQR tab due to comma restrictions in tag creation and editing. The issue has been resolved and users can now enable the data download button under the DQR tab while still maintaining the flexibility to create and modify tags with commas.
In Advanced Tools > Load Metadata from Files, hyperlinks added to the business description with data were not previously displayed as clickable links when the template was reuploaded. Instead, they appeared as plain text. This issue has been resolved, and the hyperlinks are now clickable.
In Advanced Tools > Load Metadata from Files > Table Columns, users were previously required to provide inputs in the 'Action' column when uploading a template. When users uploaded a template without filling in the required 'Action' column, job logs did not issue a warning message. The issue has been resolved, and users now receive a warning message when they fail to update the 'Action' column in the uploaded template.
In Advanced Tools > Load Metadata from Files, changes have been made in the arrangement of columns in the "Load Metadata from Files" section. Specifically, the Code Custom field columns have been reordered to appear after the Text Custom fields. Additionally, an issue with custom fields created within the application, where the 'Non-editable' checkbox was selected but values entered in the template were still updating in the UI, has been resolved. Now, values entered in the template do not update in the UI when the 'Non-editable' checkbox is enabled (as expected).
In Advanced Tools > Load Metadata from Files, users previously encountered an error when downloading a table column template with data. The issue is now resolved and users are able to download the Table column template.
In Advanced Tools > Load Metadata From Files, users previously encountered a problem when loading metadata which had governance role names containing special characters like single quotation marks or others. When these names were updated in the template, they were not displaying the full names correctly, causing problems. Now, the system fully supports special characters in governance role names, ensuring an accurate and complete display of role names in templates.
In Advanced Tools > Load Metadata from Files, users previously encountered an issue where the table's business description was getting deleted when uploading table column definitions using the "Load metadata from file". This issue has been resolved, and now it's working as intended without deleting the table’s business description.
In Advanced Tools > Load Metadata From Files, when uploading the Table Columns (TC) template, including terms and masks for table columns, there was an issue where the changes made were not reflected in the UI. This issue has been addressed and the terms and applied masking on the TC for table columns are properly reflected in TC rewrite as expected.
In Advanced Tools > Load Metadata from Files > Business Glossary, users previously encountered an issue where modifications made to the "Template with Data," including Custom Fields, Business or Detail Descriptions, were not reflected in the application when the template was uploaded. This issue has been solved now and modifications made to the "Template with Data" are accurately reflected in the application upon uploading.
In Advanced Tools > Deep Analysis, users previously experienced a problem where the system retrieved older tables despite recent profiling. Users found that when they ran the Deep Analysis job to gain insights into data tables, it failed to reflect the most recent changes and updates in the tables. The issue has been resolved, and now the "Deep Analysis" job effectively fetches the most up-to-date data from the tables during profiling, ensuring accurate analysis results.
In Advanced Tools > OvalEdge APIs, previously, field naming conventions caused confusion between term retrieval. This issue has been resolved by standardizing field naming conventions across all APIs.
In Advanced Tools > OvalEdge APIs > Data Quality Rule API, the "Last run time" was displayed in nanoseconds, leading to a mismatch with the user interface (UI). This issue has been resolved by modifying it to a valid time format.
In the Advanced Tools > OvalEdge APIs> Business Glossary API, DQ Rule associations previously appeared in the API response despite the latest version intended to exclude them. This issue has been resolved by removing the Data Quality Rules from the API response, ensuring the Business Glossary associations are correctly displayed in the API response.
API Fixes - Several refinements have been implemented in the OvalEdge APIs, encompassing changes in field names, field removals, and updates to descriptions.

Administration

In Administration > Connectors, the Teradata database does not provide a built-in way to get the data types for the columns in a table. This impacted the performance and accuracy of data analysis queries. The issue has been resolved, and now users can retrieve data types for the columns in a table in the tera data database.
In Administration > Connectors, the Dell Boomi connector interface had a problem where the "settings" option was inaccessible when clicking on the 9 dots symbol. The issue is now resolved, and the "settings" option is accessible in the Dell Boomi connector.
In Administration > Connectors > RDAM, the previous attempt to update the password for the Redshift RDAM in OE (OvalEdge) for the Connector user failed. As a result, users were unable to access the Redshift database. The issue has been resolved, and users can now successfully access the Redshift database.
In Administration > Connectors > RDAM, the masking policy was not reflected in the source after enabling it for columns. Data remained unmasked, impacting data privacy and security. This issue has been resolved, and users can now ensure that the masking policy is properly reflected in the source, which helps to protect data privacy and security.
In Administration > Connectors > RDAM, previously actions were not logged in audit trails when revoking permissions remotely, causing a gap in auditing. The issue is resolved, and audit trails now capture permission revocations accurately.
In Administration > Connectors > RDAM, users previously encountered difficulties mapping a user to a group when OvalEdge was configured as the Master. This prevented users from being assigned to groups, affecting user permissions and access control. The issue with Redshift RDAM has been resolved, and now users can be successfully mapped to their respective groups even when OvalEdge is configured as the Master.
In Administration > Connectors > RDAM, users previously encountered an issue where they were unable to revoke a user assigned to a schema when the remote system (OvalEdge) was configured as the master. This prevented users from being removed from schemas, potentially impacting user permissions and data security. The issue has been successfully resolved. Users can now revoke users from a schema even when the remote system (OvalEdge) is configured as the master, ensuring proper access control and security measures.
In Administration > Connectors > In Profiling, users previously encountered missing column summary information (distinct counts, null counts, top values) after performing a clone operation. The discrepancies raised uncertainty about whether it was a bug or related to crawling, profiling, or sampling processes. The issue has been resolved. Now, after the clone operation, the column summary includes accurate distinct counts, null counts, and top values, providing users with the necessary information for data analysis and understanding.
In the Administration > Connectors > Redshift connector, users encountered an issue with RDAM that prevented them from viewing the remote privileges of a user in the User List of the Governance Catalog Module, particularly in the "Remote Access" section. This limitation restricted users from effectively managing and monitoring user access to the database. The issue has been successfully resolved, and users can now view the remote privileges of a user in the User List of the Governance Catalog Module, specifically in the "Remote Access" section.
In Administration > Connectors, users faced an issue where they couldn't delete a Group from the connector's Roles Tab in Redshift RDAM. Despite clicking the delete option, an icon pop-up appeared, but the deletion didn't happen, and the icon remained visible. This problem has been addressed, and now users can easily delete a Group from the connector's Roles Tab without any complications.
In Administration > Connectors, users encountered a problem where they couldn't view reports in the Build Lineage page while trying to build lineage for the Tableau Connector. The issue has been resolved, users can now view the required reports and successfully build data lineage, enabling them to effectively track and understand the data flow.
In Administration > Connectors, a problem arose from the team's decision not to use big data jars due to security concerns. This decision caused issues with data access and viewing. The problem has now been effectively resolved by implementing duckdb. As a result, users can access and view the data without encountering any errors.
In Administration > Connectors, users encountered an issue where they could validate the Delta Lake connector with incorrect credentials successfully, even though the validation process should have resulted in failure when incorrect information was provided. This raised security concerns and highlighted the need to improve the validation process to prevent unauthorized access. The issue has been resolved. The validation process now correctly detects and handles incorrect information, ensuring that unauthorized access is prevented, and users can securely validate the Delta Lake connector with accurate credentials.
In Administration > Connectors, users previously encountered an issue where lineage information was not populating for certain segment tables in the attached source codes, and the mquery (Power Query) was not visible in the reference tab for these tables. This limitation hindered data flow tracing and understanding the data source and transformations within OvalEdge. The issue has been resolved. Lineage information is now correctly populating for all segment tables, and the mquery (Power Query) is visible in the reference tab
In Administration > ADM Connectors, the Power BI (PBI) report previously encountered an issue where duplicate queries were being generated, leading to incorrect data representation. This issue had adverse effects on data accuracy and report performance. The issue has been resolved. As a result, the Power BI (PBI) report will no longer generate duplicate queries, and the data displayed in the report is now accurate.
In Administration > ADM Connectors, users previously faced an issue where they were unable to view remarks or comments when updates were made to a user's profile or permissions. This lack of visibility hindered their ability to access additional context or details about the modifications made. The issue has now been resolved. Users can now see the remarks or comments associated with any updates made to a user's profile or permissions, providing them with a more comprehensive understanding of the changes made.
In Administration > Connectors > RDAM, specifically in the User Management section, there was an issue where users could add conflicting privileges "nocreatedb" and "Createdb" simultaneously. This posed a potential security risk as it allowed a user to have the ability to both create databases and prevent other users from creating databases. The problem has been resolved. Now, when users attempt to add conflicting privileges, the system displays an appropriate error message, preventing the addition of conflicting privileges and ensuring proper access control and data security.
In Administration > Connectors > ADM Connectors, users faced an issue where they couldn't view the remarks or comments associated with updates made to a user's profile or permissions. The issue has been resolved. Users can now access and view the remarks or comments for any updates made to a user's profile or permissions, enabling better tracking and understanding of account modifications.
In Administration > Connectors > DB2 ODBC connector, users faced an issue related to sample profiling. When attempting to perform sample profiling, the system failed to generate the expected profile results, hindering users from obtaining the necessary data insights and statistics. The issue has been resolved, and users can now perform sample profiling successfully, obtaining the expected profile results without any complications.
In Administration > Connectors > Redshift connector, users faced an issue with RDAM that prevented them from viewing the remote privileges of a user in the User List of the Governance Catalog Module, particularly in the "Remote Access" section. This limitation posed challenges in effectively managing and monitoring user access to the database. The issue has been successfully resolved. Users can now view the remote privileges of a user in the User List of the Governance Catalog Module, specifically in the "Remote Access" section, ensuring smoother access control and data security.
In Administration > Connectors > RDAM, there was an issue where permissions granted by a user to others were not automatically revoked when the user was deleted. This resulted in other users retaining access to the data even though the granting user was no longer present. The issue has been resolved. Now, users can successfully revoke permissions for schemas and tables even after deleting the associated user.
In Administration > Connectors, previously, SFTP connector's File Manager encountered problems when used with the Bridge and cataloging. Users faced issues with null profile files, data unavailability in the data tab, and errors while downloading files from the 9 dots menu option. The issue has been resolved; the SFTP connector's File Manager now functions properly with the Bridge and cataloging. Users can access the profile file without any null values, view data in the data tab, and download files from the 9 dots menu option without encountering any errors.
In Administration > Connectors, previously, when users attempted to search for the third page using the toolbar, they encountered a problem where the search results did not display the correct message or information. The issue has been resolved, and users should no longer encounter the problem of incorrect messages or information when searching for the third page in the toolbar within the Connectors section.
In Administration > Connectors > Snowflake, users previously encountered errors when attempting to profile the schema of the database. These errors were reported in the context of job status, which was marked as "partial success." The issue has been resolved, and users no longer encounter errors when profiling the schema of the database in the Connectors > Snowflake section. The job status now indicates a successful outcome without "partial success" markings.
In Administration > Connectors > Talend, previously the connector was unable to retrieve files from the Azure Report. When attempting to crawl the Talend connector, users encountered a 404 error. This error is confirmed by checking the Tomcat log. Consequently, the connector cannot successfully fetch files from the Azure Repository. The issue has been resolved and users can now fetch files successfully from the Azure repository.
In Administration > Connectors > SQL Connector, profiling was not working as expected, even when the sample profile size was set to 90000. Users were unable to obtain results based on this profile size, and there was a question regarding the editability of the sample profile, which should have allowed users to input their own values. The issue has been resolved, and profiling in the SQL Connector now functions as expected when the sample profile size is set to 90000. Users should be able to obtain results based on this profile size, and the sample profile should accept user-provided values as intended.
In Administration > Connector > Azure Data Factory (ADF), there was a challenge with transferring "Pipeline_Run_params" objects to OvalEdge in the production environment. This functionality has been addressed and users can now transfer data functions without any problems.
In Administration> Connectors > ADM Connectors, previously when users logged into the OvalEdge Application and navigated to the Connectors section to crawl the Power BI connector, they encountered a problem with the generation of report columns. Specifically, for some reports, the report columns were not being generated as expected after crawling the Power BI connector. The issue has been resolved, and users should now be able to log in to the OvalEdge Application, navigate to the connectors section, and successfully crawl the Power BI connector with the report columns being generated correctly as expected.
In Administration > Connectors > ADM Connectors, while connecting to the database using Azure Key Vault during migration, users previously encountered a challenge in reading the JDBC URL. The issue has been resolved by making it a non-mandatory requirement.
In Administration > Connectors > ADM Connectors, slow job execution was observed when crawling data from a SAP HANA connection. The issue has been resolved, and users no longer experience delays in their data extraction or synchronization tasks, resulting in improved performance.
In Administration > Connectors, users were unable to create data lineage, which is the visualization of data flow and relationships, due to differences between the caption (a descriptive label) and the ID (a unique identifier) of the data source within a Workbook. The issue has been resolved; users can now create data lineage successfully even when there are differences between the caption and the ID of the data source within a Workbook.
In Administration > Connectors > ADM Connectors > MongoDB, previously, certain schemas were failing to be crawled due to extended crawling times required to retrieve the complete data. The issue has been resolved, and users can now crawl MongoDB schemas without encountering extended crawling times or failures.
In Administration > Connectors > ADM Connectors, within the Workday connector, some columns were reported as missing or were not appearing as expected. The issue has since been resolved, and the missing columns in the Workday connector within ADM Connectors have been restored or addressed, ensuring that all columns appear as expected.
In Administration > Connectors, users were previously unable to access and manage bridge configurations in the Connectors module's "Manage Bridge" feature for "ovaledge.connector.creator." They encountered a "No Data Exists" message and an "Access Denied" error, even for the "OE_ADMIN" user. Adding the "author" role in System Settings did not resolve the problem, highlighting a role-based access issue. Only "OE_Admin" could access data when their role was in the configuration. The issue has since been resolved, and users can now access and manage bridge configurations in the Connectors module's "Manage Bridge" feature for "ovaledge.connector.creator" without encountering the "No Data Exists" message or "Access Denied" error.
In Administration > Connectors, previously, when users tried to profile tables, an issue occurred. The problem stems from the profiling process exceeding the preset maximum value, resulting in an error. The issue has been resolved and users can now profile tables as required.
In Administration > Connectors, users encountered an issue when attempting to validate a connector with a bridge, resulting in an error message, signifying that the validation had failed. When attempting validation without using the bridge, it was successful. The issue has been resolved and users can now validate the connector with or without using the bridge option.
In Administration > Connectors > Build lineage, when users attempted to export source code to file in build auto lineage, It was not generated at the temporary location as expected. Clicking the download link resulted in a blank page. The issue has been resolved and users can now download the source code in the temp location as well as via the local path.
In Administration > Connectors > XML Connector, there was a metadata import issue (VSP) where imported XML columns were incorrectly set to 'string' with a length of '0'. This resulted in incomplete table column metadata. The issue has been resolved, and Table column metadata is complete and accurately reflects the data types and column lengths
In Administration > Connectors > Snowflake connectors, the crawling process previously encountered a problem with schemas. The UI job logs displayed a warning message, and the crawling process omitted Stages (data objects like views and procedures), resulting in incomplete data retrieval. This caused data gaps and inaccuracies in the crawled data. The issue has been resolved. The crawling process now works as expected, and the UI job logs no longer display warning messages. Stages (Data objects like views and procedures) are properly included during the crawling process.
In Administration > Connectors > Redshift RDAM (Redshift Data Access Manager) with OvalEdge as the master connector, previously, revoking a Role/Group assigned to a connector user did not update the source. The issue is now resolved, and revoking a Role/Group correctly applies the change at the source.
In Administration > Connectors > Crawl & Profile, when crawling schemas in Snowflake, a warning message was previously displayed in the UI job logs, and it seems to ignore views and procedures for stages. This issue has been resolved and the users are able to crawl schemas without any warning message.
In Administration > Connectors > Crawl & Profile, users had to manually configure different temporary paths each time they downloaded templates, data, or conducted ADL profiling. This was a time-consuming and error-prone process. This issue has been resolved by providing two different paths (e.g. TEMP and PATH).
In Administration > Connectors, previously, when a user was created and assigned a role or group in the connector user and roles modules, revoking the role or group did not update the source. The role or group continued to be displayed for the user in the source, even after it had been revoked in the application. This issue has been resolved, and the role or group is updated in the source.
In Administration > Connectors, users were unable to update the password for the connector user in the OvalEdge application. This was preventing the user from logging into the remote Redshift using the updated password. This issue has been resolved and users are able to update the password for the connector user in OvalEdge.
In Administration > Connectors, users were unable to revoke a user assigned on a schema. This issue has been resolved and users are now able to revoke users assigned on schemas.
In Administration > Connectors, when OvalEdge was set as the master in the connection settings, roles, groups, and users were not created in the remote system. This issue has been resolved and the users are created in a remote system when OvalEdge was set as the master in connection settings.
In Administration > Connectors > Crawl & Profile, previously, profiling results for SQL Server connections were empty. This included null count, distinct count, and other results. The issue has been resolved and Profiling results for SQL Connection are displayed.
In Administration > Connectors > Crawl & Profile, previously there was an issue where users couldn't see data under the Data tab when profiling a file in Azure Data Lake protected by Azure Key Vault. The issue has been resolved, and users can now effectively profile files in Azure Data Lake secured with Azure Key Vault, with the data becoming visible under the Data tab as expected.
In Administration > Connectors, users previously encountered an issue wherein they were unable to delete a Group from the Connectors Roles Tab. The issue has been resolved, and users can now seamlessly delete Groups from the Connectors Roles Tab as needed.
In Administration > Connectors, when conducting file profiling within Azure Data Lake secured by Azure Key Vault, an issue arose where the profiled data was not appearing within the Data tab. The issue has been resolved and the profiled data is now visible as expected under the Data tab.
In Administration > Connectors, users were previously unable to crawl the DBT connector due to the absence of a "Manifest.json" file in certain "RUN" files, and the crawling of those files remained unsuccessful. This issue has been resolved and users can now validate and crawl the DBT connector successfully.
In Administration > Connectors > Delta Lake, users encountered difficulties when profiling tables due to a syntax error, which resulted in a partial success status. This issue has been resolved by configuring the syntax, and users can now profile tables as expected.
In Administration > Connectors, the OvalEdge tool previously did not support connector views that contained the "UNPIVOT" operation. This issue has been resolved, and OvalEdge now supports the "UNPIVOT" operation in all queries and for all connectors
In Administration > Connectors > Redshift > Crawl & Profile, while crawling views and materialized views, an unwanted code, specifically an extra "Create view or Replace View View_name As" snippet, was being added to materialized views. This problem has been resolved, and users can now crawl and profile views without encountering any errors or unwanted code.
In Administration > Connectors > Denodo Connector, users were previously unable to build lineage due to the absence of JSON files, resulting in parse failure errors. This issue has been resolved and users can now build lineage successfully.
In Administration > Connectors > Crawl & Profile page, selecting multiple schemas at once resulted in an Internal Server Error. This issue has been resolved, and users can now select multiple schemas simultaneously for crawling and profiling without encountering this problem.
In Administration > Delta Lake Connector, there was an issue where users could validate the connection using invalid credentials. This issue has been resolved, and users can validate the connection only using valid credentials.
In Administration > Connector, for the S3 connector, an issue was identified where, after applying crawler rules using regex and recrawling the connector, the job log indicated a successful job, but no data was visible in the file manager. This issue has been resolved, and now the folders are correctly displayed on the file manager page as expected.
In Administration> Connectors, when adding a new Tableau connector and selecting "Yes" for token-based authentication, the labels were incorrectly shown as "Username" and "Password" instead of the expected "Token Name" and "Token".This issue has been resolved, and now it correctly displays the expected label names.
In Administration > Connectors > DB2 connector, an issue occurred when users enabled the bridge. Users encountered a problem where the "Select important schemas for crawling and profiling" pop-up window appeared empty, preventing the selection of schemas before crawling and profiling. This issue has been effectively resolved. Users can now access and select the preferred schemas for the DB2 connector as intended.
In Administration > Connectors, users encountered an access denied issue for all the connectors. This issue has been successfully resolved and users can now access the desired connectors as intended.
In Administration > Connectors > Power BI On-Premise environment, a few issues have been addressed,
- Certified Report Pop-up Not Displaying, Previously, when users logged in via the Chrome Plug-in and attempted to open certified reports in Power BI using the nine dots menu, the Certified Pop-up did not appear as expected. This issue has now been resolved, and the Certified Pop-up appears as expected.
- Error Message "Charts Not Found", Another issue occurred when published terms were applied to Power BI report columns and users tried to open these reports from the nine dots menu. In such cases, an error message stating "Charts Not Found" was displayed. This issue has been fixed.
In Administration > Connectors > S3 connector, previously, there was an issue where data crawled and cataloged from Parquet and Yaml files was not displayed in the Data Catalog's Data tab. This issue has been resolved. Now, data contained within the Parquet and Yaml files is clearly visible and accessible in the Data Catalog's Data tab.
In Administration > Connectors > AWS Athena connector, an issue was identified where, after data was crawled and cataloged, users encountered query execution errors when profiling on tables. As a result, profiling operations could not be successfully executed, and the required profile statistics were not displayed. This issue has been resolved. Users can now profile tables without encountering query execution errors, ensuring accurate and informative profile statistics are displayed as expected.
In Administration > Connectors > Redshift connector, an issue occurred after successfully establishing the connection and building lineage. Some tables from the base to staging were omitted, resulting in incomplete lineage records. This issue has been resolved. Now, the process successfully captures all tables, ensuring a comprehensive lineage representation of your data.
In Administration > Users & Roles > Connector Policies, previously, when users attempted to filter by the source column, the expected "Remote" text checkbox was not displayed. Instead, the text checkbox for "Masking" was incorrectly shown. The issue has been resolved and now when users filter by the source column, the correct "Remote" text checkbox is displayed.
In Administration > Users & Roles > Connector Roles, users encountered an issue where the Warehouse filter option didn't work correctly for sorting results. The issue has been resolved and users can now sort the Warehouse filter option results without any errors.
In Administration > Users & Roles > Connectors, users were unable to map a user to a group. This issue has been resolved and users are now able to map users to groups.
In Administration > Users and Roles > Connector Users, previously the application allowed the combination of user privileges, contradicting their intended exclusivity. This led to scenarios where users could simultaneously possess 'nocreatedb' and 'created' privileges, despite the expectation that one should override the other. This issue has been resolved, and users can now apply privileges in a manner that ensures proper overriding of old ones.
In Administration > Users & Roles, previously, a problem occurred where if a role was linked with Domain Creator or Project Admin (in "System Settings > Users and Roles" ) and then deleted through the user interface (UI), the role still remained in the field. This issue has been fixed by adding a validation message when attempting to delete a role from the UI. This message guides users to first remove the role from the system settings under the specified key before proceeding with deletion. This improvement simplifies role management and prevents accidental deletions.
In Administration > Security, when users disable a governance role, its corresponding checkbox in the Data Catalog or Business Glossary should also be disabled. Previously, these checkboxes remained active, even though they didn’t work in those modules. The issue has been resolved, and when a governance role is disabled in the Administration's Security section, the corresponding checkboxes in the Data Catalog or Business Glossary are now correctly disabled.
In Administration > Security > Databases, previously when users selected the custodian name as the custodian filter option and applied the filter, it didn't display the expected results associated with the custodian name. The issue has been resolved and now users can get the custodian-filtered results accurately.
In Administration > Security > Folders, previously when searching for the Admin Roles & Users filter with user options, all roles and users were displayed, including the user option, rather than showing only the specific users' details. The issue has been resolved, and users can now filter with particular users or roles, and only the associated results are displayed.
In Administration > Security, the "Delete folder" option in the security section was not functional previously. When users visited the security folder page and attempted to use the "Delete folder" option, it didn't work as expected. The issue has been resolved, and users now can visit the security folder page and to delete folders as desired.
In Administration > Security > Databases, previously, when using the "Governance Role 5" filter to select the "#Inbox Team," the expected results were not displayed. Selecting "Governance Role 4" and the "OE_Admin" checkbox showed the results for the "#Inbox Team." Directly selecting "#Inbox Team" via the "Governance Role 5" filter did not yield the expected results. The issue has been resolved, and Users can now directly select the "#Inbox Team" using the "Governance Role 5" filter, and the expected results are displayed as intended.
In Administration > Security > Story Zone, previously, when users applied filters to view authorized roles and users in the "Story Zone," the system incorrectly displayed roles and users that should not have been available for selection. The issue has been resolved; when users filter for authorized roles and users in the "Story Zone," the system now correctly displays only the available roles and users as expected.
In Administration > Security > Databases, when users selected both the Active and Inactive checkboxes in the status filter, the system displayed only the Inactive results. This behavior was not as expected- both Active and Inactive results should have been shown. This issue has been resolved, and now when users select both the Active and Inactive checkboxes in the status filter, both Active and Inactive results are displayed as expected, ensuring accurate visibility of database statuses.
In Administration > Security, there was an issue with role-based access for the "service desk" keyword, which caused an unresponsive drop-down menu when attempting to change the license type selection from "author" to other options. This problem was isolated to the "service desk" keyword and did not affect other keywords. The issue has been resolved. Now, in the "Security" module, users can successfully change the license type selection from "author" to other options for the "service desk" keyword without any issues with the drop-down menu. The role-based access for the "service desk" keyword is now functioning as expected, providing users with the appropriate license type selection based on their permissions.
In Administration > Security > Applications, there was an issue with the mouse hover behavior for the enable/disable button. When users hovered over this button to enable or disable access for viewers or contributors, it incorrectly displayed the text as "disabled" regardless of the actual status. The issue has been resolved. When users hover over the enable/disable button, it now correctly displays the appropriate status, providing a clearer user interface.
In Administration > Security > Databases, when users set the crawled filter option to "Yes," they were able to see the corresponding "Yes" results, and when they chose "No," they could view the associated "No" results. The problem occurred when users selected both "Yes" and "No" options together; in this case, they could only see "Yes" results. The issue has been resolved, and when users select both "Yes" and "No" options together in the crawled filter, they correctly see both "Yes" and "No" results as expected.
In Administration > Security > Domains, when trying to change role permissions from Read Write (RW) to Administrator (ADM), the operation functioned correctly, but when attempting to change from Administrator (ADM) to Read Write (RW), it did not work as expected. The issue has been resolved and changing role permissions from Administrator (ADM) to Read Write (RW) is working as expected.
In Administration > Security > Domains, users were unable to save updates to Governance roles via the '9 dots' menu. The 'Save' button was not working as expected. This issue has been resolved and users can now save the Governance roles as expected.
In Administration > Security section, users previously encountered a limitation where they could not add or remove users from schemas and tables within the RDAM environment. The issue has been resolved and users now have the capability to efficiently add or remove users from both schemas and tables.
In Administration > Advanced Jobs, when working with AdvanceJob attributes, users discovered that copying and pasting a value cleared the entire attribute value and replaced it with only the copied part. The issue has been resolved and users can copy and paste the selected text in the attribute value.
In Administration > Advance Jobs, previously users faced job log errors when attempting to import Data Quality Rules using a CSV file. The upload process for the CSV file was unsuccessful, and the job log errors hindered the proper import of the Data Quality Rules. The issue has been resolved, and users can now upload CSV files to import Data Quality Rules in the Advance Jobs section of the Administration module without encountering any errors.
In Administration > Advanced Jobs, while attempting to upload a CSV file through the Advanced Jobs tool in the OvalEdge Application UI, the user was not previously receiving the Stats Query and Failed Query functionalities. This issue has been resolved and the user is able to view all the queries in the associated objects in the data quality.
In Administration > Advanced Jobs, users encountered a problem where the Data Quality Report (DQR) score was not visible on the quality index page after migrating to a new release version. To address this issue, an advanced job "DQ Score calculation for 61" is designed to update the DQR score, ensuring it reflects the most current and accurate data quality information. As a result, users can now access and view the DQR score on the quality index page without any disruptions.
In Administration > Advanced Jobs, previously, there was a problem when users executed the "Discover Primary and Foreign Key Recommendations" advanced job (by providing the required attributes such as connector ID, name and schema ID, or name and if the user selected the option to build relationships across schemas as true) and ran the advanced job. The system was unable to establish relationships between new objects and existing objects. This issue has been resolved. Now, when users run this advanced job and select the option to build relationships across schemas, the system accurately builds relationships between the selected schemas.
In Administration > Schedule, previously, when attempting to select and save a schedule state (such as "active" or "inactive"), the system returned an error with the message "problem occurred." The issue has been resolved, and users can now successfully select and save a scheduled state (e.g., "active" or "inactive") without encountering the "problem occurred" error.
In Administration > System Settings, when users attempted to filter the “Last Updated By” column by a specific name, the filtering process didn’t effectively narrow down the results. Instead, it continued to display all available columns. This issue was observed across multiple system paths, including Users and Roles, Lineage, Notifications (Settings), SSO, Proxy, Connector, and AI. The issue has been resolved, and users can now successfully filter the “Last Updated By” column by a specific name in all the system paths.
In Administration > System Settings > Notifications & Alerts, previously, Slack notifications were coming in HTML format instead of the expected enriched Markdown format. This occurred when setting up Slack Integration in the OvalEdge application and executing Data Quality Rules. The issue has been resolved and users can now receive Slack notifications in the Markdown format when setting up Slack Integration in the OvalEdge application and executing Data Quality Rules.
In Administration > System Settings > Others, users encountered an issue while trying to download the source code using the "export source code" option. Initially, the code was saved to a temporary path instead of directly downloading to the local system, leading to difficulties in accessing and managing the source code. The issue has now been resolved. When users select the "export source code" option, the code is correctly downloaded directly to their local system.
In Administration > System Settings > Notifications & Alerts, previously, users received notifications in their inbox for messages they are not tagged in or shouldn't have access to, violating expected behavior. Also, users could clear messages but could not delete them, an action that needs prompt resolution. This issue has been resolved, and users can no longer receive notifications for messages they are not supposed to access in their inbox. Additionally, they can now both clear and delete messages as expected, improving overall message management.
In Administration > Audit Trials, previously, the audit trails were not capturing the actions that were being revoked in the remote. This meant that there was no record of the actions that had been taken, which made it difficult to track changes and troubleshoot problems. The issue has been resolved and the audit trails now capture all actions that are taken in the remote, including actions that are revoked.
In Administration > Audit Trials, users were previously unable to access update-associated comments made to a user within the Audit Trails. The issue has been resolved. Users can now access comments within the Audit Trails, providing a more comprehensive view of user updates and activities.
In Administration > Audit Trials, previously, users were unable to access the remote privileges of a user within the User List. The issue has been resolved and users can now conveniently view the remote privileges of a user directly from the User List, enhancing their ability to manage and monitor user permissions effectively.

Release6.1.1.1

Improvements

OvalEdge Licenses

Global Search

Tags

Data Catalog

Lineage Enhancements

Business Glossary

Dashboard

Service Desk

Data Quality

My Resources

Query Sheet

Advanced Tools

Administration

Logs Backup

New Connectors

New System Settings

New Advanced Jobs

Bugs Fixes

Global Search

Tags

Data Catalog

Business Glossary

Projects

Dashboards

Service Desk

Data Quality

My Resources

File Manager

Query Sheet

Jobs

Advanced Tools

Administration