You might decide to run a mapping from a workflow so that you can make decisions during the workflow run. You can configure a workflow to run multiple mappings in sequence or in parallel. You can configure a workflow to send emails that notify users about the status of the Mapping tasks.
If you add a mapping to a workflow that runs on the Spark engine, you can also configure mapping outputs. You can persist a mapping output in the Model repository to assign the persisted output to a Mapping task input, or you can bind a mapping output to a workflow variable to pass the value of the output to other tasks in the workflow.
You cannot use the SUM aggregation type in mapping outputs on the Spark engine.
For more information about mapping outputs, see the "Mapping Task" chapter in the
Developer Workflow Guide
When a Mapping task runs a mapping configured to run on the Blaze engine, do not assign the Mapping task outputs to workflow variables. Mappings that run on the Blaze engine do not provide the total number of target, source, and error rows. When a Mapping task includes a mapping that runs on the Blaze engine, the task outputs contain a value of zero (0).