Table of Contents

Search

  1. Preface
  2. Overview, Downloading, and Installing
  3. Administration API
  4. Identity Service API
  5. Screenflow Programming and SDK
  6. ActiveVOS WSHT API
  7. Embedding Request Forms in Standalone Web Pages
  8. XML-JSON for Process Central

7. APIs, SDKs, and Services

7. APIs, SDKs, and Services

What is a Guide Designer Automated Step

What is a Guide Designer Automated Step

A Guide Designer guide is built with steps. There are only a few step types, such as a
screen step
in which there is a prompt and answers that automatically create new steps.
A Service Call step is another step type. This is described in the Service Call discussion elsewhere in this help. This topic looks at creating services using Process Developer.
The steps for creating an a service call step are:
  1. Create a new BPEL process.
  2. In the Participants view, create a new Process Service Consumer based on the Process Designer system service.
  3. Build the process to do something required by a guide. A process's requirements include:
    • Defining the input for the service. This can be required and user-defined data, and it can either be simple or complex. Process Designer editors can add their own data by defining fields in the
      Properties
      dialog.
    • Setting response messages from the service.
    • Naming the resources the guide will use, such as images.
    • Creating the HTML renderings for complex data types.
  4. Create the
    services.xml
    file for the service all step service descriptor.
Note:
For additional getting started resources, create a new orchestration project and select the Guide Designer Customization Starter template.