# tDSInput / tDataStewardshipTaskInput Connects to Qlik Talend Data Integration or Talend Data Stewardship and retrieves the data stored in campaigns in the form of tasks. 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). tDSInput retrieves tasks according to certain search criteria. All retrieved tasks must belong to the same sprint/campaign and must have the same schema. You can then process this data and/or write it into target applications or systems. You can set proxy settings to connect to Talend Data Stewardship by using the tSetProxy component. 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 tDSInput and tDataStewardshipTaskInput components which run in the Standard Job framework. The Standard tDSInput and tDataStewardshipTaskInput components belong to the Data Stewardship family. The component in this framework is available in all subscription-based Talend products. ## Basic settings to retrieve data from a Qlik Talend Data Integration sprint | Properties | Description | | --- | --- | | Cloud | Select Qlik Data Stewardship and click
Apply. | | Property Type | Either Built-in or Repository.


Built-In: You create and store the schema locally for this component
only.


Repository: You have already created the schema and stored it in the
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
(columns) to be processed and passed on to the next component. When you create a Spark
Job, avoid the reserved word line when naming the
fields.

Click Edit
schema to make changes to the schema. If the current schema is of the Repository type, three options are available:



The columns below are automatically added to the schema of this component and
are read-only. They give the task metadata:

| | URL | Enter the address of your Qlik Cloud
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
which you want to retrieve the data. | | States | Select from the list the states in the workflow at which you want to retrieve
the tasks.

This list displays the names of all the states you define in the sprint
workflow. It shows the initial and final states and any validation state you
add when creating the sprint in Qlik Talend Data Integration. | | Assignee | Select the sprint participant whose tasks you want to retrieve.


No Assignee retrieves the tasks which are
not assigned to any data steward, while Any Assignee
retrieves the tasks without taking any assignee into account. | | Priority (optional) | Select any of the priorities. Otherwise, select Custom and set a custom expression in the
Custom field that is displayed.

If no
level is selected, Medium is used by
default. | | Tags (optional) | Enter the tags to associate with the tasks you want to retrieve.
You can use the tags to filter the tasks. | ## Advanced settings to retrieve data from a Qlik Talend Data Integration sprint | Properties | Description | | --- | --- | | tStatCatcher Statistics | Select this checkbox to gather the Job processing metadata at the Job level
as well as at each component level. | | Maximum number of retries | Set the number of request retries before throwing a timeout exception and
killing the Job. | | Batch Size | Set the number of lines you want to have in each processed
batch.

Do not change the default value unless you are facing performance
issues. Increasing the batch size can improve the performance but setting a too
high value could cause Job failures. | ## Basic settings to retrieve data from Talend Data Stewardship | Properties | Description | | --- | --- | | Cloud | Select Talend Data Stewardship and click
Apply. | | Property Type | Either Built-in or Repository.


Built-In: You create and store the schema locally for this component
only.


Repository: You have already created the schema and stored it in the
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
(columns) to be processed and passed on to the next component. When you create a Spark
Job, avoid the reserved word line when naming the
fields.

Click Edit
schema to make changes to the schema. If the current schema is of the Repository type, three options are available:



The columns below are automatically added to the schema of this
component and are read-only. They give the task metadata.

