Description:

The Create Execute Process Instance workflow step creates a new Process Instance from a selected Process Definition and executes it.

The step supports:

• Selecting the Process Definition to use for the new instance.
• Passing variables to the new Process Instance.
• Passing Globals to the new Process Instance.
• Passing selected Variables to the new Process Instance.
• Passing selected Globals to the new Process Instance.
• Selecting the execution priority.
• Configuring the execution interval type.
• Providing an optional name for the new Process Instance.
• Configuring an execution interval.
• Storing the new Process Instance ID in a Variable or Global variable.
• Returning a True or False result for subsequent workflow processing.

Usage:

The Create Execute Process Instance step is typically used when one workflow needs to start another Process Definition as a new Process Instance.

The parent workflow can select the Process Definition to execute and optionally provide Variables or Globals to the newly created instance.

A typical workflow pattern is:

Prepare Data → Create Execute Process Instance → Continue Process

The newly created Process Instance ID can optionally be stored in a Variable or Global variable and used by subsequent workflow activities.

The step is particularly useful when a workflow needs to:

• Start another Process Definition.
• Launch a reusable subprocess as an independent Process Instance.
• Pass information from the current workflow to the new instance.
• Start different Process Definitions based on workflow conditions.
• Control the priority of the new Process Instance.
• Configure execution interval information.
• Track the newly created Process Instance using its ID.

Typical Workflow Suggestions:

Start a Process Definition from Another Workflow

Use this step when one workflow needs to start another Process Definition.

Example:

Main Process → Create Execute Process Instance → Continue Main Process

Configure the definition to use the Process Definition you want to start.

This allows the current workflow to initiate another Process Instance without requiring the target process to be manually started.

Launch a Child Process for Additional Processing

Use the step when part of a larger business process should be handled by a separate Process Definition.

Example:

Order Processing → Create Execute Process Instance → Continue Order Processing

The target Process Definition can handle the additional processing independently.

Pass Variables to the New Process Instance

Enable Pass variables to new instance when the new Process Instance needs access to Variables from the current workflow.

Example:

Collect Request Data → Create Execute Process Instance

Variables such as:

• Request ID
• Customer ID
• Request Type
• Priority

can be made available to the new Process Instance according to the configured variable-passing behavior.

The XML exposes both a general Pass variables to new instance option and a Pass selected variables to new instance property.

Pass Selected Variables

Use Pass selected variables to new instance when only specific Variables should be supplied to the new Process Instance.

Example:

Prepare Data → Create Execute Process Instance → Continue

Selected Variables might include:

• variable.RequestID
• variable.CustomerName
• variable.RequestType

This allows the workflow configuration to identify the Variables intended for the new Process Instance.

Pass Globals to the New Process Instance

Enable Pass globals to new instance when the new Process Instance needs Globals from the current workflow environment.

Example:

Determine Processing Configuration → Create Execute Process Instance

The new Process Instance can receive the configured Globals according to the step's passing configuration.

Pass Selected Globals

Use Pass selected globals to new instance when the workflow should pass specific Globals rather than configuring the general Global-passing option.

Example:

Prepare Environment Information → Create Execute Process Instance

Select the Globals that the new Process Instance should receive.

The XML explicitly exposes a separate property for passing selected globals to the new instance.

Start Different Process Definitions Based on a Condition

Use the step after a decision or evaluation when different Process Definitions need to be started depending on workflow information.

Example:

Evaluate Request Type → Select Process → Create Execute Process Instance

Possible workflow paths can identify the appropriate Process Definition before the Create Execute Process Instance step executes.

Store the New Process Instance ID

Use Variable/Global to store instance ID when subsequent workflow activities need to reference the Process Instance that was created.

Example:

Create Execute Process Instance → Store Instance ID → Continue

The resulting Process Instance ID can be stored in a Variable or Global variable.

This provides a reference that later workflow activities can use when they need to work with the newly created Process Instance.

Assign an Execution Priority

Use Select execution priority when the new Process Instance should be created with a particular execution priority.

Example:

Identify Urgent Request → Create Execute Process Instance

Configure the execution priority appropriate for the new Process Instance.

The XML exposes execution priority as an optional property using the clsInstancePriority data type.

Provide a Name for the New Instance

Use the name of the instance to give the new Process Instance a meaningful name.

Example:

Create Execute Process Instance

Instance name:

Customer Onboarding - {{CustomerID}}

A meaningful name can make Process Instance identification easier when viewing or managing process instances.

Configure the Execute Interval

Use the Execute interval and Execute interval type properties when the workflow requires execution interval configuration for the new Process Instance.

Example:

Prepare Process → Create Execute Process Instance

Configure:

• Execute interval type
• Execute interval

The XML defines both properties as optional and identifies TaskExpireType as the data type for the interval type. The interval value itself is a string property with a default value of 0.

Confirm the exact interpretation of interval values against the FlowWright implementation before documenting specific units or timing behavior.

Start a Process After an Approval

