ONE Desktop ONE DQ&C ONE MDM ONE RDM ONE Runtime Server
latest (16.1.0) 16.0.0 15.4.0 15.3.0 15.2.0 15.1.0 14.5.x 13.9.x 13.8.x 13.7.x 13.6.x 13.5.0 13.4.x 13.3.x 13.2.x
User Community Service Desk Downloads
If you can't find the product or version you're looking for, visit support.ataccama.com/downloads

Ataccama 16.1.0 Release Notes

Products

  • ONE Data Quality & Catalog, including ONE Data and Data Stories

  • ONE RDM

  • ONE MDM

Release date

April 10, 2025

Downloads

support.ataccama.com/downloads/16.1.0

Security updates

Ataccama Security Advisories

ONE

Azure Synapse Pushdown Processing

Azure Synapse SQL pushdown processing is now available. Run profiling and data quality evaluation as an SQL pushdown workload directly in Azure Synapse and benefit from enhanced security, performance, and scalability.

Once pushdown is enabled for profiling, all catalog items under that connection are profiled using pushdown. For DQ evaluation using pushdown, you can exclude selected catalog items if they use rules not supported in pushdown. This flexibility allows you to disable pushdown for DQ evaluation at a catalog item level or for individual monitoring projects.

For more details about how it works and how to set it up for your connection, see Azure Synapse Pushdown Processing.

Support for Apache Avro

You can now import and process Apache Avro assets in ONE, namely Avro files, tables, and partitioned tables. When assets other than Avro files are imported, ONE analyzes the asset and then creates a catalog item with the attributes based on the asset.

To learn more, see Apache Avro.

Support for Built-In Lineage Scanner in Self-Managed Deployments

Ataccama Lineage Scanners can now be installed in built-in mode in self-managed, on-premise deployments. Previously, the built-in service was compatible only with Ataccama Cloud environments.

Display All Rules in Monitoring Projects

Display all rules applied to a catalog item in monitoring project: select Show all rules at once on the monitoring project Configuration & Results tab. This is particularly useful when you want to search for a specific rule applied to the project.

720

Improved Full-Text Search Ranking

We have enhanced the full-text search functionality to ensure that the most relevant results appear first.

The relevance of search results is now ranked in the following order:

  1. Exact matches: Results that perfectly match the search query.

  2. Partial matches: Results with partial matches.

  3. Multi-token matches: Results that match across multiple tokens (words or phrases).

When search results include attributes from a single catalog item, these are also sorted by relevance.

Snowflake Pushdown Processing Schema Selection

Snowflake pushdown processing now allows you to specify a schema other than the default public schema when setting up your connection. Previously, only the public schema of the working database could be utilized for pushdown processing.

For Snowflake pushdown configuration, see Snowflake Pushdown Processing.

JWT Authentication for HashiCorp Vault

We have added JWT authentication as a new method for connecting to HashiCorp Vault in Secret Management Services. This expands your authentication options when integrating ONE with your HashiCorp Vault for secure secret management.

For more information about using HashiCorp Vault as a secret management service and configuring JWT authentication, see Secret Management Services.

Data Stories

Detailed Drill-Down for Monitoring Projects

Data Stories now supports drill-down to the rule or attribute level when visualizing DQ results from monitoring projects. This level of detail was previously supported only for catalog-based DQ results.

The enhancement provides deeper insights and a more granular analysis of your data quality metrics within Data Stories. As such, it is especially valuable if you are using monitoring projects for your data quality initiatives, as you no longer need to compromise on visualization capabilities when building data quality dashboards and reports.

For more information, and step-by-step tutorials, see Monitoring projects > Attribute-level DQ and Monitoring projects > Rule-level DQ in Data Quality Reporting.

MDM

Manage Runtime Parameters from Admin Center

Managing runtime parameters for the MDM Server is now easier, more transparent, and more secure.

Edit runtime parameters directly from the UI, from the Runtime Parameters tab in the MDM Web App Admin Center. Previously, this screen only showed a list of configured parameters.

You can also undo your last change, revert the value to the previous or the default one (available only after saving). These options become available after you edit a value, allowing you to keep track of the edits more easily.

To ensure consistency in configuration and help prevent conflicts and errors, we added the Save all changes option. This way, you can propagate changes immediately after modifying a group of parameters.

Runtime Parameters screen in MDM Admin Center
Note that some parameters might require a server restart to take effect. Look for a yellow dot next to the parameter to identify changes that are pending restart.

To prevent unauthorized changes, only a limited number of users can edit runtime parameters. The required role is MDM_server_admin by default, the specific name depends on your setup (see Additional Improvements to Admin Center and MDM Admin Center permission changes).

For more details, see MDM Web App Admin Center > Runtime Parameters.

