Step Execution

Data Available to Step

When a step is configured it declares the data that it needs to execute. There is the ability to map data in from the flow or to provide a constant into that step. The step knows that it needs certain values in order to execute. These values can be mapped in multiple ways using different mapping editors. The mapping editors that can be used are contingent base on the type of data. If the data is, a string, a merge editor may be used. If the data is a date, an extra editor will show allowing the designer to provide a constant or compute the date.

Mapping Inputs

The data that is available to be mapped is a combination of the data that is present in the flow and where the step is connected. This data is a combination of the flow inputs and all of the data from the steps proceeding. This data can also include data that has been defined externally as system constants and lookup lists, these are different avenues that data is given in a flow.

Advanced Mapping

There is a star functionality here that has the ability to run a flow to provide inputs to steps that aren't part of the flow that you are executing, called converter flows. This step always returns right away and it can tell the flow engine to store that data so that we can later come back to it.

Store Flow Data

The step can do whatever it has been designed to do. It is a black-box component, one thing that it might do is to choose  If the step knows that it is not returning right away it can tell the flow engine that this is a point that we want to store that data so that we can later come back to it.
When the step is done executing whether that is a synchronize finish which just tells us immediately what the result is or whether it is in the future. If I asked the user to fill out a form and the user takes 20 min to fill out the form, the step tells the flow engine that it's complete and it also tells the flow engine that this is on the path that is complete and outputs data that satisfy the output requirements.

Result Path

When the step is done executing, the step tells the flow engine that it is complete and the results will show data from the completed step.  When the completed step has processed the result data the outputs of that step are then mapped back into the flow. The result output paths can be ignored, mapped or a value can be added to the step. The flow engine then finds the next step by looking around at the links between steps and following those steps. The flow engine can look for trigger components to connect pathways if that link is not connected. The flow engine will throw an exception when it does not know what to do next. When the step is done executing, the step tells the flow engine that the step is complete.

Mapping Output

When the output mapping has been done and the data has been handed back to the flow engine.

Finding the Next Component

In the flow, you can add a step that will deal with the error of an unconnected pathway. This step will output the details of the exception and give a path to connect to other steps.

Exceptions

Exceptions are dealt with by using a special step called anExceptions Trigger Step. This step looks for pathways to connect to and then gives you the options.