Table of Contents

Search

  1. Preface
  2. Understanding Data Types and Field Properties
  3. Designing Processes
  4. Using and Displaying Data
  5. Designing Guides
  6. Designing Process Objects
  7. Designing Service Connectors
  8. Using Connectors
  9. System Services, Listeners and Connectors

2. Design

2. Design

Screen Step

Screen Step

Use the a Screen step to perform the following tasks:
  • Show instructions about what is being displayed, what to enter, and so on.
  • Update an object's data based on user input.
The following image shows a Screen step that contains what a sales rep would say to a prospect:
This image shows the Edit Screen window of a screen step. There is a prompt for a sales representative to ask a customer about a POC. There are options for the representative to select.
When the sales representative runs the guide, they see the question that they need to ask as well as buttons for each possible answer.
The following image shows a part of a simulated Screen step:
This image shows a part of a simulated screen step. There is a prompt and the four options.
After you add a Screen step with different choices, Guide Designer creates a branch for each answer.
The following image shows a Screen step with four possible answers:
This image shows a canvas view of the Screen step. Four branches emerge from it, one for each possible outcome.
You can add steps to each branch of the Screen step.
The following image shows a Screen step with two answers:
This image shows a Screen step with two outcomes. One branch leads to a Create step and the other branch leads to an End step.
You can insert the following field types when you edit a Screen step:
  • Editable Fields: Fields that the user can edit. You can proceed to the next step even if you do not enter values in these fields.
  • Read-only Fields: Fields that the end user cannot edit.
To create a translated version of a Screen step, see Guide Translations.