tDataStewardshipTaskInput Standard properties

Data Stewardship

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

These properties are used to configure the tDataStewardshipTaskInput component which runs in the Standard Job framework.

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

The component in this framework is available in any subscription-based Talend solution.

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. The schema is either Built-In or stored remotely in the Repository.

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 anARBITRATION 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_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/.

Username and Password

Enter the authentication information to the Talend Data Stewardship server.

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.

Campaign

Click Find a campaign to open a list of all the campaigns available on the server, and select the campaign from which to delete the tasks.

Label

A read-only field which shows the campaign name once the campaign is selected.

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 list the state of the tasks you want to retrieve.

Assignee: Select the campaign participant whose tasks you want to retrieve. Otherwise, select No Assignee to retrieve the tasks per the search criteria without taking any assignee into account.

Otherwise, select Custom and 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. Otherwise, select Custom and 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 records in the campaign.

Tags (optional): Enter the tag(s) to associate with the tasks. You can use the tag(s) to filter the tasks you want to retrieve.

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.. For example: to filter tasks by assignee and first name value when having a FirstName field in the record, use user@company.com in the Assignee field and record.firstName='John' 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

Retrieve golden record only

Select this check box 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

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

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

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 is usually used as a start component of a Job or Subjob and it always needs an output link.