InteractiveForm 

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
ID	STRING	(automatic)	No
additionalArchives	STRING		No
archive	STRING		No
classId	STRING		No
codeBase	STRING		No
contextMenuBehaviour	WDUI_CONTEXT_MENU_BEHAVIOUR	inherit	No
contextMenuId	WDY_MD_UI_ELEMENT_REFERENCE		No
dataSource	Context node		Yes
displayType	WDUI_INTERACT_FORM_DISP_TYPE	activeX	Yes
enabled	WDY_BOOLEAN	true	Yes
height	STRING	300px	Yes
pdfSource	XSTRING		Yes
readOnly	WDY_BOOLEAN	false	Yes
templateSource	STRING		No
tooltip	Translatable text		Yes
type	STRING		No
visible	WDUI_VISIBILITY	visible	Yes
width	STRING	300px	Yes

 

Events in the View Designer

Name

onSubmit

Other properties that can be inherited are defined in the associated higher-level classes. The associated UI elements are:

●        AbstractActiveComponents

●        UIElements

●        ContextMenuProviders

●        ViewElements

Accessibility

Note that, in connection with Accessibility, the tooltip attribute is not checked as part of the syntax check.

Dynamic Programming

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
additionalArchives	ADDITIONAL_ARCHIVES	STRING
archive	ARCHIVE	STRING
classId	CLASS_ID	STRING
codeBase	CODE_BASE	STRING
contextMenuBehaviour	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
contextMenuId	CONTEXT_MENU_ID	WDY_MD_UI_ELEMENT_REFERENCE
dataSource	DATA_SOURCE	OBJECT
displayType	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	ENABLED	WDY_BOOLEAN
height	HEIGHT	STRING
pdfSource	PDF_SOURCE	XSTRING
readOnly	READ_ONLY	WDY_BOOLEAN
templateSource	TEMPLATE_SOURCE	STRING
tooltip	TOOLTIP	WDY_MD_TRANSLATABLE_TEXT
type	TYPE	STRING
visible	VISIBLE	WDUI_VISIBILITY
visible: none	CL_WD_INTERACTIVE_FORM=>E_VISIBLE-NONE
visible: visible	CL_WD_INTERACTIVE_FORM=>E_VISIBLE-VISIBLE
width	WIDTH	STRING

 

Dynamic Programming of Events

View Designer Name	Runtime Name
onSubmit	ON_SUBMIT

 

Showing and Hiding the Adobe-Reader-Toolbar

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 access the method handler (IF_WD_IACTIVE_FORM_METHOD_HNDL) in WDDOMODIFYVIEW.

a.      DATA l_interactive_form TYPE REF TO cl_wd_interactive_form.                             b.      l_interactive_form ?= view->get_element( `MY_INTERACTIVE_FORM` ).                             c.      DATA l_ifba_hndl TYPE REF TO if_wd_iactive_form_method_hndl.                             d.      l_ifba_hndl ?= l_interactive_form->_method_handler.

 

Here you can use the methods SET_HIDE_TOOLBARS or GET_HIDE_TOOLBARS to display the toolbar or to check the display status.

e.      l_ifba_hndl->set_hide_toolbars( abap_true ).

The other methods of IF_WD_IACTIVE_FORM_METHOD_HNDL are not released.

Example

You can find an example of this UI element in the WDR_TEST_ADOBE component.

Additional Information

You can find basic information about the SAP Interactive Forms by Adobe solution in the SAP Interactive Forms by Adobe documentation.