Writing tasks into a Merging campaign - 6.5

Data Stewardship

Talend Big Data
Talend Big Data Platform
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Real-Time Big Data Platform
Talend Data Stewardship
Talend Studio
Data Governance > Third-party systems > Data Stewardship components
Data Quality and Preparation > Third-party systems > Data Stewardship components
Design and Development > Third-party systems > Data Stewardship components
Configure the tDataStewardshipTaskOnput component to load the groups of similar records into the CRM Data Deduplication campaign which is already defined on the Talend Data Stewardship server and which has the same schema as the data in the input file.


  1. Double-click the tDataStewardshipTaskOutput component to open its Basic settings view.
  2. In the URL field, enter the address of the application suffixed with /data-stewardship/, for example http://localhost:19999/data-stewardship/.

    In this example, all connection information is defined as context parameters and centralized in the Studio repository. For further information about context parameters, see Talend Studio User Guide.

  3. Enter your login information to the server in the Username and Password fields.
    To enter your password, click the [...] button next to the Password field, enter your password between double quotes in the dialog box that opens and click OK.
  4. Click Find a campaign to open a dialog box which lists the campaigns defined in Talend Data Stewardship and for which you are the owner or you have the access rights.
  5. Click the column header to sort the list alphabetically for text columns and chronologically for the date column. Select the campaign in which to write the arbitration tasks, CRM Data Deduplication and click OK.

    The Campaign, Label and Type fields are automatically filled in with the campaign metadata.

    The schema of the selected campaign is retrieved from the server and is read-only. Two columns are added by default:
    • TDS_DUE_DATE which provides the task due date using the format: YYYY-MM-DD HH:mm:ss. The due date is automatically calculated according to the task resolution delay you define in the campaign, if any.
    • TDS_EXTERNAL_ID which you can use to provide the task identifier you define in the Job.
    • TDS_GID which is used to group records in tasks. All source records that should be grouped in a single task must have the same TDS_GID.
    • TDS_MASTER which indicates if the record is a master or a source record.

      If no source is set as master for a given task, Talend Data Stewardship determines which attributes of matched records to use to create the master record according to the survivorship rules you define when creating the campaign.

      You can click Edit Schema to display the schema, if needed.

      The output schema of tDataStewardshipTaskOutput always uses the String type for all the columns regardless of the initial data types, except the ones generated by default.

  6. Select the Override enforcement of data model check box to load the new tasks even if their schema type does not match what has been defined on the Talend Data Stewardship server.
  7. Set the metadata of the tasks you want to write in the Merging campaign as follows:
    • From the State list, select to write the tasks and assign them the New status.

    • From the Assignee list, select No Assignee to write the tasks in the campaign pending to be assigned to the campaign participants.

    • Don't change the by-default value in the Priority list.

      If no priority level is selected, Medium is used by default.

  8. In the Tag field, enter the tag or tags you want to associate with the tasks, use a comma to separate multiple tags.
    You can use the tag(s) to filter the tasks you want to load into the campaign.
  9. In the Comments table, enter a comment for one or more columns, if needed.