Rational Developer for System z

Flow nodes and invoke nodes in the generation properties editor

The generation properties editor displays in the the left pane of the editor area a hierarchical tree in which each node corresponds to and contains the generation properties for a corresponding invocation in the flow file.
The flow node is the topmost node of the hierarchical tree in the generation properties editor. The characteristics of the flow node are as follows:
In contrast, an invoke node is a descendant of the flow node in the hierarchical tree. The characteristics of an invoke node are as follows:
The following table shows how nodes in the generation properties editor correspond with nodes in the flow editor:
Table 1. Significance of a node in the hierarchical tree in the generation properties editor
Node in the hierarchical tree in the generation properties editor: Corresponding nodes in the flow editor:
Flow node
Flow node

Invocation of the flow itself -- not displayed in the flow editor.
Invoke node -- invocation of an operation
Invoke node
Invoke nonterminal node
Invoke nonterminal node
Invoke outbound Web service node
Invoke nonterminal node
Invoke screen operation node
Invoke screen operation node
Invoke node -- invocation of a flow
Invoke node
Invoke flow node
Invoke flow node
As Table 1 shows, two simplifications have been made in showing the correspondence between nodes in the generation properties editor (shown in the left column of the table) and nodes in the flow editor (shown in the right column of the table).

Despite these two simplifications as far as the use of symbols goes, nevertheless the generation properties editor does detect and is aware of all the various types of Invoke nodes as they are defined in the flow editor (see Invoke types).

The hierarchical tree in the left pane of the generation properties editor can have either two or three levels, depending on whether the corresponding flow invokes another flow (see Table 2).
Note: The depth of invocation for flows is only one level deep. A main flow can invoke another flow (or can invoke multiple other flows, one at a time) but an invoked flow cannot invoke another flow.
Table 2. Depth of invocation for flows
Flow file: Levels: Example in the Outline view:
Main flow:
  • The flow file is a main flow that does not invoke another flow.
  • Flow node (topmost)
  • Invoke nodes for invocations of operations (Level 1)
Flow node and invoke nodes
Main flow with invoked flow:
  • The flow file is a main flow that invokes another flow.
  • The generation properties editor shows both the main flow and the invoked flow in the Outline view.
  • Flow node (topmost)
  • Invoke nodes for invocations of operations (Level 1)
  • Invoke node for invocation of a flow (Level 1)
    • Invoke nodes for invocations of operations (Level 2)
Flow node and invoke nodes
Invoked flow opened by itself in the generation properties editor:
  • The flow file is an invoked flow (and therefore cannot invoke another flow).
  • Flow node (topmost)
  • Invoke nodes for invocations of operations (Level 1)
Flow node and invoke nodes
In Table 2, note that the structure of the hierarchical tree is the same for: The generation properties editor does not distinguish between a main flow or an invoked flow per se.
Notice also in Table 2 that there are two sets of generation properties for the invoked flow SCRCAP_001:

(See Two development scenarios: (1) Main flow; (2) Main flow with invoked flows.)


Feedback