Tasks

Using Guided Procedures (GP), you can easily integrate various applications and services into a lightweight, user-centric, and process-based composite application. Before you can compose your processes, however, you must make sure that the applications meet the requirements for their proper use in GP.

This section explains in detail the tasks that you need to perform to develop a composite application with Guided Procedures.

Overview

To build your composite, first you need a model for it that defines its steps. Then, the creation of a composite with GP goes through the following steps:

  1. You must make your applications known to GP by exposing them as callable objects.

    See: Exposing Applications as Callable Objects

  2. Once you have created your callable objects, you put them together in a process template to build up the composite.

    See: Modeling and Configuring Workflows

  3. If your application requires it, you can integrate offline and form-based activities in the process template.

    See: Integrating Offline and Form-Based Activities

  4. Once you have designed the process template you must activate it so that you can start a process at runtime. You can also take advantage of the design time tools that support GP content versioning, customization, update, and transport.

    See: Activating and Maintaining Guided Procedures Content

  5. You must choose the appropriate option to start your process.

    See: Starting and Terminating Processes Within a Composite

  6. If necessary, you can implement functions that complete actions outside the GP runtime.

    See: Completing Actions Within a Composite

  7. Optionally, you can enhance your composite with additional functions.

    See: Using the GP APIs