Ataccama ONE Agentic ONE Desktop ONE DQ&C ONE MDM ONE RDM ONE Runtime Server
latest (17.2.0) 17.1.0 17.0.0 16.3.x 16.2.0 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
Downloads

Tasks and Publishing

Changes to master data don’t go live right away. Instead, they are collected in a task, reviewed when the workflow requires it, and then published or discarded. The task keeps the changes together with who made them, why, and where they are in the process.

Tasks and drafts

A task is a collection of changes to one or several records.

The changes themselves are stored in a draft, which lists every change in the task. Tasks created in the legacy interface can have several drafts.

Every time you start editing a record, a task with a draft is created for you. AI agents can also create tasks through the MDM MCP Server. See Create and manage tasks.

Task types

The task type says what the task is for and which actions the task detail offers:

  • Record change: Edit or delete records.

  • Manual match: Merge records that matching didn’t put together.

  • Matching proposal: Resolve matching proposals. See Matching Proposals.

  • Create: Create a record.

  • Generic: Any other work. A generic task has no linked records and no draft.

Workflow

A workflow is the path a task takes from the first change to publishing or discarding. It makes sure changes are reviewed by the right people before they reach the MDM Server and other systems.

Your permissions determine which actions you can perform on tasks and how tasks move between workflow steps.

Default workflow

The default workflow moves a task through these steps: Draft > Waiting for publisher > Published. While the task is in either of the first two steps, you can discard it at any point. In the task listing, such tasks have the status In progress.

The following diagram shows the workflow steps (circles) and transitions (arrows).

Workflow schema
Published (start)

The initial state. From here, you begin making changes to data, which creates a task.

Draft

Data has been created or edited. From this step, depending on your permissions, you can move the task to a publisher, publish it directly, or discard it.

Waiting for publisher

Changes await review by a team member with publishing permissions. The reviewer can publish the changes, return the task to Draft for additional edits, or discard the task.

Published (end)

Changes are propagated to the MDM Server and the updated records are ready to use. The task is resolved.

Discarded

Changes are rejected without being published. The task is resolved.

The steps Draft and Waiting for publisher in the default workflow can be customized to meet project requirements. See Configuring Workflows.

Next steps

  • Access Tasks: Find the tasks assigned to you, pick up new ones, and open a task.

  • Work with Drafts: Make changes in a task and manage its draft.

  • Resolve Tasks: Move a task through the workflow and publish or discard it.

Was this page useful?