The query language used with Talend Data Stewardship components - 7.1

author
Talend Documentation Team
EnrichVersion
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

The query language used with Talend Data Stewardship components

You can use a query language with the tDataStewardshipTaskDelete and tDataStewardshipTaskInput components to query and filter the data you want to delete or read from Talend Data Stewardship.

The query statement used to filter tasks on the server is composed of one or several conditions. You can combine or negate conditions using the boolean operators and and or, or the not operator respectively. Parenthesis are supported to override default boolean precedence.

A task condition is composed of a field name, an operator and a value. You should use simple quotes around strings, and precede quotes within the string with a backslash.

Supported metadata fields on tasks are:

Metadata field

Description

id (string)

Task internal identifier

externalID (string)

Task external identifier which helps to access a given task from an external system

currentState (string)

Current state of the task in the campaign workflow

assignee (string)

userId of the data steward currently assigned to this task

targetTransition (string)

Name of the transition chosen by user to move the task to the next step in the campaign workflow

completed (boolean)

true if the task is completed (it is in a final state of the workflow)

priority (integer)

Priority level of the task, ranging from 0 (Very Low) to 4 (Very High), default is 2 (Medium)

dueDate

Timestamp in milliseconds of the task due date

matchScore (only for Merging and Grouping campaigns)

Decimal value which shows the highest match score of each group in the source data

version (integer)

Integer value of the task version which is incremented whenever the task is updated

consumed (boolean)

true if the task has already been processed (so it cannot be processed anymore - unless it is reopened)

createdBy (string)

userId of the task creator

creationDate (long)

Timestamp in milliseconds of this task creation date

lastUpdatedBy (string)

userId of the data steward who did the last update on the task

lastUpdateDate (long)

Timestamp in milliseconds of the last update done on the task

tags (string)

List of tags entered by the user for this task

arbitration (only for Arbitration and Grouping campaigns)

Arbitration choice selected by the data steward

When referencing records data, the name of the field must be prefixed by record.. Simple binary operators are =, <, >, <=, >= and !=. The third part of the condition can be any literal value. Use simple quotes around strings, and precede quotes within the string with a backslash.

To filter tasks by assignee and have a record field firstname equal to John: assignee='user1@talend.com' and record.firstName='John'

To filter tasks by assignee and have a record field firstname equal to De'wayne: assignee='user2@talend.com' and record.firstName='De\'wayne'

To filter tasks created after 2016-01-01: creationDate > 1451659712733.