TimedTrigger
UI element TimedTrigger automatically and periodically triggers an event with a specified delay. TimedTriggeris not displayed on the user interface. It therefore ignores the tooltip and the visibility property. However, in specific layouts such as the matrix layout, it does take up space. To trigger an action, you must bind the onAction property to an action. You use the delay property to specify the delay in seconds.
To prevent events being triggered by UI element TimedTrigger, proceed as follows:
● Set the value of the delay to 0 seconds.
● Disable the TimedTrigger UI element.
● Set the visibility property to a value not equal to visible.

Every user interaction is interrupted when the onAction event is triggered.
In the Web Dynpro application, you can – with certain restrictions – use periodical server requests and UI element TimedTrigger to trigger push events – that is, the controlled triggering of events, for example, as a message for the user. When using UI element TimedTrigger, the client actively retrieves the data from the server. Due to the considerable server load, you should only use this option if the number of clients is small.

To enable the development of accessible applications, the tooltip property is not checked during the syntax check, since there is no real need for a tooltip with this UI element.
Runtime Class |
CL_WD_TIMED_TRIGGER |
You can use the onAction property to specify the action that is to be triggered after a specific delay.
Properties in the View Designer
Name |
Type |
Initial Value |
Bindable |
STRING |
(automatic) |
No |
|
WDUI_CONTEXT_MENU_BEHAVIOUR |
inherit |
No |
|
WDY_MD_UI_ELEMENT_REFERENCE |
|
No |
|
I |
0 |
Yes |
|
WDY_BOOLEAN |
true |
Yes |
|
Translatable text |
|
Yes |
|
WDUI_VISIBILITY |
visible |
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:
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 |
CONTEXT_MENU_BEHAVIOUR |
WDUI_CONTEXT_MENU_BEHAVIOUR |
|
contextMenuBehaviour: inherit |
CL_WD_TIMED_TRIGGER=>E_CONTEXT_MENU_BEHAVIOUR-INHERIT |
|
contextMenuBehaviour: provide |
CL_WD_TIMED_TRIGGER=>E_CONTEXT_MENU_BEHAVIOUR-PROVIDE |
|
contextMenuBehaviour: suppress |
CL_WD_TIMED_TRIGGER=>E_CONTEXT_MENU_BEHAVIOUR-SUPPRESS |
|
CONTEXT_MENU_ID |
WDY_MD_UI_ELEMENT_REFERENCE |
|
DELAY |
I |
|
ENABLED |
WDY_BOOLEAN |
|
TOOLTIP |
WDY_MD_TRANSLATABLE_TEXT |
|
VISIBLE |
WDUI_VISIBILITY |
|
visible: none |
CL_WD_TIMED_TRIGGER=>E_VISIBLE-NONE |
|
visible: visible |
CL_WD_TIMED_TRIGGER=>E_VISIBLE-VISIBLE |
|
Dynamic Programming of Events
View Designer Name |
Runtime Name |
ON_ACTION |
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 TIMEDTRIGGER.