Web Dynpro Component Implementation

Guided Procedures comes with a set of predefined Web Dynpro components that you can expose as a callable object. In addition, it provides interfaces (APIs) that enable you to implement your own Web Dynpro components. This offers you the flexibility to build custom functions and to adapt your processes to more specific scenarios.

In the Order Office Material process several custom Web Dynpro components are used. They demonstrate how you use the APIs to create callable objects that have input and output parameters and result states.

This documentation does not go into detail on the Web Dynpro technology, since the focus is on GP development. To be able to understand and follow the descriptions in this section, you must be familiar with the basics of Web Dynpro programming.

In addition, you must already know how to create development components (DCs) in the SAP NetWeaver Developer Studio, and how to define dependencies to other DCs.

Finally, the Web Dynpro components must be developed in a configuration that contains the following DCs:

• caf/eu/gp/api/wd
• engine.security.facade

The development of the Web Dynpro callable objects used in the example includes the following steps:

1. First, you create a new Web Dynpro development component project, and modify it as follows:
   1. Add design time, build time, and runtime dependencies to DCs caf/eu/gp/api/wd and engine.security.facade .
   2. Add a reference to the caf/eu/gp/api library in the Web Dynpro project properties.
2. You create the Web Dynpro components in the project.
3. You implement the Web Dynpros as follows:
   1. Add the GP interface that the components must implement to the list of implemented interfaces.
      Caution

      To be exposed as callable objects, the Web Dynpro components must implement interface IWebDynproCO - com.sap.caf.eu.gp.co.api .

   2. Implement the methods inherited from the interface in the interface controller.
   3. Implement any additional methods for the completion of the callable object execution, which set a particular result state for the callable object. You can do this either directly in the interface controller, or in the component controller.
   4. Create the user interface. It must include elements such as buttons for example, that trigger the completion of the callable object execution.
4. You build the development component and deploy it to the Java server.

Once you have successfully deployed the Web Dynpro components, you can expose them as callable objects and use them for building the process in the Guided Procedures design time.

To familiarize yourself with the detailed procedure of developing a Web Dynpro callable object, you can work through the tutorial Implementing a Web Dynpro Callable Object .