Skip to content

Custom Controls (Obsolete)

Mostly Not Needed Anymore

Earlier versions of abap2UI5 required custom UI5 controls to cover common browser interactions — setting the page title, moving focus, scrolling, copying to the clipboard, opening new tabs, and so on. These are now built into the framework as frontend events, callable from ABAP via client->action->gen( client->cs_event-... ). The custom controls that used to wrap these behaviors are obsolete.

Replaced Custom Controls

The table below lists custom controls that are no longer necessary and the built-in action that replaces each one.

Old Custom Control PurposeNew Built-in ActionDocumentation
Set the browser tab titlecs_event-set_titleTitle
Set the launchpad titlecs_event-set_title_launchpadTitle
Move input focuscs_event-set_focusFocus
Scroll to a positioncs_event-scroll_toScrolling
Scroll an element into viewcs_event-scroll_into_viewScrolling
Start a timercs_event-start_timerTimer
Toggle the soft keyboardcs_event-keyboard_set_modeSoft Keyboard
Read frontend infoclient->get( )-s_device, -s_ui5, -s_focus, -s_scrollInfo

Typical Pattern

Instead of writing a custom control, call the matching action after an event:

abap
client->action->gen( val   = client->cs_event-set_title
                t_arg = VALUE #( ( `Invoice 4711` ) ) ).

See the linked cookbook pages above for the full argument list of each action.