A Human task reads the output of a mapping that contains an Exception transformation. An Exception transformation analyzes output from other transformations to validate the data quality status of the records in a data set. A mapping developer uses the Exception transformation to identify records that need manual processing.
The Exception transformation writes records to one or more database tables based on the data quality status of each record. The transformation specifies a table as a target for records with an unverified data quality status. The objective of the user in a Human task is to verify the data quality status of the records in the table.
When the mapping developer completes the mapping that contains the Exception transformation, a workflow developer adds the mapping to a Mapping task in a workflow. When you add a Human task to the workflow, you configure the Human task to read the database table created when the Mapping task runs. The users who perform the Human task examine the records and makes any change required.
The users then update the status of the records in one of the following ways:
If a record is valid, the user updates the table metadata so that the record is confirmed for persistent storage in the database.
If a record is not valid, the user updates the table metadata so that the record is removed from the database at a later stage in the workflow.
If the status of a record cannot be confirmed, the user updates the table metadata so that the record is returned to the workflow for further processing in a Mapping task.