InputField 

The InputField UI element allows the user to edit or display a single-line text. With an InputField you can edit any simple data type you like.The conversion from the internal display format and, when the user has input a value, back into the internal display format is done automatically. If, after the user has input a value into the field an error occurs during the conversion to the internal format, the value is not put back into the context, but remains in the data container. When it is next displayed, the InputField with the erroneous value is bordered in red and displayed with an error message.

The input is not checked until the roundtrip is triggered.

To ensure Accessibility a check is made during design time that the label property has been specified.

If no label has been set, and no descriptive text has been specified for the appropriate bound context element in the ABAP Dictionary, a check is made for the tooltip property.

 

Note that the value of InputField is also transferred to the password mode in plain text. For this reason applications that use the property passwordField should only run in HTTPS mode.

You can go to the HTTPS mode through an ICF service setting in transaction SICF by setting SSL as the Security Requirement on the tab Logon Data on the node for your application in the HTTP service tree.

Example of the Display with a Label

 

Runtime Class

CL_WD_INPUT_FIELD

 

Properties in the View Designer

Name	Type	Initial Value	Bindable
ID	STRING	(automatic)	No
alignment	WDUI_INPUT_FIELD_ALIGNMENT	auto	Yes
enabled	WDY_BOOLEAN	true	Yes
explanation	Text		No
length	I	20	Yes
passwordField	WDY_BOOLEAN	false	Yes
readOnly	WDY_BOOLEAN	false	Yes
state	WDUI_STATE	normal	Yes
textDirection	WDUI_TEXT_DIRECTION	inherit	Yes
tooltip	Text		Yes
value	Text		mandatory
visible	WDUI_VISIBILITY	visible	Yes
width	STRING		Yes

 

Events in the View Designer

Name

onEnter

Further properties that can be inherited are defined in the associated higher-level class.  The associated interface elements are:

●      AbstractInputField

●      UIElement

●      ViewElement

Dynamic Programming

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
alignment	ALIGNMENT	WDUI_INPUT_FIELD_ALIGNMENT
alignment: auto	CL_WD_INPUT_FIELD=>E_ALIGNMENT-AUTO
alignment: beginOfLine	CL_WD_INPUT_FIELD=>E_ALIGNMENT-BEGIN_OF_LINE
alignment: center	CL_WD_INPUT_FIELD=>E_ALIGNMENT-CENTER
alignment: endOfLine	CL_WD_INPUT_FIELD=>E_ALIGNMENT-END_OF_LINE
alignment: forcedLeft	CL_WD_INPUT_FIELD=>E_ALIGNMENT-FORCED_LEFT
alignment: forcedRight	CL_WD_INPUT_FIELD=>E_ALIGNMENT-FORCED_RIGHT
enabled	ENABLED	WDY_BOOLEAN
explanation	EXPLANATION	WDY_MD_TRANSLATABLE_TEXT
length	LENGTH	I
passwordField	PASSWORD_FIELD	WDY_BOOLEAN
readOnly	READ_ONLY	WDY_BOOLEAN
state	STATE	WDUI_STATE
state: normal	CL_WD_INPUT_FIELD=>E_STATE-NORMAL
state: required	CL_WD_INPUT_FIELD=>E_STATE-REQUIRED
textDirection	TEXT_DIRECTION	WDUI_TEXT_DIRECTION
textDirection: inherit	CL_WD_INPUT_FIELD=>E_TEXT_DIRECTION-INHERIT
textDirection: ltr	CL_WD_INPUT_FIELD=>E_TEXT_DIRECTION-LTR
textDirection: rtl	CL_WD_INPUT_FIELD=>E_TEXT_DIRECTION-RTL
tooltip	TOOLTIP	WDY_MD_TRANSLATABLE_TEXT
value	VALUE	WDY_MD_TRANSLATABLE_TEXT
visible	VISIBLE	WDUI_VISIBILITY
visible: none	CL_WD_INPUT_FIELD=>E_VISIBLE-NONE
visible: visible	CL_WD_INPUT_FIELD=>E_VISIBLE-VISIBLE
width	WIDTH	STRING

 

Dynamic Programming of Events

View Designer Name	Runtime Name
onEnter	ON_ENTER

Example

You can find examples of this interface element in the system in the Web Dynpro application WDR_TEST_UI_ELEMENTS, and in the component WDR_TEST_EVENTS in the View InputField.