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:
- You must make your applications known to GP by exposing them as callable objects.
See: Exposing Applications as Callable Objects
- If your application is not supported by the predefined callable object types, you must implement and register your own type.
- If necessary, you can implement additional components that you can integrate in the workflow in Web Dynpro, for example.
- Once you have created your callable objects, you put them together in a process template to build up the composite.
- If your application requires it, you can integrate offline and form-based activities in the process template.
- 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.
- You must choose the appropriate option to start your process.
- If necessary, you can implement functions that complete actions outside the GP runtime.
- Optionally, you can enhance your composite with additional functions.
See: Using the GP APIs