Show TOC Start of Content Area

Background documentation SAP Composite Forms by Adobe  Locate the document in its SAP Library structure

SAP Composite Forms are used for all form-driven process steps within a composite application. They may be implemented as online or offline forms. Online forms are used whenever system access is essential, for example, for value help or data validation. Offline forms are used whenever a system connection is not available or desired.

You can use SAP Composite Forms to implement the following use cases:

...

·        Process initiation: Submission of a form triggers a composite process. The system populates the data from the form into the process context.

      Offline step interaction: While a business process is running, a participant receives an offline form by e-mail, where he or she can add information or approve/reject only. Submitting the filled out form (by HTTP or SMTP) triggers the completion of the step and fills the process context with the form’s data.

      Generation of a final form artifact: At the end of a composite application business process, a form is created as an artifact to be sent out as the end result of the composite application.

      Online approval (review) of a form: As part of an online process step, a user can view a read-only version of a form as an integral part of the UI step (main panel). The user can also perform an action based on the review (for example, Accept, Reject).

      Online data entry using a form: In an online process step, a form is displayed to the user as an integral part of the UI step (main panel). The user can fill or modify information in the form, and submit it.

To be able to use forms effectively, you must consider the following:

·        Online forms are implemented by adding an SIF control within Web Dynpro Java (WDJ) components.

Data retrieval to and from the form is achieved by interaction with the component context. The back-end connectivity is implemented within the WDJ component and the rules for WDJ apply.

      Offline forms are implemented by creating a Composite Form callable object in Guided Procedures.

A form template is created with the Adobe LifeCycle Designer. The system retrieves all data from the GP context and writes it back into the GP context.

      An offline form may be submitted either through HTTP or by sending an e-mail to the GP server.

      You should minimize the amount of scripting within the form, and in particular, the calls to Web services, so as not to confuse the layers.

More Information

For more information about composite forms in Guided Procedures, see Integrating Offline and Form-Based Activities.

End of Content Area