# tDSOutput / tDataStewardshipTaskOutput

Connects to Qlik Talend Data Integration or Talend Data Stewardship and loads data into sprints/campaigns in the form of tasks. The tasks must have the same schema defined in the sprint/campaign.

Information noteAttention: From Talend Studio 8.0 R2025-12, the tDataStewardshipTask\* components are replaced by the tDS\* components:

* tDataStewardshipTaskInput becomes tDSInput.
* tDataStewardshipTaskOutput becomes tDSOutput.
* tDataStewardshipTaskDelete becomes tDSDelete.

These components let you connect Talend Studio to [Qlik Talend Data Integration](https://help.qlik.com/en-US/cloud-services/csh/client/qdi_stewardship_create_job) and [Talend Data Stewardship](https://help.qlik.com/talend/en-US/data-stewardship-user-guide/Cloud/talend-cloud-data-stewardship-introduction).

An authorized sprint/campaign participant can then intervene and resolve the tasks using the capabilities provided by Talend Data Stewardship.

You can set proxy settings to connect to Talend Data Stewardship by using the tSetProxy component.

Information noteNote: You can store up to 20 GB of tasks in Talend Cloud Data Stewardship per account. For more information, see [Setting the maximum amount of stored tasks](https://help.qlik.com/talend/en-US/data-stewardship-user-guide/8.0/setting-the-maximum-amount-of-stored-tasks).

This component is not shipped with your Talend Studio by default. You need to install it using the Feature Manager. For more information, see [Installing features using the Feature Manager](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/install-features-to-talend-studio).

## Standard properties

These properties are used to configure the tDSOutput and tDataStewardshipTaskOutput components which run in the Standard Job framework.

The Standard tDSOutput and tDataStewardshipTaskOutput components belong to the Data Stewardship family.

The component in this framework is available in all subscription-based Talend products.

## Basic settings to load data into a Qlik Talend Data Integration sprint

| Properties | Description |
| --- | --- |
| Cloud | Select Qlik Data Stewardship and click<br>Apply. |
| Property Type | Either Built-in or Repository.<br><br><br>Built-In: You create and store the schema locally for this component<br>only.<br><br><br>Repository: You have already created the schema and stored it in the<br>Repository. You can reuse it in various projects and Job designs. |
| Schema and Edit<br>schema | A schema is a row description. It defines the number of fields<br>(columns) to be processed and passed on to the next component. When you create a Spark<br>Job, avoid the reserved word line when naming the<br>fields.<br><br>Click Edit<br>schema to make changes to the schema. If the current schema is of the Repository type, three options are available:<br><br><ul> <li> <p> <span>View schema</span>: choose this                option to view the schema only.</p> </li> <li> <p> <span>Change to built-in property</span>:                choose this option to change the schema to <span>Built-in</span> for local changes.</p> </li> <li> <p> <span>Update repository connection</span>:                choose this option to change the schema stored in the repository and decide whether                to propagate the changes to all the Jobs upon completion.</p> <p>If you just want to                propagate the changes to the current Job, you can select <span>No</span> upon completion and choose this schema metadata                again in the <span>Repository Content</span>                window.</p> </li> </ul><br><br>Once you select a sprint from the Sprint list, tDSOutput<br>becomes aware of the schema defined in the sprint and creates identical schema<br>columns in its basic settings. |
| URL | Enter the address of your Qlik Cloud<br>tenant, for example https://qcs.us.qlikcloud.com/. |
| API key | Enter your API key. To generate one, see [Generating an API key](https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Admin/mc-generate-api-keys.htm). |
| Sprint | Click [...] and select the sprint from<br>which you want to load data. |
| Priority (optional) | Select any of the priorities. Otherwise, select Custom and set a custom expression in the<br>Custom field that is displayed.<br><br>If no<br>level is selected, Medium is used by<br>default. |
| Assignee | Select the sprint participant whose tasks you want to create. Otherwise, select<br>No assignee to create the tasks without assigning<br>them to anybody. |
| Tags (optional) | Enter the tag to associate with the tasks you want to load.<br><br>You can use the tags to filter the tasks you want to load into the<br>sprint. |

## Advanced settings to load data into a Qlik Talend Data Integration sprint

| Properties | Description |
| --- | --- |
| tStatCatcher Statistics | Select this checkbox to gather the Job processing metadata at the Job level<br>as well as at each component level. |
| Maximum number of retries | Set the number of request retries before throwing a timeout exception and<br>killing the Job. |
| Batch Size | Set the number of lines you want to have in each processed<br>batch.<br><br>Do not change the default value unless you are facing performance issues.<br>Increasing the batch size can improve the performance but setting a too high<br>value could cause Job failures. |

## Basic settings to load data into Talend Data Stewardship

| Properties | Description |
| --- | --- |
| Cloud | Select Talend Data Stewardship and click<br>Apply. |
| Property Type | Either Built-in or Repository.<br><br><br>Built-In: You create and store the schema locally for this component<br>only.<br><br><br>Repository: You have already created the schema and stored it in the<br>Repository. You can reuse it in various projects and Job designs. |
| Schema and Edit schema | A schema is a row description. It defines the number of fields<br>(columns) to be processed and passed on to the next component. When you create a Spark<br>Job, avoid the reserved word line when naming the<br>fields.<br><br>Click Edit<br>schema to make changes to the schema. If the current schema is of the Repository type, three options are available:<br><br><ul> <li> <p> <span>View schema</span>: choose this                option to view the schema only.</p> </li> <li> <p> <span>Change to built-in property</span>:                choose this option to change the schema to <span>Built-in</span> for local changes.</p> </li> <li> <p> <span>Update repository connection</span>:                choose this option to change the schema stored in the repository and decide whether                to propagate the changes to all the Jobs upon completion.</p> <p>If you just want to                propagate the changes to the current Job, you can select <span>No</span> upon completion and choose this schema metadata                again in the <span>Repository Content</span>                window.</p> </li> </ul><br><br>Once you select a campaign from the Find a campaign<br>list, tDSOutput becomes aware of the schema defined in<br>the campaign and creates identical schema columns in its basic settings. The<br>component also adds the TDS\_DUE\_DATE and<br>TDS\_EXTERNAL\_ID columns to the schema:<br><br><ul> <li> <p> <span>TDS_DUE_DATE</span>: holds the task due date using the                              format: <span>YYYY-MM-DD HH:mm:ss</span>. The due date is                              calculated automatically according to the task delay time you define                              when creating the campaign in <span>Talend Data Stewardship</span>. If you do not define a delay date for tasks when creating the                              campaign, this column stays empty. </p> </li> <li> <p> <span>TDS_EXTERNAL_ID</span>: helps you set an identifier of your                              choice on tasks so that you can retrieve them easily from any other                              system.</p> <p>If you do not define an identifier for tasks when creating the Job,                              this column stays empty. </p> </li> </ul><br><br>In case you select to write the tasks in a MERGING or a<br>GROUPING campaign, the below columns are<br>automatically added to the schema:<br><br><ul> <li> <p> <span>TDS_GID</span>: holds the group identifier.</p> <p>This identifier is used by <span>tDSOutput</span> to group                              records in tasks. All source records that should be grouped in a                              single task must have the same <span>TDS_GID</span>.</p> </li> <li> <p> <span>TDS_MASTER</span> (only for a <span>MERGING</span>                              campaign): indicates if the record is a master or a source record.</p> <div>Two cases to consider:<ul> <li>If no source record is set as master for a given task, <span>Talend Data Stewardship</span> determines which attributes of matched records to use to                                    create the master record according to the survivorship rules you                                    define when creating the campaign.<p>For more information about                                       survivorship rules, see the section about setting data models                                       in <span>Merging</span> campaigns in <a href="https://help.qlik.com/talend/en-US/data-stewardship-user-guide/8.0/talend-data-stewardship-examples" target="_blank">Talend Data Stewardship                                          Examples</a>.</p> </li> <li>If more than one source record is set as master for a given                                    task, <span>Talend Data Stewardship</span> takes the first source set as master to be the master record.                                    So the best practice is to have either 0 or one master record                                    per task.</li> </ul> </div> </li> <li> <p> <span>TDS_SOURCE</span>: holds the name of the source of the                              record, if any.</p> </li> <li> <p> <span>TDS_RATING</span> (only for a <span>MERGING</span>                              campaign): provides a trust score per source record at task creation.                              This score overrides the score you define at campaign creation, if                              any. It is an integer value, which represents a percentage between 0                              and 100.</p> </li> <li> <p> <span>TDS_SCORE</span>: provides the calculated distance between                              the input and the master records according to the matching                              algorithm.</p> </li> <li> <span>TDS_CREATION</span>: holds the task creation date.</li> <li> <span>TDS_LAST_UPDATE</span>: holds task last update date.</li> </ul> |
| URL | Enter the address to access the Talend Data Stewardship server suffixed with<br>*/data-stewardship/*, for example<br>http://&lt;server\_address&gt;:19999/data-stewardship/.<br><br>If you are working with Talend Cloud Data Stewardship, use the URL for the<br>corresponding data center suffixed with */data-stewardship/* to access the<br>application, for example, https://tds.us.cloud.talend.com/data-stewardship for the AWS US<br>data center.<br><br>For the URLs of available data<br>centers, see [Accessing Talend Cloud applications](https://help.qlik.com/talend/en-US/installation-guide-windows/Cloud/talend-cloud-application-url). |
| Username and Password | Enter the authentication information to log in to Talend Data Stewardship.<br><br>To enter the password, click the [...] button<br>next to the password field, enter the password in double quotes in the pop-up dialog box,<br>and click OK to save the settings.<br><br>If you are working with Talend Cloud Data Stewardship and if:<br><br><ul> <li>SSO is enabled, enter an access token in the field.</li> <li>SSO is not enabled, enter in the field either: <ul> <li>an access token.</li> <li>your password (deprecated).</li> </ul> </li> </ul> |
| Campaign | Click Find a<br>campaign to open a list of all the campaigns available in Talend Data Stewardship, and select the name of the campaign holding the tasks. This is an<br>informative read-only field. |
| Type | A read-only list which shows the campaign type out of the<br>predefined types once the campaign is selected. |
| Override enforcement of data model | Select this checkbox if you want to process data on the Talend Data Stewardship server even if the schema type is not valid, no input validation of<br>the schema is performed.<br><br><br>This checkbox is selected by default only for Merging and Resolution campaign<br>types. |
| State | Select from the list the state in the workflow at which you want to create the<br>tasks.<br><br>This list displays the names of all the states you define in the campaign<br>workflow. It shows the initial and final states and any validation state you<br>add when creating the campaign in Talend Data Stewardship.<br><br>Use the Custom option if you want to contextualize<br>values in order to define different states depending on different values. For<br>example, you can assign the "New" value to the State<br>field if you want all incoming fields to be checked, and assign the "To<br>validate" value to the same field if you are confident with incoming values and<br>just want them to be validated. |
| Assignee | Select the campaign participant whose tasks you want to create. Otherwise,<br>select No Assignee to create the tasks without assigning<br>them to anybody.<br><br>The Custom option allows you to assign tasks dynamically<br>to the data stewards part of the campaign by defining context variables in the<br>field which is displayed. The expected value is the steward's login.<br><br>You can use this option to assign the tasks to specific stewards based on a<br>given attribute of the incoming data. For example, you can assign French<br>customers to Jacques Bocuse, a French steward, and US customers to Cale<br>Carolina, a US steward, or assign them based on the customer support level<br>Platinum for the support team lead and Gold for experts. |
| Priority, Choice and<br>Tags | Priority (optional): Select any of the task<br>priorities. Otherwise, select Custom and set a custom<br>expression in the field which is displayed.<br><br>If no level is selected, Medium is used by default.<br><br><br>Choice (optional, available only when an<br>ARBITRATION campaign is selected): Select<br>any of the choice options set on the records while defining the campaign in the<br>web application. The default value is No<br>Choice, this enables data stewards to do the work in the web<br>application. However, setting an arbitration choice in the Job is a way to help<br>the steward by pre-selecting the supposedly most relevant choice directly when<br>creating the tasks.<br><br><br>Tags (optional): Enter the tag to associate<br>with the tasks you want to load.<br><br>You can use the tag(s) to filter the tasks you want to load into the<br>campaign. |
| Comments (optional) | Select one or several schema columns and enter the comment you want<br>to add to the tasks you want to load.<br><br>This table lists by default all the schema columns.<br><br>The campaign participant will be able to see the comment any time<br>they place the pointer on the source record column in Talend Data Stewardship. This information can help them making a more informed<br>decision when resolving the task. |

## Advanced settings to load data into Talend Data Stewardship

| Properties | Description |
| --- | --- |
| Campaign ID | Displays the technical name of the campaign once it is selected<br>in the basic settings. However, you can modify the field value to replace it with a<br>context parameter for example and pass context variables to the Job at runtime. This<br>technical name is always used to identify a campaign when the Job communicates with<br>Talend Data Stewardship whatever is the value in the Campaign<br>field. |
| Max tasks per commit | Set the number of the tasks you want to have in each commit.<br><br>There are no limits for the batch size in Talend Data Stewardship (on premises).<br><br>However, you need to make sure not to exceed 200 tasks per commit<br>in Talend Cloud Data Stewardship, setting higher values causes Job failure. |
| HTTP client configuration | Connect Timeout: Set the time in milliseconds (ms) you<br>want to wait before the connection attempt fails and the Job is killed.<br><br><br>Request Timeout: Set the time in milliseconds (ms) you<br>want to wait before the request attempt fails and the Job is killed.<br><br>The value 0 is interpreted as infinite waiting time. |
| tStatCatcher Statistics | Select this checkbox to gather the Job processing metadata at the Job level<br>as well as at each component level. |

## Global variables

| Variable | Description |
| --- | --- |
| NB\_LINE | The number of messages processed. This is an After variable and it returns an<br>integer. |
| NB\_REJECT | The number of rows rejected. This is an After variable and it returns an<br>integer. |
| NB\_SUCCESS | The number of rows successfully processed. This is an After variable and it returns<br>an integer. |
| ERROR\_MESSAGE | The error message generated by the component when an error occurs. This is an<br>After variable and it returns a string. This variable functions only if the Die on error checkbox is cleared, if the component has this<br>checkbox. |

## Usage

| Usage guidance | Description |
| --- | --- |
| Usage Rule | This component is usually used as an end component of a Job or<br>subJob and it always needs an input link. |

**Related concepts**

* [Assigning tasks dynamically in Talend Data Stewardship](https://help.qlik.com/talend/en-US/components/8.0/data-stewardship/tdatastewardshiptaskoutput-tmap-tfileinputdelimited-tfileinputdelimited-assigning-tasks-dynamically-in-talend-data-stewardship-standard-component-enterprise "When loading data to Talend Data Stewardship, it is possible to dynamically assign the tasks to specific stewards based on a given attribute of the incoming data.")
* [Populating campaigns dynamically using campaign IDs](https://help.qlik.com/talend/en-US/components/8.0/data-stewardship/tdatastewardshiptaskoutput-tmap-tmatchgroup-tfileinputdelimited-populating-campaigns-dynamically-using-campaign-ids "This Job loads tasks into campaigns defined in Talend Data Stewardship using campaign technical names. Context parameter are used to pass technical names as context variables to the Job at runtime.")
* [Populating tasks into the same campaign on different Talend Data Stewardship instances](https://help.qlik.com/talend/en-US/components/8.0/data-stewardship/tdatastewardshiptaskoutput-tmap-tmatchgroup-tfileinputdelimited-populating-tasks-into-same-campaign-on-different-talend-data-stewardship-instances "This Job loads tasks into two campaigns with the same data model on two different Talend Data Stewardship instances. Context variables are used to pass the connection information of each Talend Data Stewardship instance to the Job at runtime.")
* [Writing tasks in a Merging campaign](https://help.qlik.com/talend/en-US/components/8.0/data-stewardship/writing-tasks-merging-campaign "This Job loads tasks into a Merging campaign defined in Talend Data Stewardship according to the criteria you define in the basic settings of the tDataStewardshipTaskOutput component.")
* [Writing tasks in Talend Data Stewardship campaigns](https://help.qlik.com/talend/en-US/components/8.0/data-stewardship/tdatastewardshiptaskoutput-tfileinputdelimited-tmatchgroup-tmap-writing-tasks-in-talend-data-stewardship-campaigns-standard-component-enterprise "This Job loads tasks in different campaigns defined in Talend Data Stewardship. It loads the tasks according to the criteria you define in the basic settings of the tDataStewardshipTaskOutput components.")