This page was last edited on December 3, 2013, at 21:20.
Comments or questions about this documentation? Contact us for support!
Use the Subroutine block to create reusable sub-modules (sub-workflows). You can invoke external SCXML documents or use a sub-workflow created using Composer. The input and output parameters names will be automatically picked from the sub-workflow created by Composer. Composer supports passing variables between a workflow and sub-workflow.
Also see Using Composer Shared Subroutines.
Now the Parameters property can be used for the Parameter Synchronization. The main diagram implicitly parses the sub-workflow parameters and lists them in the Parameter settings dialog as shown below.
The Subroutine block has the following properties:
Find this property's details under Common Properties.
Find this property's details under Common Properties.
Find this property's details under Common Properties.
The Uri property specifies the destination (URL or Composer Project) depending on the value of the Type property. To set a URL destination for the Uri property (Type property is set to URL):
To set a Project destination for the Uri property (Type property is set to ProjectFile):
The Type property sets the type of the invoked subroutine. There are two options:
To select a value for the Type property:
Find this property's details under Common Properties.
Find this property's details under Common Properties.
Find this property's details under Common Properties.
Find this property's details under Common Properties.
Use the Parameters property to specify parameters to pass to the invoked sub-workflow. To specify parameters:
input | Input parameters are variables submitted to the sub-workflow. |
out | Output parameters are variables that the sub-workflow returns and will be reassigned back to the current workflow. |
inout | Inout parameters are parameters that act as both input and output. |
Delete Button To delete a parameter: