tDataStewardshipTaskInput Standard properties

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.

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, and then in the pop-up dialog box enter the password between double quotes 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 check box 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. This check box is selected by default for all campaign types to guarantee smooth processing of data.

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.

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 (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.

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.

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.

This option is only available with Talend Cloud Data Stewardship.

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.

This check box 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.

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.