tDSOutput / tDataStewardshipTaskOutput

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.

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:

• View schema: choose this option to view the schema only.

• Change to built-in property: choose this option to change the schema to Built-in for local changes.

• Update repository connection: choose this option to change the schema stored in the repository and decide whether to propagate the changes to all the Jobs upon completion.

  If you just want to propagate the changes to the current Job, you can select No upon completion and choose this schema metadata again in the Repository Content window.

Once you select a sprint from the Sprint list, tDSOutput becomes aware of the schema defined in the campaign and creates identical schema columns in its basic settings.

Enter the address of your Qlik Cloud tenant, for example https://qcs.us.qlikcloud.com/.

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

Select the sprint participant whose tasks you want to create. Otherwise, select No assignee to create the tasks without assigning them to anybody.

Select this checkbox to gather the Job processing metadata at the Job level as well as at each component level.

Set the number of request retries before throwing a timeout exception and killing the Job.

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.

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:

• View schema: choose this option to view the schema only.

• Change to built-in property: choose this option to change the schema to Built-in for local changes.

• Update repository connection: choose this option to change the schema stored in the repository and decide whether to propagate the changes to all the Jobs upon completion.

  If you just want to propagate the changes to the current Job, you can select No upon completion and choose this schema metadata again in the Repository Content window.

In case you select to write the tasks in a MERGING or a GROUPING campaign, the below columns are automatically added to the schema:

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

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.

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.

A read-only list which shows the campaign type out of the predefined types once the campaign is selected.

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.

Select from the list the state in the workflow at which you want to create 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 Custom option if you want to contextualize values in order to define different states depending on different values. For example, you can assign the "New" value to the State field if you want all incoming fields to be checked, and assign the "To validate" value to the same field if you are confident with incoming values and just want them to be validated.

Select the campaign participant whose tasks you want to create. Otherwise, select No Assignee to create the tasks without assigning them to anybody.

The Custom option allows 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 (optional): Select any of the task priorities. Otherwise, select Custom and set a custom expression in the field which is displayed.

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

Choice (optional, available only when an ARBITRATION campaign is selected): Select any of the choice options set on the records while defining the campaign in the web application. The default value is No Choice, this enables data stewards to do the work in the web application. However, setting an arbitration choice in the Job is a way to help the steward by pre-selecting the supposedly most relevant choice directly when creating the tasks.

Tags (optional): Enter the tag to associate with the tasks you want to create.

You can use the tag(s) to filter the tasks you want to load into the campaign.

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.

Set the number of the tasks you want to have in each commit.

There are no limits for the batch size in Talend Data Stewardship (on premises).

However, you need to make sure not to exceed 200 tasks per commit in Talend Cloud Data Stewardship, setting higher values causes Job failure.

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.

The number of messages processed. This is an After variable and it returns an integer.

The number of rows rejected. This is an After variable and it returns an integer.

The number of rows successfully processed. This is an After variable and it returns an integer.