| | URL | Enter the address to access the Talend Data Stewardship server suffixed with
*/data-stewardship/*, for example
http://<server\_address>:19999/data-stewardship/.

If you are working with Talend Cloud Data Stewardship, use the URL for the
corresponding data center suffixed with */data-stewardship/* to access the
application, for example, https://tds.us.cloud.talend.com/data-stewardship for the AWS US
data center.

For the URLs of available data
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.

To enter the password, click the [...] button
next to the password field, enter the password in double quotes in the pop-up dialog box,
and click OK to save the settings.

If you are working with Talend Cloud Data Stewardship and if:

| | Campaign | Click Find a
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
informative read-only field. | | Type | A read-only list which shows the campaign type out of the
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
the schema is performed. | | State | Select from the list the state in the workflow at which you want to retrieve
the tasks.

This list displays the names of all the states you define in the campaign
workflow. It shows the initial and final states and any validation state you
add when creating the campaign in Talend Data Stewardship.

Use the Any State option to retrieve all tasks whatever
is their state.

Use the Custom option to specify different states of the
tasks to be retrieved separated by commas, for example
"New,toValidate1,Resolved". You must enter the exact
label of the state you define in the workflow. | | Assignee | Select the campaign participant whose tasks you want to retrieve.


No Assignee retrieves the tasks which are not assigned
to any data steward, while Any Assignee retrieves the
tasks without taking any assignee into account.


Custom enables you to assign tasks dynamically to the
data stewards part of the campaign by defining context variables in the field
which is displayed. The expected value is the steward's login.

You can use this option to assign the tasks to specific stewards based on a
given attribute of the incoming data. For example, you can assign French
customers to Jacques Bocuse, a French steward, and US customers to Cale
Carolina, a US steward, or assign them based on the customer support level
Platinum for the support team lead and Gold for experts. | | Priority, Choice and
Tags | Priority (optional): Select any of the task priorities.
Otherwise, select Custom and set a custom expression in
the field that appears.

If no level is selected, Any Priority retrieves all
tasks whatever is their priority.


Choice (optional, available only when an
ARBITRATION campaign is selected): Select any of the
choice options set on the records in the campaign.


No Choice retrieves the tasks for which no choice has
been selected by data stewards, while Any Choice
retrieves all tasks whatever is the selected choice.


Tags (optional): Enter the tag(s) to associate with the
tasks you want to retrieve. You can use the tag(s) to filter the tasks. | | Query | Enter the query statement you want to use to filter the tasks to retrieve from
the campaign.

The condition is composed of a field name, an operator and a value. When
referencing record data, the name of the field must be prefixed by
record.. You should use simple quotes around strings, and
precede quotes within the string with a backslash. For example: to filter tasks
by assignee and first name value when having a *FirstName* field in the
record, use assignee='user1@talend.com' in the
Assignee field and
record.firstName='De\'wayne' in the
Query field.

For more information, see [The query
language used with data stewardship components and the REST API](https://help.qlik.com/talend/r/en-US/7.3/data-stewardship-user-guide/tql-with-tds-components-api). | | Retrieve golden record only | Select this checkbox to read only the golden records which are the results of
the merging process.

This option is available only with the MERGING campaigns
and is selected by default. | ## Advanced settings to retrieve data from Talend Data Stewardship | Properties | Description | | --- | --- | | Campaign ID | Displays the technical name of the campaign once it is selected
in the basic settings. However, you can modify the field value to replace it with a
context parameter for example and pass context variables to the Job at runtime. This
technical name is always used to identify a campaign when the Job communicates with
Talend Data Stewardship whatever is the value in the Campaign
field. | | HTTP client configuration | Connect Timeout: Set the time in milliseconds (ms) you
want to wait before the connection attempt fails and the Job is killed.


Request Timeout: Set the time in milliseconds (ms) you
want to wait before the request attempt fails and the Job is killed.

The value 0 is interpreted as infinite waiting time. | | Use ID based pagination | This option improves performances when fetching tasks by relying on the last
task ID of a batch to fetch the next one. | | Batch Size | Set the number of lines you want to have in each processed batch.

Do not change the default value unless you are facing performance issues.
Increasing the batch size can improve the performance but setting a too high
value could cause Job failures. | | Consume tasks when they are read | This checkbox is selected by default to mark tasks as consumed on the
Talend Data Stewardship
server once they are retrieved by the component. These tasks will
not be retrieved a second time when you rerun the Job with the same filter
criteria.

Make sure to clear this checkbox only for very specific use cases, otherwise
there is a very high risk of processing twice the same tasks.

Information noteNote: This option
only applies to resolved tasks. | | Max request attempts | Set the number of request attempts before throwing a timeout exception and
killing the Job. | | tStatCatcher Statistics | Select this checkbox to gather the Job processing metadata at the Job level
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
integer. | | NB\_REJECT | The number of rows rejected. This is an After variable and it returns an
integer. | | NB\_SUCCESS | The number of rows successfully processed. This is an After variable and it returns
an integer. | | ERROR\_MESSAGE | The error message generated by the component when an error occurs. This is an
After variable and it returns a string. This variable functions only if the Die on error checkbox is cleared, if the component has this
checkbox. | ## Usage | Usage guidance | Description | | --- | --- | | Usage Rule | This component is usually used as a start component of a Job or
subJob and it always needs an output link. | **Related concepts** * [Retrieving tasks from Talend Data Stewardship](https://help.qlik.com/talend/en-US/components/8.0/data-stewardship/tdatastewardshiptaskinput-tlogrow-retrieving-tasks-from-talend-data-stewardship-standard-component-enterprise "This Job reads the tasks stored in Talend Data Stewardship according to the criteria you define in the basic settings of the tDataStewardshipTaskInput component.")