Supported Elements of the Adobe Library
Special UI elements in the Adobe Designer are available for form development in a Web Dynpro ABAP application. Go to the Layout tab page in the form builder. Depending on how the forms are integrated the following libraries are available for Web Dynpro ABAP in the Library group box.
If you have selected the entry ZCI Layout as the Layout Type in the form builder's Properties, as a developer of forms based on ZCI you can use the Web Dynpro Native library.
The following elements are currently supported by the Web Dynpro ABAP environment:
With the Web Dynpro
form UI element Send, the input data of a PDF form is sent to an SAP
backend system. The Web Dynpro
context bound to the
InteractiveForm
(property dataSource in the view designer) is updated with the input
data. The event onSubmit of the
Web Dynpro UI element InteractiveForm is also triggered.
Both value helps can be retrieved from the Web Dynpro library in the Adobe Designer using drag and drop on the form. The difference between the two values is that EnumeratedDropDownListNoSelect does not automatically select a value if either no entry at all is found in the data part or no entry is found that is relevant to the current selection list. Whilst EnumeratedDropDownList would automatically retrieve the first entry from the selection list.
1. Place the Adobe UI element as usual on the template and bind it to the context in the data view.
2. Change the element value binding.
a. ChooseElement Values.
On the following popup the following entry for Objects appears below the group title Binding:
$record.sap-vhlist.REPLACE_THIS.item[*]
b. Replace REPLACE_THIS with the SOM expression of the data binding.
You can get this value from the Object menu. This is the value that appears after $record in the standard binding. Example Node.DVH3.
Note that you escape each point with \.
Example of a correct value: $record.sap-vhlist.Node\.DVH3.item[*]

The values of the EnumeratedDropDownList are taken from the VALUE_SET of the bound Web Dynpro attribute. If the type of the attribute is DDIC (ABAP Dictionary) and domain fixed values are defined, these are shown. You can also program the VALUE_SET to fill with values at runtime.
The Adobe UI element input help makes it possible to call an input help from the form.

Example of input help in an input field:

Note that the coding of the xfo input help must be slightly adjusted. Enter the name of the bound attribute as field name. In the present example this is CARRID.
● Before:

● After:

So the Adobe UI element input help is the connection to the Web Dynpro ABAP input help.
Developers of forms
based on ACF should use the Web Dynpro ActiveXlibrary (see Documentation about
PDF-Based Print
Forms).
The following element is currently supported by the Web Dynpro ABAP environment:
With the Web Dynpro form UI element Send, the input data of a PDF form is sent to an SAP backend system for storage. The UI element also provides an automatically generated event.

Documentation
about forms and the Form Builder is available under
Form Design Using the
Form Builder. Note that for
Web Dynpro ABAP the interface definition and activation mentioned there is not
required.
Documentation on the individual UI elements is available in the online help for the form builder under Help ® Adobe LifeCycle Designer Help, section Working with Objects.
