You can use the InteractiveForm UI element to insert an interactive or a non-interactive PDF form into a view. This enables you to create and design a form from scratch. The layout of the PDF form is designed with Form Builder. The required Adobe-specific standard objects are provided by a library. These standard objects are subdivided into field objects and text module objects. They represent layout elements like text fields, time fields, push buttons, or checkboxes. They can be inserted into the PDF form template. Field objects like push buttons, radio buttons, checkboxes, and dropdown list boxes enable the user to interact with the application. On the other hand, text module objects like circles, rectangles, and static texts have a static characteristic and can only be used for presentations with a static content. The field objects have a similar function to Web Dynpro UI elements. They are bound to the form context in the Designer. In the standard system the form context is predetermined by an XML schema, which is generated at design time on the basis of the Web Dynpro context.
The form builder is automatically called when you edit the InteractiveForm UI element inserted into the view. You edit the InteractiveForm UI element by double-clicking on the UI element in the View Designer.
Note that when using the InteractiveForm UI element you cannot display two InteractiveForm UI elements at the same time in the browser window.
See also:
Documentation about integrating Adobe forms into Web Dynpro ABAP.
PDF-Based Print Forms
Documentation about PDF-based forms.
When the template is designed there is no check for the tool tip property to guarantee Accessibility.
Runtime Class |
CL_WD_INTERACTIVE_FORM |
Properties in the View Designer
Name |
Type |
Initial Value |
Bindable |
ID |
STRING |
(automatic) |
No |
STRING |
|
No |
|
STRING |
|
No |
|
STRING |
|
No |
|
STRING |
|
No |
|
Context Node |
|
Yes |
|
WDY_BOOLEAN |
true |
Yes |
|
STRING |
300px |
Yes |
|
XSTRING |
|
Yes |
|
WDY_BOOLEAN |
false |
Yes |
|
STRING |
|
No |
|
Text |
|
Yes |
|
STRING |
|
No |
|
WDUI_VISIBILITY |
visible |
Yes |
|
STRING |
300px |
Yes |
Events in the View Designer
Name |
Further properties that can be inherited are defined in the associated higher-level class. The associated interface elements are:
For dynamic programming the same properties, events, and aggregations are provided in the View Designer. Bear in mind the different spellings.
Dynamic Programming of Properties
View Designer Name |
Runtime Name |
Type |
ADDITIONAL_ARCHIVES |
STRING |
|
ARCHIVE |
STRING |
|
CLASS_ID |
STRING |
|
CODE_BASE |
STRING |
|
DATA_SOURCE |
OBJECT |
|
ENABLED |
WDY_BOOLEAN |
|
HEIGHT |
STRING |
|
PDF_SOURCE |
XSTRING |
|
READ_ONLY |
WDY_BOOLEAN |
|
TEMPLATE_SOURCE |
STRING |
|
TOOLTIP |
WDY_MD_TRANSLATABLE_TEXT |
|
TYPE |
STRING |
|
VISIBLE |
WDUI_VISIBILITY |
|
visible: none |
CL_WD_INTERACTIVE_FORM=>E_VISIBLE-NONE |
|
visible: visible |
CL_WD_INTERACTIVE_FORM=>E_VISIBLE-VISIBLE |
|
WIDTH |
STRING |
Dynamic Programming of Events
View Designer Name |
Runtime Name |
ON_SUBMIT |