You can configure mapping outputs for standalone mappings or mappings that are a part of a workflow. You can bind persisted mapping outputs to use them in subsequent runs of the mapping or workflow.
Standalone Deployed Mappings
You can persist a mapping output in the Model repository for mappings that run in the native environment or on the Spark engine. You can bind a mapping output to a mapping parameter to pass the value of the output to the mapping the next time you run the mapping.
For more information about mapping outputs in standalone mappings, see the "Mapping Outputs" chapter in the
Developer Mapping Guide
Mapping Tasks in Workflows
If you add a mapping to a workflow that runs on the Spark engine, you can 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.
When a Mapping task runs a mapping configured to run on the Blaze engine, do not bind 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).
For more information about mapping outputs in workflow Mapping tasks, see the "Mapping Task" chapter in the