The following illustration shows the design of this example's embedded guide.

The

Embedded Guide

step within the embedding guide asks the user to enter a number. Based on the value of this number, the guide chooses one of the three branches.

You must define fields for all the values sent to the embedded or embedding guide in the guide properties.

Here, four fields are declared. One is an input field and the others are output fields. These fields are available in all steps within the embedded guide.

Input fields are meant to be read. That is, a guide places data into an input field and this data is read by the embedded guide. If, however, the embedded guide changes the value of an input field, this change is seen by the embedding guide.

An output field does not exist until it is set to a value within an embedded guide. For example, if the fifth step in a guide is an embedded step, output fields are invisible in the first five steps. However, they are visible beginning at the sixth step.

For more information on selections you make in the

Type

column see Data types & Field Properties.

These fields are used in the following Screen Step:

The table contains the fields set in the

Guide Fields

tab. Select the fields to insert in the step from the insert lists.

Here, no object fields display because the

Applies To

field was set to

* Any *

. This means that the embedded guide does not have access to any of the fields within any objects. If this guide needed access to object fields, you will need to select the object in the

Applies To

list or pass them to the guide as input fields.

The step following this data decision step uses the value placed in the

Number 1

field to choose the guide's outcome.