Getting started with nested workflows

A nested workflow is a workflow embedded in a parent workflow that completes an action before the parent workflow completes. 

Use nested workflows to take advantage of the following features:

➢External variables: External variables can be used to relay information from the parent to nested workflows. For example, when a user requests software, the user's information can be passed to a nested onboarding workflow.

➢ Enable reuse and eliminate redundancy: Create a nested workflow to perform an action that is repeated across multiple workflows. For example, sending a notification when a workflow fails or creating a ticket.

➢ Simplify maintenance and testing: When you update a nested workflow, all instances of the nested workflow in parent workflows are updated. Update once, update everywhere. Breaking workflows down makes it easier to understand what each component of the workflow does, makes it easier to test each component of the workflow separately, and makes it easier to troubleshoot.

Limitations

• A nested workflow can’t contain or trigger another nested workflow.
• Nested workflows are object specific. For example, a nested workflow for the User object, can’t be used in a workflow for the Asset object.