Workflows Launched by Other Workflows

Installations often have one workflow start another workflow using the scheduleWorkflowEvent method in the Standard Workflow Handler. One of the initiating workflow steps launches the method through a call action.

Arguments to the step include the following:

Name	Value
workflow	Name of the workflow to launch.
requestName	Name to be assigned to the request. If not specified, the name of workflow is the default.
scheduleDate	Date and time you want the workflow to launch. Must be specified with a java.util.Date value. If this argument is not set, the workflow launches immediately.
scheduleDelaySeconds	An alternative to using scheduleDate. When set, the value is the number of seconds to delay before launching the workflow.
caseName	Specify a user friendly name for workflowCase to be displayed in the user interface. If no name is specified, the default is the name of workflow.
launcher	Name of the identity to be displayed as the launcher of the new workflow case. If this argument is not specified, the launcher of the initiating workflow is used.

A workflow that is launched by another workflow is different from a workflow that is launched as a subprocess. If a workflow is launched as a subprocess, the calling workflow waits until the subprocess is completed. After the workflow returns control to the caller, the processing continues.

A workflow that is launched by another workflow causes a completely separate workflow to begin launching. After the new workflow is started, the original or calling workflow moves on to its next step.