Ataccama ONE Agentic ONE Desktop ONE DQ&C ONE MDM ONE RDM ONE Runtime Server
User Community Service Desk Downloads

April 2026

This release expands pipeline monitoring and AI Agent capabilities, introduces the MCP Trust Layer for external AI clients, and adds new options for working with reference data.

Datetime timezone support in reference data

You can now configure a display timezone so that all datetime values in reference data are shown in a timezone that matches your team’s location or workflow.

The display timezone applies across the entire reference data module:

  • Grid columns, filters, cell editing, bulk edit, and record detail all show values converted to the selected timezone.

  • Under the hood, datetime values remain stored in UTC and are converted back automatically when saved.

You can also specify the timezone of source data when changing a column to the datetime data type or importing data from a file.

To configure the display timezone, see Configure RDM Settings.

Duplicate reference data records

Reuse existing reference data records as starting points for new entries, skipping manual re-entry of shared field values.

For details, see Duplicate records.

Data transformations in AI Agent

You can now use the AI Agent to find, run, and manage transformation plans, and generate transformation rules from a natural language description.

  • Find plans: Search for transformation plans by name and get an overview.

  • Run or schedule plans: Run a plan immediately or set a recurring schedule.

  • Manage plan lifecycle: Publish, discard drafts, or delete plans without leaving the chat.

  • Get AI descriptions: Ask the Agent to explain what a plan does in plain language.

  • Generate transformation rules: Describe the logic you need and the Agent creates the rule.

For example prompts, see Transformation management.

Connect external AI agents through the MCP Trust Layer

Query Ataccama ONE catalog metadata, ownership details, business terms, and data quality metrics directly from your AI assistant.

The Ataccama Model Context Protocol (MCP) Trust Layer is a remote, hosted interface that lets external AI clients access selected Ataccama ONE information over HTTPS. There is nothing to install locally.

The MCP Trust Layer is:

  • Remote and hosted: The MCP server runs in your Ataccama ONE environment, with no local server, runtime, or package manager required.

  • Read-only: Query data without modifying it.

  • Authenticated: Supports single sign-on (SSO) with OAuth 2.0 and machine-to-machine (M2M) authentication with client ID and client secret. Your Ataccama permissions determine which data you can access.

  • Configurable: Turn individual tools on or off in your AI client.

Supported clients include Claude Desktop, Claude Code, Microsoft Copilot Studio, and Amazon Bedrock.

For an overview of available tools and authentication options, see MCP Trust Layer for External AI Agents. For setup instructions, see Connect to the MCP Trust Layer.

Back references in search filters

Configure search filters based on entities that reference your listed entity, not just the ones it references itself. For example, filter the term listing by the catalog items that use each term.

Set up back references in Global settings > Search configurations by marking indexed properties as Back reference.

For details, see Back references.

Pipeline monitoring for GCP Cloud Data Fusion

Data Observability pipeline monitoring now supports GCP Cloud Data Fusion, bringing the total to six supported orchestrators: dbt Core, Airflow, Dagster, AWS Glue, Azure Data Factory, and GCP Cloud Data Fusion.

The integration is deployed using a provided package available on request, and requires CDF 6.7.0 or later.

For setup instructions, see Configure Cloud Data Fusion with OpenLineage.

Authenticate to Amazon S3 with AWS Assume Role

Connect to Amazon S3 using short-lived credentials instead of static access keys.

In addition to AWS access keys, the Amazon S3 connection now supports AWS Assume Role authentication with OpenID Connect (OIDC) federation.

Use AWS Assume Role when:

  • Your security policy prohibits long-lived AWS access keys, or rotating them is operationally costly.

  • You want to manage Ataccama’s S3 access entirely through IAM.

  • You need detailed audit trails of every credential issuance and S3 access.

Setup involves registering the Ataccama identity provider in your AWS account and creating an IAM role that trusts it. You then provide the role ARN when adding credentials in ONE.

For setup steps, see Amazon S3 Connection.

Was this page useful?