tDataStewardshipTaskDelete Standard properties - 7.1

Data Stewardship

author
Talend Documentation Team
EnrichVersion
Cloud
7.1
EnrichProdName
Talend Big Data
Talend Big Data Platform
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Real-Time Big Data Platform
task
Data Governance > Third-party systems > Data Stewardship components
Data Quality and Preparation > Third-party systems > Data Stewardship components
Design and Development > Third-party systems > Data Stewardship components
EnrichPlatform
Talend Data Stewardship
Talend Studio

These properties are used to configure the tDataStewardshipTaskOutput component when it runs in the Standard Job framework

The Standard tDataStewardshipTaskDelete component belongs to the Talend Data Stewardship family.

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

Basic settings

Property Type

Either Built-in or Repository.

 

Built-In: You create and store the schema locally for this component only. Related topic: see Talend Studio User Guide.

 

Repository: You have already created the schema and stored it in the Repository. You can reuse it in various projects and Job designs. Related topic: see Talend Studio User Guide.

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.

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

  • TDS_STATE : current state of the task.

  • TDS_ASSIGNEE : task assignee.

  • TDS_CREATION : task creation date.

  • TDS_LAST_UPDATE: task last update date.

  • TDS_LAST_UPDATED_BY : identifier of the user who last updated the task.

  • TDS_PRIORITY: numeric value which represents the priority level of the task in the web application. Each numeric value is retrieved from a text value as below:

    • Very Low = 0

    • Low = 1

    • Medium = 2

    • High = 3

    • Very High = 3

    The No Priority is set by default to Medium = 2.

  • TDS_TAGS: the tag(s) assigned to the task retrieved as a list of comma-separated values.

  • TDS_ARBITRATION: (Available only when an ARBITRATION campaign is selected) the choice assigned to the task in enumeration values.

  • TDS_ARBITRATION_LABEL: (Available only when anARBITRATION or a GROUPING campaign is selected) the choice assigned to the task as displayed in Talend Data Stewardship.

  • TDS_MASTER: (Available only when a MERGING campaign is selected) indicator to whether the record is a master record.

  • TDS_SOURCE: (Available only when a MERGING campaign is selected) name of the source of the record.

  • TDS_SCORE: (Available only when a GROUPING or a MERGING campaign is selected) the calculated distance between the input and the master record according to the matching algorithm.

  • TDS_RATING: (Available only when a MERGING campaign is selected) provides the trust score per source record you set 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.

  • TDS_EXTERNAL_ID: helps you set an Identifier of your choice on tasks so that you can retrieve them easily from any other system such as Talend MDM Web UI.

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 one of the following addresses to access the application:

  • https://tds.us.cloud.talend.com/data-stewardship for the US data center.
  • https://tds.eu.cloud.talend.com/data-stewardship for the EU data center.
  • https://tds.ap.cloud.talend.com/data-stewardship for the Asia-Pacific data center.

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, and then in the pop-up dialog box enter the password between double quotes and click OK to save the settings.

If you are working with Talend Cloud Data Stewardship and if:
  • MFA ( Multi Factor Authentication) is enabled, enter an access token in the field.
  • MFA is not enabled but SSO (Single Sign-On) is configured, enter either an access token or your password in the field.

    It is recommend to use tokens as passwords will soon be obsolete and disappear.

  • MFA is not enabled and SSO is not configured, enter either an access token or your password in the field.

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. This check box is selected by default with the RESOLUTION campaigns. However, this check box should be selected for all campaign types to guarantee smooth processing of data.

State and Assignee

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

Any State deletes all tasks whatever is their state, while Custom enables you to specify different states of the tasks to be deleted, separated by commas, for example "New,To Validate".

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 further information about the language used to query and filter data on the Talend Data Stewardship server, see The query language used with Talend Data Stewardship components.

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.

Advanced settings

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.

tStatCatcher Statistics

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

Global variables

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

Usage Rule

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