InteractiveForm 

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.

The integration of active controls like InteractiveForm in Web Dynpro ABAP popups is not supported.

More Information:

●      Adobe Integration

Documentation about integrating Adobe forms into Web Dynpro ABAP.

●      PDF-Based Print Forms

Documentation about PDF-based forms.

To enable the development of accessible applications, the tooltip property is not checked during the syntax check.

 

Runtime Class

CL_WD_INTERACTIVE_FORM

 

Properties in View Designer

Name	Type	Initial Value	Bindable
ID	STRING	(automatic)	no
additionalArchives	STRING		no
archive	STRING		no
classId	STRING		no
codeBase	STRING		no
dataSource	Context nodes		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	Text		yes
type	STRING		no
visible	WDUI_VISIBILITY	visible	yes
width	STRING	300px	yes

 

Events in View Designer

Name

onSubmit

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

●        AbstractActiveComponent

●        UIElement

●        ViewElement

Dynamic Programming

For dynamic programming, the same properties, events and aggregations are available as in the view designer. 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
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