Ataccama 14.3.0 Release Notes

Stewardship is now the primary solution for managing data asset ownership in ONE. You assign ownership of your data assets to groups, after which appropriate levels of access to the asset are assigned to the members of the group depending on their governance role.

Once selected, the owner group is represented in the Stewardship widget on the Overview tab of the asset with the list of users assigned to relevant governance roles. You can also view and filter listing screens based on the Stewardship column.

We highly recommended assigning stewardship on all of your existing data assets as it brings the following advantages:

For detailed information, see Stewardship.

ONE now comes with a default home page that all users land on when they log in to the application.

ONE administrators can customize this page and create secondary landing pages and share them with groups and individual users. For more information, see The Home Page.

It is now possible to select whether you want time-independent or time-dependent anomaly detection to be used during profiling. For more information, see Anomaly Detection in Catalog Items.

The anomaly detection on profiles has been improved to identify previously hard-to-detect anomalies more effectively and to reduce the overall number of false positives.

The model is now better equipped to detect unexpected nulls, unexpected negative or positive values, unexpected zero values, and changes from established trends. Regarding false positives, values identical to those previously dismissed as not anomalous are no longer flagged, and values are no longer flagged based on frequency if no significant key or changes are detected. The low-sensitivity options are now even less sensitive, so altering the anomaly detection sensitivity can help if false positives persist.

Get notified when new terms are detected in your observed system or when existing terms are newly added to attributes. You can also enable notifications for when terms are applied manually.

Term notifications are configured within the Advanced configuration flow for observed systems. For more information, see Data Observability.

Check notifications in the issues table in the data observability dashboard. From here, you can also add newly-found terms to the list of observed terms or review term suggestions.

From the data observability dashboard, you can then add the terms to the observed system or accept the term suggestion accordingly. For more information, see Data Observability Dashboards.

You can now see the status of all observed systems after selecting Data Observability in the left navigation menu. Filter the selection by connection type, catalog item count, observability status, observability monitoring, and stewardship, as well as according to the selected timeframe (such as day, week, month). Use the icons to switch between table view and list view.

We now support working with reports from Tableau and Power BI in ONE. To import reports from these BI tools to ONE, make sure that all the prerequisites are met. For more information, see Reports from Tableau and Reports from Power BI respectively.

You can also manually document reports, sources, or datasets from BI tools other than Tableau, PowerBI, and Data Stories by creating a generic report and using your BI tool’s APIs. However, the functionality of these reports depends on the BI tool connection options and might be limited. For more information, see Reports from Other BI Tools.

We have added support for Databricks Unity Catalog for new data sources. Databricks Unity Catalog provides a unified approach to governing your data and AI assets across Databricks workspaces, along with centralized access control, auditing, lineage, and data discovery capabilities. In Unity Catalog, data assets are organized in three levels, starting from the highest: Catalog > Schema > Table, allowing you to work with multiple catalogs at once. For more information, see Databricks Unity Catalog Connection.

ONE Data is now better equipped to assist you with data remediation.

Easily export all invalid records from a catalog item to ONE Data using the Data Export feature. Once you select the catalog item for export, choose Invalid records instead of All records. Before your table is created, DQ evaluation runs on the whole table. For more detailed instructions, see Create a Table, section Import from catalog item.

When your data is imported, use the new data quality filters to quickly find specific data quality issues in your table. Filter by entire DQ dimension, DQ rule, or a specific condition within a rule. In addition, filters can apply to a specific attribute, all attributes, or any. For more details, see Filters.

In addition to adding or removing attributes, optimistic locking is now also applied when duplicating, renaming, or reordering attributes. Your changes are only saved if the table structure hasn’t been modified by another user in the meantime. Otherwise, you need to load the latest changes first before continuing.

To help you understand why your change is not accepted and maintain the integrity of the data displayed, we have also introduced more robust error handling. In case an issue occurs, for example, if the table is locked due to a long-running operation or the attribute name already exists, follow the instructions displayed in the application to solve it.

User actions from ONE Data can be monitored in the Audit module. Explore audit logs directly in ONE (Audit tab), or using the dedicated Audit API. To learn more, see Audit and Audit API respectively.

For ONE Data, the following actions are audited:

Operations related to ONE Data use the prefix [ONE Data].

In addition to Ataccama ONE PaaS solution, ONE Data can now also be deployed in self-managed, virtual machine-based solutions using Ansible.

Automatic task configurations tab can be accessed from the left navigation panel.

The functionality can also be turned off, and you can enable and run the creation process manually (for example, in case the filters need to be reviewed by other team member first).

You can view automatically created tasks on the Tasks or My tasks tab along with manually created tasks. For more information, see Automatic Task Configuration.

To determine your upgrade path, see MDM Upgrade Procedure and MDM 14.3.0 Upgrade Notes.

We have introduced a native REST API for RDM, allowing you to read metadata and data from your RDM instance using REST interfaces. This way, you can retrieve the application status and configured data models, or list table records using basic or advanced filtering options.

In addition, you can use the API to generate an encoded link to a specific record for easier sharing.

To learn more, see RDM REST API.

To determine your upgrade path, see RDM 14.3.0 Upgrade Notes.