Use the step after an approval activity when a separate Process Definition should start only after the request has been approved.

Example:

Submit Request → Approval → Create Execute Process Instance → Continue

The approved workflow can start the appropriate downstream Process Definition.

Start a Process for Each Business Record

Use the step within a workflow pattern that processes multiple records when each record requires a separate Process Instance.

Example:

Get Records → Process Record → Create Execute Process Instance

The appropriate Variables for the current record can be passed to the new Process Instance.

Launch a Reusable Process

Use this step to invoke a reusable Process Definition from multiple workflows.

Example:

Main Workflow → Create Execute Process Instance → Reusable Process

This can help separate specialized processing into dedicated Process Definitions.

Example:

Let’s build and execute the “createExecuteInstanceDef” example.           

• Create a new process definition named “createExecuteInstanceDef” and open it in designer mode. 
• Drag the "createExecuteInstance" step to the canvas.
• Connect the dots between the “Start” and the “createExecuteInstance” steps, as shown above.
• Select the line between the steps to configure the “Connection Properties”. The default property values are “None, True, False, Error, and Evaluate”. Depending on the step’s purpose, you can configure additional values.
• Define a variable or a global to store the process instance ID.
• Click the "createExecuteInstance" step to configure its "Required" properties. Provide a name for the step, then select the process definition from the drop-down list. Click the Save button. Note: Click the "AI Predict" button to have the Copilot add new process steps that match your process description. 

• Click the "createExecuteInstance" step to configure its "Optional" properties. Select the process definition from the drop-down list. Choose whether variables and globals must be passed to the new process instance. Provide specific variables to pass instead of passing all variables to the new process instance (separated by commas). Select the execution priority from the drop-down list (low, medium, high). Select the execution interval type from the drop-down list (days, months, hours, minutes). Note: Configuring the execution interval for a few minutes is recommended when executing this process step in a loop. Provide specific globals to pass, instead of passing all globals to the new process instance (separated by commas). Provide a name for the new process instance. Provide the execution interval value in time. Provide the variable or global reference to hold the new process instance ID. Click the Save button. 

• The “Logging” configuration is necessary for documentation and also measures workflow progress and percent complete. Do this by configuring the step state and percent fields individually, as shown below. Configure the “Logging” using the following properties.

• Save the process definition. Create a new process instance and execute it. Render the process instance and select the Create Execute Process Instance step to view its properties and execution information. When the workflow reaches the step, FlowWright uses the selected Process Definition to create and execute a new Process Instance using the configured options. If the operation succeeds, the workflow follows the True path. If it does not succeed, the workflow can follow the False path.

• Navigate to the Process - Instances page to view the new instance.  Render the new process instance to view the variables and globals passed from the source instance.

Tips:

• Select the correct Process Definition in Definition to use.
• Verify that the selected Process Definition is available in the environment where the workflow executes.
• Use meaningful names for newly created Process Instances.
• Pass only the Variables required by the new Process Instance.
• Use Pass selected variables to new instance when the child process requires only a specific subset of Variables.
• Use Pass selected globals to new instance when only specific Globals should be passed.
• Verify that Variables being passed contain the expected values before the Create Execute Process Instance step executes.
• Avoid passing unnecessary information to the new Process Instance.
• Use meaningful Variable or Global names when storing the new Process Instance ID.
• Store the new Process Instance ID when later workflow activities need to reference the child instance.
• Verify the stored Process Instance ID after the step executes.
• Use Select execution priority when the execution priority of the new Process Instance needs to be explicitly configured.
• Give the new Process Instance a meaningful name when it will need to be identified by users or administrators.
• Test the workflow with representative Process Definitions before deployment.
• Test the False return path and determine the appropriate failure-handling behavior.
• Test workflows with and without Variables and Globals being passed.
• Verify that the target Process Definition can operate with the Variables or Globals being supplied.
• Test the configuration after changing the target Process Definition.
• Review execution interval configuration carefully before deploying workflows that use it.
• Do not assume the meaning or units of Execute interval without confirming the FlowWright implementation.
• Avoid relying on the new Process Instance ID unless the Variable/Global to store instance ID property has been configured.
• When launching multiple Process Instances, make sure each new instance receives the intended Variables, Globals, priority, and name.
• Consider connecting the False return path to an appropriate logging, notification, or recovery activity.

Definition Sample:

You may provide a sample CreateExecuteInstanceDef process definition for users to download and later import into their FlowWright Process Definition.

After importing the sample, verify and complete any missing configuration, including:

• Process Definition to execute.
• Variable-passing configuration.
• Selected Variables to pass.
• Global-passing configuration.
• Selected Globals to pass.
• Execution priority.
• Execute interval type.
• Execute interval.
• New Process Instance name.
• Variable or Global used to store the new Process Instance ID.
• Workflow Variable references.
• Environment-specific Process Definition configuration.
• Downstream True and False workflow paths.

After verifying the configuration, save the Process Definition before execution.

Click here to download the sample file.