Some runtime parameters, such as those related to the Matching step or resource usage, are still configured using the runtime.properties file, allowing you to use different settings for each instance. For details, refer to Runtime Parameters and MDM 16.1.0 Upgrade Notes.

Stop a Task without Server Restart

To minimize system downtime and productivity disruptions and manage the server workload more efficiently, MDM Admin Center is now equipped with options to cancel a queued task or stop a running task.

To cancel or stop a task, go to the MDM Web App Admin Center > Task Execution tab. The available action depends on the task status.

Task Execution screen in MDM Admin Center

For more details, see Cancel task and Stop task respectively.

Additionally, the same action is available over REST API. To cancel or stop a task, send a request to the /tasks/task/{id}/terminate endpoint.

For details, see Cancel or stop system task.

Additional Improvements to Admin Center

Changes to permissions

For more granular user access management, we have made the following updates:

  • A new role is required for server management (defined in the property ataccama.one.mdm.admin-center.manager.required-roles). By default, this role is MDM_server_admin and it allows you to manage the server dashboard, runtime parameters, and logging settings.

  • To view the Server Dashboard, Runtime Parameters, and Logging Configuration screens, you need one of the roles defined in ataccama.one.mdm.admin-center.read-only.required-roles and ataccama.one.mdm.admin-center.full-access.required-roles. In this case, you cannot make any changes to the screens listed.

    For details about the required roles and where to define them, see MDM Admin Center permissions.

Better monitoring of task execution

To quickly access related tasks for a specific batch load or export, use a shortcut from the Load Operations or Export Operations tab respectively.

If the operation has finished, select the timestamp in the Last run column. If the operation is running, select the Operation name.

Export Operations screen in Admin Center
The operation row is now highlighted in blue during execution.

In addition, it is possible to download task execution details in HTML format for further analysis. Open the task details page (Task Execution > [Task]) and select Download page.

New shortcut from MDM Web App

Navigating to Admin Center is now simpler and faster. You can access it from the MDM Web Application main navigation provided that you have view permissions or higher.

Shortcut to Admin Center

Fixes

ONE

