Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This Artifact shape allows you to indicate the start of parallel processing of the workflows.
The Name property of this shape defaults to Fork.how data payload is passed into the workflow from outside and transferred between the workflow steps..
The following diagram shows several use cases

Image Added

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. 


Anchor
artifact_tsr
artifact_tsr
EJM Task Response

This Gateway shape allows you to indicate that waiting is required until parallel workflows complete before proceeding to the next action.
The Name property of this shape defaults to Join.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.

Image Added

Anchor
artifact_rtr
artifact_rtr
EJM Run Task

This Gateway shape allows you to determine what the next step is based on a specific condition being true or false.
The following table describes the shape's properties.

...

  1. The branches of the Decision shape should not converge later, but should represent independent execution paths leading to the ‘end’ shape.

The example of a WRONG scenario below merges the two branches into one shape :

Image Removed

The CORRECT way to do this is to duplicate the second decision shape, as shown in the next picture:

Image Removed

      2. Neither branch of the Decision shape should lead directly to the “End” shape. For such scenario it is better to use “Condition To Execute” property of the shape, and get rid of the Decision shape altogether.

WRONG:

Image Removed

CORRECT:

Image RemovedEJM 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

Image Added