Processing Sequence
The Processing Sequence Processing Directive executes the Processing Sequence specified for the item. In this way, one Processing Sequence can execute another Processing Sequence.
Note: While LANSA Composer imposes no inherent limit on the level of nesting of Processing Sequences that can be achieved in this way, it is strongly recommended that you do not nest Processing Sequences to a depth greater than two or three.
The LANSA run-time environment used by LANSA Composer does limit the degree of nesting either within a single Processing Sequence and/or when nesting Processing Sequences. In any event, excessive degrees of nesting may adversely impact the performance of your business process integration solutions.
You can identify the specific Processing Sequence that is to be executed. Usually you do this by dragging items from the tab directly into the Processing Sequence. However, you may also change the Processing Sequence for an existing Processing Sequence item by dragging an item from the tab into the detailer window for the item.
If you wish, you can specify a variable name whose value will be used at run-time to determine the Processing Sequence to execute. If you specify the Variable for Processing Sequence, it will override the specific Processing Sequence identified above it. (However, you may still wish to provide a specific Processing Sequence to be used as a model to allow you to enter parameter values for the Processing Sequence).
The tab of the detailer window identifies the Processing Sequence that is specified for this item and, optionally, the name of the variable that will contain the Processing Sequence name or identity at run-time..
The tab of the detailer window shows the parameters received or returned by the Processing Sequence.
Note: When the nested Processing Sequence runs, it has its own independent variable pool. Variables in the containing Processing Sequence are not accessible to the nested Processing Sequence, nor vice-versa. Communication of variables is only possible through the Processing Sequence parameters.
|
* |
An asterisk in the second column denotes an inbound parameter that is flagged as being required. This means that a variable or value must be specified for it if its value has not already been set by a preceding Directive such as an Assign or an Activity. |
|
Inbound |
The second column of the list shows whether the associated parameter is inbound (received by the Processing Sequence), outbound (returned by the Processing Sequence) or both. |
| Variable or value for parameter |
Optional. Specifies the name of a variable or a numeric or alphanumeric literal that is to be used for the parameter. Refer to 3.1.1 Activities and Transformation Maps for more information on specifying values for Processing Sequence parameters, |
|
Parameter Name |
These columns show the parameter names and parameter descriptions as specified in the Processing Sequence definition. The parameter names shown are added to the variable pool for the Processing Sequence for use in this and other Processing Sequence items. |