Click here to expand

  • ONE-63349: In transformation plans, the Database output step can write to the database when configured to use the Replace data write strategy.

  • ONE-65165: SQL catalog items import selectively when used in reconciliation projects instead of importing the entire source.

  • ONE-66207, ONE-65909: Rule variables support multiple data types other than Boolean.

  • ONE-68207, ONE-68399: Monitoring project status is correctly displayed in the web application. Previously, some projects were shown as still running even though the processing was actually finished.

  • ONE-65861: If the list of unpublished rules consists of multiple pages, you can navigate to any of the pages.

  • ONE-65672: Slack channel refresh correctly reports all failures instead of silently handling errors.

  • ONE-56489: When you accept a rule suggestion and then revert your decision, the rule is removed from Applied rules.

  • ONE-67104: Integer values no longer overflow when displaying results of BigQuery DQ pushdown processing.

  • ONE-68712: Rule variables correctly transform attributes from STRING to INTEGER and FLOAT data types.

  • ONE-56486: Accepted rule suggestions are accessible in the sidebar.

  • ONE-66749: Catalog item loading performance was improved by optimizing pushdown support loading.

  • ONE-68110: Updated lookups are correctly reflected in DQ firewalls.

  • ONE-67217: In monitoring projects, the Reports tab no longer shows inconsistent values for Overall Quality after applying a year filter and switching between different project runs.

  • ONE-62993: The Test Rule function works as expected in the quick DQ rule creation workflow that was started from a BigQuery catalog item from a source with pushdown enabled.

  • ONE-64849: Error notifications no longer appear after accessing the rule library under Data Quality > Rules > DQ Evaluation Rules.

  • ONE-66591: Monitoring project import no longer occasionally fails when using implicit mapping.

  • ONE-68079: Improved error messaging when trying to create a DQ firewall from a catalog item containing attributes of unsupported data types.

  • ONE-62735: Invalid samples display all failed rules for a particular row after processing on Databricks.

  • ONE-65064: In DQ firewalls, business readiness alerts provide correct information instead of showing empty DQF logs.

  • ONE-66164: Type errors no longer appear on rule listing pages, ensuring consistent UI experience.

  • ONE-66949, ONE-66445: The DQ Monitoring Project Check Results step in ONE Desktop contains the ResultName column, allowing you to filter out invalid results based on its values.

  • ONE-64880: In transformation plans, validation messages in the Data remediation output step display the correct information.

  • ONE-64791: ONE Data tables are deleted completely without leaving any remnants. As a result, you can delete ONE Data table and then create a new one with the same name.

  • ONE-66231: Slack registration has the option to bypass the proxy and send registrations directly to ONE.

  • ONE-64831: In transformation plans, if you write a wrong condition into the Condition step, you can see the error in the tooltip.

  • ONE-65320: The Fetch rules tab in the Debugging Tools sidebar works as expected instead of showing the Mobx error.

  • ONE-61521: The Directly applied Rules text displays correctly when you open a rule preview on the attribute Profile & DQ Insights tab.

  • ONE-56220: Fixed naming inconsistencies on the attribute Profile & DQ insights tab (Applied rules is now used instead of Assigned rules).

  • ONE-65175: In Data Observability Dashboards, the Freshness tab in the issues table displays only catalog items from the selected data source, instead of all catalog items.

  • ONE-68910: MMM no longer reports unexpected Term Suggestions errors after upgrading to v15.4.0-patch15.

  • ONE-68904: Fixed an issue related to undeclared MinIO buckets that led to errors when deploying Ataccama Cloud environments.

  • ONE-68570: Previews of reports from Tableau Cloud sources are correctly loaded..

  • ONE-60626: Fixed the issue with high database load in Ataccama Cloud environments running in the US region.

  • ONE-67868, ONE-65565: Improvements to Elasticsearch alerts in Ataccama Cloud environments.

  • ONE-65985: Fixed the issue where, in certain situations, the system canceled review workflows, returning the entity to the draft state.

  • ONE-65528: Sorting of reports in Data Catalog works as expected.

  • ONE-60392: The notifications view of the Processing Center correctly responds to user actions even when the browser window is minimized.

  • ONE-68198: Profiling results on the catalog item Profile & DQ insights tab display correct Top 3 values.

  • ONE-67382: Custom previews for reports are saved and displayed as expected.

  • ONE-67932: The Term Suggestions screen loads and displays without issues.

  • ONE-65601: Stability improvements to Anomaly Detection and Term Suggestions services in Ataccama Cloud environments.

  • ONE-65624: The All tab correctly displays all (published and unpublished) results. This applies to all screens containing Published/Unpublished/All tabs.

  • ONE-65560: Fixed the issues where the source page was not accessible and the layout did not render correctly after upgrading to 16.0.0.

  • ONE-65415: The source connection browser no longer freezes during loading operations.

  • ONE-65941, ONE-67626: Term suggestions results are correctly returned.

  • ONE-65209: The terms dropdown that opens after you select Add Term correctly displays how many items are loaded when loading 20 items.

  • ONE-69677: Monitoring projects on BigQuery catalog items work as expected when pushdown is enabled.

  • ONE-69520: Stability improvements to Data Processing Engine (DPE) in cloud deployments. As a result, jobs don’t fail if DPE gets disconnected for a short time.

  • ONE-68847: Added an alert for Data Processing Module indicating when the gRPC pool is exhausted.

  • ONE-68802: Profiling on S3 sources works as expected.

  • ONE-68405: Fixed the issue where importing some schemas from a Snowflake data source failed.

  • ONE-68350: Security certificates work correctly for data processing jobs.

  • ONE-67727: You can import a Power BI Report and a Power BI dataset at the same time without issues.

  • ONE-67617: Monitoring projects works correctly with Spark pushdown enabled.

  • ONE-67275: Parquet tables from S3 storage are successfully imported and profiled, even if the Parquet directory on S3 contains a 0-byte file.

  • ONE-67252: In SAP Hana sources, the LOCATE statement is correctly processed during profiling and in monitoring projects.

  • ONE-66991: Using multiple Data Processing Engines (DPEs) connected to multiple Databricks clusters works without issues.

  • ONE-66987: An error is no longer thrown when accessing MinIO on Databricks.

  • ONE-66953: When importing SQL catalog items from an Oracle data source, the data type 'NUMBER' with no scale and no precision is treated as a decimal number, instead of an integer.

  • ONE-66952: Profiling and DQ evaluation in monitoring projects work as expected in Salesforce sources when using Databricks pushdown.

  • ONE-66903: Improved DPE logging: the message to fix corrupt slots is no longer incorrectly shown.

  • ONE-66770: DPM tasks run without issues when an S3 connection exists in both runtime configurations (in DPM and in ONE Desktop).

  • ONE-66353: Hybrid DPEs can successfully connect to Spark clusters.

  • ONE-66341: In Ataccama Cloud environments, profiling large catalog items doesn’t fail when trying to upload profiling results to ONE Object Storage (MinIO).

  • ONE-66268: In Ataccama Cloud, it is possible to connect to hybrid DPE via AWS PrivateLink.

  • ONE-66211: Attributes from imported SAP tables are properly displayed.

  • ONE-66109: Keycloak database issues trigger alerts as expected.

  • ONE-65944: When profiling virtual catalog items with a Catalog Item Reader step, a DPE engine is correctly selected for the job.

  • ONE-65894: It is possible to run DQ evaluation that includes DQ rules containing references to lookups with a 'LONG' data type on Snowflake when pushdown processing is enabled.

  • ONE-65742: Pushdown tag is correctly positioned on the catalog item listing.

  • ONE-65265: Fixed the issue where previewing and profiling Databricks tables resulted in a deserializing error.

  • ONE-62935: Spark job name can be configured when running Spark profiling with a job cluster.

