Skip to main content Skip to complementary content

Creating a Job to retrieve stewardship tasks

Create a Job to connect to Talend Data Stewardship, retrieve tasks and their metadata from a number of campaigns and list them on the Studio log console. You can use this Job with any Talend output component to write the retrieved tasks in a target application or system.

To replicate the example described below, retrieve the tdatastewardshiptaskinput_read_tasks.zip file from the Downloads tab in the left pane of this help page.

To replicate the example described below, retrieve the tdatastewardshiptaskinput_read_tasks.zip file from the Downloads tab of the online version of this page at https://help.talend.com.

The campaigns used in this example are:
  • An Arbitration campaign, Beta Candidates, which stores the tasks of the candidates for a beta testing program,

  • A Resolution campaign, Product Catalog, which stores the tasks of the enterprise products,

  • A Merging campaign, CRM Data Deduplication, which stores the tasks of customer data retrieved from the enterprise CRM system.

  • A campaign, Matching on Spark, which stores the tasks of the enterprise products retrieved from the enterprise product catalog.

Before you begin

  • The campaigns from which you want to retrieve the tasks are already defined in Talend Data Stewardship and populated with tasks.

  • You have been assigned the Campaign Owner role which grants you access to the campaigns.

Procedure

  1. In the design workspace, start typing tDataStewardshipTaskInput and select this component from the list that opens. Repeat the operation to add three tDataStewardshipTaskInput components in the workspace.
  2. Do the same to add three tLogRow components to the workspace.
  3. Link the tDataStewardshipTaskInput components to the tLogRow components using the Row > Main links.
  4. Link the tDataStewardshipTaskInput components together using the Trigger > OnSubjobOk links.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!