Artifact shapes are used to indicate data flow patterns.
The following Artifact shapes are included in the Toolbox:
Data
This Artifact shape allows you to indicate how data payload is passed into the workflow from outside and transferred between the workflow steps..
The following diagram shows several use cases
Data artifact can be used as data entry point. In this case it is necessary to provide file mask.
In the run window during the test, you will be able to select the file name to be used.
The default location for the files at run time is tpe/data/msgcenter/cmw/in
If the workflow is bundle-based (this is a flag in the property sheet of begin shape) - then data file should be delivered to the incoming folder of eagle_ml-2-0_default_cm_ndfa stream.
Another use case is to indicate how data should be moved from one shape to another. In most cases, adjacent shapes do not have to be connected by data artifact, but such connection is absolutely necessary if you want to pass data to a distant shape, or to multiple shapes at once.
EJM Task Response
EJM Task Response artifact can only be used to pass the execution result message (Task Status Response, a.k.a. RTR) from one step to another.
The latter step is responsible for parsing the XML Format and extracting necessary information from it.
EJM Run Task
EJM Run task can be used similarly to previously described EJM Task Response, but it is only available in the workflows, built with deprecated "MC stream cascading" framework.
You can check what framework your workflow is based on, by opening properties window from solution's context menu
0 Comments