tDataStewardshipTaskDelete Standard properties

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:

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

URL

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

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.

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

Select from the list the state of the tasks you want to delete.

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 Cloud Data Stewardship. This list enables you to filter the tasks by their states and delete them whether they are new or resolved, or whether they are in any of the validation states you define in the campaign workflow.

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

Use the Custom option to specify different states of the tasks to be deleted separated by commas, for example "New,toValidate1,toValidate2". You must enter the exact label of the state you define in the workflow.

Assignee

Select the campaign participant whose tasks you want to delete.

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

Custom enables you to set a custom expression in the field which is displayed to filter the tasks you want to process according to specific needs.

Priority, Choice and Tags

Priority (optional): Select any of the task priorities.

Any Priority deletes all tasks whatever is their priority, while Custom enables you to set a custom expression in the field which is displayed.

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

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

Tags (optional): Select any of the tags assigned to the tasks in the campaign.

Query

Enter the query statement you want to use to filter the tasks to process.

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 'De\'wayne' in the Query field.

For more information, see The query language used with data stewardship components and the REST API.

Delete by ID

Select this check box if you want to delete a task by providing its identifier through an input schema using the tFixedFlowInput component for example.

Input field of task ID: From the drop-down list, select the schema column that corresponds to the task identifier field. The choices available correspond to the column names provided by the input component you use in the Job with tDataStewardshipTaskDelete.

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.

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.

tStatCatcher Statistics

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

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 check box is cleared, if the component has this check box.

Usage Rule

This component can be used as a standalone component or as a start component of a Job or subJob.