MDM

Click here to expand

  • ONE-69302: Oracle database hints now respect the specified query limit.

  • ONE-67786, ONE-66803: You can now deactivate two or more records in a single draft.

  • ONE-67365: Changing date columns in a draft works without issues.

  • ONE-67010: Fixed the database connection leak when running master data consolidation in parallel.

  • ONE-68975: Matching parallelism settings are correctly tracked in logs.

  • ONE-65700: When manually merging two records, a permissions error is no longer incorrectly reported.

  • ONE-42109: Path variables and resources are now correctly read in workflows in the MDM server.

  • ONE-65606: Traversing plan publishers can handle entities with multiple mutual relationships without issues. Previously, the resulting publisher configuration was reported as not valid.

  • ONE-66302: When a source has its origin changed within the same system, old records are deactivated as expected.

  • ONE-62785: Fixed the issue where reprocessing operations would fail on proposal committing due to duplicates and conflict handling.

  • ONE-64692: MDM migration load is generated for all entities.

  • ONE-64588: Fixed the SQL logic due to which data in labeled related MN lists was not correctly displayed.

  • ONE-62554: If two related records are processed in parallel, the conflict is correctly identified.

  • ONE-61856: The space used by the Versioned File System component is freed up as expected after server restart.

  • ONE-55173: MDM Web App Admin Center includes the option to download execution status details.

  • ONE-54083: Users with MDM_viewer role cannot discard tasks over REST API.

  • ONE-57381: Users with MDM_viewer role no longer see or use the Reject proposal action.

  • ONE-64072: Added a validation ensuring that multiple event handlers aren’t sharing a single persistence folder.

  • ONE-62808: You can download performance statistics from MDM Web App Admin Center even if the pg_stat_statements plugin is missing.

  • ONE-62560: Improved logging in Ataccama Cloud environments when invalid Git configuration is used.

  • ONE-49470: Improved error logging when server startup fails due to no database storage defined for event handlers.

  • ONE-29585: Fixed the issue where VLDB persistence would fail on startup with the following error: "ResultSet not positioned properly, perhaps you need to call next."

  • ONE-67463: Improved logging of the Collect output stage during matching.

  • ONE-64480: Improved server monitoring in cloud deployments.

  • ONE-65535: All connectors now remove temporary folders after server reload.

  • ONE-60073: MDM conditional export filtering supports conditions using eng_* columns.

RDM

Click here to expand

  • ONE-63933: The Multi-edit option now allows changing the record value to NULL.

  • ONE-49912: The Create dump option correctly populates the export even if one of the tables exported contains an MN-reference column.

  • ONE-62347: When editing an existing record, permission restrictions are applied as expected to Boolean fields.

  • ONE-49919: Fixed the issue where a database synchronization plan using the RDM Reader step would fail due to one of the tables containing an MN-reference column.

  • ONE-65018: Improved messaging when a table is locked due to multiple users editing it at the same time.

  • ONE-68222: In the web application, filtered fields and reordered columns are correctly saved and displayed at the next login session.

  • ONE-67787: In RDM webapp, dropdown filters work as expected.

  • ONE-66371: Improvements to UI to ensure a smoother and more consistent user experience.

  • ONE-65554: In cloud environments, RDM fails if Keycloak is not available on startup.

  • ONE-56559: In cloud environments, you can change the Git repository without the server failing.

  • ONE-70360: In cloud environments, when manually selecting a commit in the Admin Center, the selected branch is correctly stored in the database.

  • ONE-57357: On startup, RDM validates the database setup when using MS SQL and the server fails if there are issues detected.

  • ONE-56644: Improved error messaging if RDM Server cannot be accessed due to incorrect credentials: the HTTP response status code returned is no longer 500 Internal Server Error but 401 Unauthorized.

ONE Runtime Server

Click here to expand

  • ONE-66370: Fixed the issue with worker threads in parallel processing getting locked and slowing down the server performance.

ONE Desktop

Click here to expand

  • ONE-69887: Opening a lookup file in ONE Desktop doesn’t result in an error.

  • ONE-65019: Improvements to SAP RFC Reader step: the step can be debugged without issues.

Was this page useful?