Modeling Composite Views for Use in Guided Procedures

You can expose composite views created in Visual Composer as callable objects in the Guided Procedures design time, and then attach the callable object to an action in a Guided Procedures process flow. In Guided Procedures, these Visual Composer applications are called WD4VC (Web Dynpro for Visual Composer) application callable objects. More information: Exposing WD4VC Applications as Callable Objects.

General Guidelines

Following are some general guidelines for modeling composite views for use as WD4VC callable objects in a Guided Procedures process flow:

Each WD4VC callable object that passes data to and from Guided Procedures should contain at least a start point and an end point.

Note
Instead of a start point, you can use a data share. More information: Transferring Data Using a Data Share

End of the note.
Add an end point to each WD4VC callable object to terminate the application.
To create multiple result states, add multiple boolean fields to the end point. Each boolean field should be named ResultState_<status> (where <status> is the result state name, for example, ResultState_Reject).
A WD4VC callable object that does not pass any data to Guided Procedures does not need a start point, it only needs an end point.

Guidelines When Upgrading from Earlier Versions

Visual Composer models that were created in enhancement package 1 for SAP NetWeaver CE 7.1, are supported in SAP NetWeaver 7.2.
If you want to modify a Visual Composer model that was created in enhancement package 1 for SAP NetWeaver CE 7.1, in SAP NetWeaver 7.2, note the following:
There are two methods for creating multiple result states in enhancement package 1 for SAP NetWeaver CE 7.1:
1. Create multiple end points. In this case, the name of an end point is the name of the result state.
2. Create one end point with multiple boolean fields named ResultState_<status> (where <status> is the result state name, for example, ResultState_Reject).
Depending on the method used when creating the result states in enhancement package 1 for SAP NetWeaver CE 7.1, you should modify them in SAP NetWeaver 7.2 as follows:
- To delete a result state:
  - First method (multiple end points): Delete the relevant end point
  - Second method (multiple fields on a single end point): Delete the relevant field from the end point
- To add an additional result state:
  - First method (multiple end points): Copy and paste one of the end points to duplicate it, then rename it to the name of the new result state. (End point behavior was changed in SAP NetWeaver 7.2, so adding a new end point from the Compose task panel will lead to unexpected results.)
  - Second method (multiple fields on a single end point): Add a new field to the existing end point

Note Note

To create a new WD4VC callable object in SAP NetWeaver 7.2, you should use only the second method of a single end point with multiple result state fields. Using multiple end points (the first method) is not supported in SAP NetWeaver 7.2.

End of the note.