Both output and input elements can be logged, but they must be context-bound UI elements.
UI elements that are generated automatically (for example, when using F4 Help) can be logged. They do not need to have a UI element ID assigned during application development. In these cases, a temporary ID is assigned during the recording.
The table below shows all UI elements that can be logged in Web Dynpro applications. It shows the properties that can be recorded for each UI element.
UI Element |
Property |
---|---|
|
Value |
|
Text |
|
Value |
|
Text If value suggest is active, all proposed texts for this UI element that are displayed on the UI are logged. |
|
Value If value suggest is active, all proposed texts for this UI element that are displayed on the UI are logged. Historical values are not recorded. |
|
Value |
|
Texts |
|
Text |
|
Text |
|
Text |
|
Texts |
|
Text |
|
Text |
|
Text |
|
Text |
|
Text |
|
Text |
|
Text |
|
Text |
|
Text |
|
Text |
|
Text |
|
Text |
|
fileName, mimeType, text, data |
|
Title |
|
Text Selected Key |
|
Text |
|
Selected Key |
|
Text |
|
Text |
|
Text |
|
Selected Key |
|
Selected Key |
|
ItemText ItemDescription Texts |
|
ItemText ItemDescription Texts |
The constituents of the following multiple UI elements can be logged with Read Access Logging:
-
Table
-
CTable
-
RowRepeater
-
MultiPane
-
Accordion
andMultiAccordionItem
Related Information