Central and ActiveVOS Screenflow

9.2.4.6
- 9.2.5

Back Next

Embedded Guide Step

To better orchestrate and manage your business processes, you can design guides that embed other guides, similar to how you would create a subprocess that is called from another process.

For example, suppose there are a set of steps associated with entering client information. If there are different ways that your users interact with clients and many need to enter client information, you could group these client information steps into their own guide. Now, whenever a guide needs to enter client information, it just "embeds" the guide. This also means that all embedding guides use the same steps

Using an embedded guide has several advantages, including these:

Avoids Repetition
: If you place commonly used patterns in a separate guide, you can save time and create other efficiencies if you place the discrete set of steps into a guide that can be embedded and reused in other guides. When you change the embedded guide, you can easily make those changes available to all guides that use it.

Clarifies Design
: Embedding can make your design look simpler. Removing steps and placing them into an embedded guide means that the embedding object only shows one step rather than all of the steps. This can simplify the diagram on the canvas. Also, if a problem occurs in the ways steps occur, embedding can make it easier to locate a problem.

Clarifies Logic
: If there are many steps that need to operate on other objects, this allows you to create logical chunks of work that each apply to different objects (such as opportunities and leads). This decreases the complexities of working with multiple object types in a single guide.

You handle the data received from a guide and the data that can get sent back to it using the Input and Output fields defined in the guide properties.

Guides Overview

Embedding and Embedded Field Relationships

An Embedded Example

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal