When creating a guide or process, one set of choices might require some activities and a branch would occur. After these activities are completed, the flow of steps should rejoin the actions of another branch.

For example, a guide that leads a sales rep through a conversation with a prospect could take many different branches as the rep talks about features and overcomes objectives. However, at some point in some of these branches, the rep should schedule a meeting. The scheduling step and the steps that follow may be same. Rather than add a scheduling step to each branch that needs one, you could instead jump to a scheduling step that has the scheduling steps.

A

Jump Step

is exactly what it sounds like. In the following illustration, the "Were they interested?" step has two branches, "Yes" and "No". This "Yes" branch leads to a

Jump Step

that tells the process to move to and execute the "Schedule a Meeting?" step.

Unlike embedded steps or service call steps, a jump step changes the execution path.

A Jump step is displayed as a circle with a rounded arrow in it. To the right of the circle is the name of the step to which the step will jump. This name is also a link. When you click on it, the step that is the target of the jump is displayed and selected.

The target of the jump has a small rounded arrow at its upper left corner. In the previous figure, notice the arrow points into the step for the target of the jump while the arrow of the jump step points away from it. This little arrow lets you know that the step is also executed from another step in addition to being executed normally within the branch.

If more than one step jumps to the same target step, you can hover over the small arrow to see how many jump steps have this step as their target. If you click on the

jumped to

arrow, the editor displays a dialog showing all of the steps jumping to it.

To create a Jump step, simply choose the Jump Step type and, from the To list, select the step to which you want to change the execution path.