Ataccama ONE Agentic ONE Desktop ONE DQ&C ONE MDM ONE RDM ONE Runtime Server
latest (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

MDM Workflow Tasks

The following workflow tasks are available in MDM:

  • Run MDM Export

  • Run MDM Load

  • Run MDM Multi Load

For more information about how to use workflow tasks, see Workflow Basics and Workflow Tutorials. To use variables set by a task in subsequent tasks, see Using task variables.

Run MDM export

Starts an MDM export operation. See Input and Output Interfaces > Adding an Export Operation section in the documentation.

Properties

Name Type Description Expression support

Operation name

mandatory

ID of the operation to be invoked. Workflow fails to load if the operation is not known.

semi-expression

Parameters

optional

See Common parameters properties.

dynamic

 
<EwfTaskElement>
    <acceptMode>ALL_VALID</acceptMode>
    <executable operationName="full_instance_crm_export" class="com.ataccama.nme.ext.workflow.RunNmeBatchExport">
        <parameters/>
    </executable>
    <id>031_BatchExport</id>
    <name>Perform full instance batch export (CRM system data only)</name>
    <priority>0</priority>
</EwfTaskElement>

Common parameters properties

  • parameters - A list of name (constant)-value (semi-expression) pairs that are passed to batch operations. These can be used as component parameters, path variable definitions, or elements in more complex parameter definitions.

Name Type Description Expression support

Name

mandatory

Name of the parameter as defined in the plan (for example, path_to_file, DATA).

none

Value

mandatory

Value of the parameter (for example, real path: /mnt/data).

semi-expression

 
<parameters>
    <p name="etc_pv" value="${etcFolder}" />
    <p name="parameter" value="${paramValue}" />
    <p name="referenceTransactionId" value="${ref_tid}" />
    <p name="string_constant" value="\'INCR\'" />
    <p name="integer_constant" value="1" />
</parameters>
The referenceTransactionId parameter can be used only for export. It enables starting the export from a particular transaction ID.

Predefined variables

  • taskId: ID of the MDM task started by this step, as shown in the MDM Web App Admin Center. The variable is set when the export finishes, including when it fails or is canceled.

Logging

The step redirects logging of the MDM plan to the log file located in the workflow resources directory (as specified in the server configuration).

For each workflow instance, there is a directory in Files > storage > resources > workflow named wfinst_<instance_id>/task_<#>.log. This directory and logging file are created only if there is some content in the log file.

Run MDM load

Starts a batch load for a connected system. See Input and Output Interfaces > Adding a Batch Load Operation section in the documentation.

Properties

Name Type Description Expression support

Operation name

mandatory

ID of the operation to be invoked. Workflow fails to load if the operation is not known.

semi-expression

Parameters

optional

See the following sections.

dynamic

Predefined variables

  • taskId: ID of the MDM task started by this step, as shown in the MDM Web App Admin Center. The variable is set when the load finishes, including when it fails or is canceled.

  • transactionId: ID of the batch transaction created by the load.

Example

Sample
<executable class="com.ataccama.nme.ext.workflow.RunNmeBatchLoad">
    <operationName>full_load_s2_par</operationName>
    <parameters>
        <p name="etc_pv" value="${etcFolder}" />
    </parameters>
</executable>

Logging

The step redirects logging of the MDM plan to the log file located in the workflow resources directory (as specified in the server configuration). For each workflow instance, there is a directory in Files > storage > resources > workflow named wfinst_<instance_id>/task_<#>.log. This directory and logging file are created only if there is some content in the log file.

Run MDM multi load

Starts a batch load for one or more connected systems. Grouping of multiple batch operations can increase processing throughput.

Properties

Name Type Description Expression support

Operation names

mandatory

ID of the operation to be invoked. Workflow fails to load if the operation is not known.

semi-expression

Parameters

optional

See the following sections.

dynamic

Predefined variables

  • taskId: ID of the MDM task started by this step, as shown in the MDM Web App Admin Center. All operations listed in Operation names run in this one task. The variable is set when the multi load finishes, including when it fails or is canceled.

  • transactionId: ID of the batch transaction created by the multi load.

Example

Sample
<executable class="com.ataccama.nme.ext.workflow.RunNmeMultiLoad">
    <operationNames>delta_load,full_load_s2</operationNames>
    <parameters/>
</executable>

Logging

The step redirects logging of the MDM plan to the log file located in the workflow resources directory (as specified in the server config). For each workflow instance, there is a directory in Files > storage > resources > workflow named wfinst_<instance_id>/task_<#>.log. This directory and logging file are created only if there is some content in the log file.

Maintenance tasks

Lookup Refresh

This task reloads the "virtual filesystem" for lookups (lookup refresh), including service restart. This task has no parameters or output variables.

<executable class="com.ataccama.adt.dqc.tasks.EwfReloadVfsTask">
</executable>

It functions exactly the same way as with the online server. See Versioned File System Component.

Was this page useful?