You can use the InteractiveForm UI element to insert a PDF document (interactive or non-interactive) into a view.
You can also integrate a form which was created with the Form Builder.
The Form Builder is called if you double click on the templateSource property of the InteractiveForm UI element.
You can find details about the integration of forms in the section Integration of Forms .
Runtime Class |
CL_WD_INTERACTIVE_FORM |
Properties in the View Designer
Name |
Type |
Initial Value |
Bindable |
STRING |
(automatic) |
No |
|
STRING |
No |
||
STRING |
No |
||
STRING |
No |
||
STRING |
No |
||
WDUI_CONTEXT_MENU_BEHAVIOUR |
inherit |
No |
|
WDY_MD_UI_ELEMENT_REFERENCE |
No |
||
Context node |
Yes |
||
WDUI_INTERACT_FORM_DISP_TYPE |
activeX |
Yes |
|
WDY_BOOLEAN |
true |
Yes |
|
STRING |
300px |
Yes |
|
STRING |
Yes |
||
XSTRING |
Yes |
||
WDY_BOOLEAN |
false |
Yes |
|
STRING |
No |
||
Translatable text |
Yes |
||
STRING |
No |
||
WDUI_VISIBILITY |
visible |
Yes |
|
STRING |
300px |
Yes |
Events in the View Designer
Name |
Other properties that can be inherited are defined in the associated higher-level classes. The associated UI elements are:
Accessibility
Note that, in connection with Accessibility , the tooltip attribute is not checked as part of the syntax check.
For dynamic programming, the same properties, events, and aggregations as in the View Designer are available. 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 |
|
CONTEXT_MENU_BEHAVIOUR |
WDUI_CONTEXT_MENU_BEHAVIOUR |
|
contextMenuBehaviour: inherit |
CL_WD_INTERACTIVE_FORM=>E_CONTEXT_MENU_BEHAVIOUR-INHERIT |
|
contextMenuBehaviour: provide |
CL_WD_INTERACTIVE_FORM=>E_CONTEXT_MENU_BEHAVIOUR-PROVIDE |
|
contextMenuBehaviour: suppress |
CL_WD_ITEM_LIST_BOX=>E_CONTEXT_MENU_BEHAVIOUR-SUPPRESS |
|
CONTEXT_MENU_ID |
WDY_MD_UI_ELEMENT_REFERENCE |
|
DATA_SOURCE |
OBJECT |
|
DISPLAY_TYPE |
WDUI_INTERACT_FORM_DISP_TYPE |
|
displayType: activeX |
CL_WD_INTERACTIVE_FORM=>E_DISPLAY_TYPE-ACTIVE_X |
|
displayType: native |
CL_WD_INTERACTIVE_FORM=>E_DISPLAY_TYPE-NATIVE |
|
ENABLED |
WDY_BOOLEAN |
|
HEIGHT |
STRING |
|
JOB_PROFILE |
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 |
Some properties of the InteractiveForm UI element are not set using the UI element properties but instead with the help of method handler. You can find more information in IF_WD_IACTIVE_FORM_METHOD_HNDL .
You can find an example of this UI element in the WDR_TEST_ADOBE component.
You can find basic information about the SAPInteractive Forms by Adobe solution in the Form-Based Processing of Business Data .