AcfExecute
If the WDLIGHTSPEED parameter is active, AcfExecute starts an external application such as Notepad or Paint in A Web Dynpro application.

Note that the integration of AcfExecute in Web Dynpro ABAP dialog boxes (popups) is not supported.
See SAP Note 1178747
Like for OfficeControl methods can be executed; the CL_WDR_ACFEXECUTE_HNDL ACF method handler is required for this.
Unlike other Web Dynpro ABAP UI elements, AcfExecute is implemented in a way that means the action can only be triggered by a method call. For AcfExecute, the Execute action only takes place if an IF_WD_ACFEXECUTE~EXECUTE method call occurs.
Since rendered pages are normally displayed in a Web browser connected to the Internet in Web Dynpro, security aspects must be considered for UI elements like AcfExecute. This is especially important due to the generic structure of AcfExecute.
There are therefore the following security measures for AcfExecute.
● AcfExecute only communicates with authorized servers.
● Only authorized executables on the client PC are triggered.
● Data can only be stored in authorized directories.
● Data can only be read from authorized directories.
The authorized servers and directories are listed in a white list (an administrator stores this information locally using transactions WDR_ACF_WLIST and ACF_WHITELIST_SETUP). If requests for access to directories or communication with servers are sent using HTTP or HTTPS, the control first checks whether this is allowed at all. It then compares the directories or servers in question with the data in the local white list file. It only executes the relevant methods if the authorization is set in the white list.
For more information see the SAP Reference Implementation Guide (IMG). In transaction SPRO, choose Display SAP Reference IMG. The path in the Implementation Guide for SAP NetWeaver is: Application Server ® Web Dynpro ABAP ® Set Up Whitelist for Active Controls and Activate Whitelist for Active Controls.
Runtime Class |
CL_WD_ACF_EXECUTE |
Properties in the View Designer
Name |
Type |
Initial Value |
Bindable |
ID |
STRING |
(automatic) |
No |
STRING |
|
Yes |
|
STRING |
|
Yes |
|
WDUI_CONTEXT_MENU_BEHAVIOUR |
inherit |
No |
|
WDY_MD_UI_ELEMENT_REFERENCE |
|
No |
|
WDY_BOOLEAN |
true |
Yes |
|
STRING |
|
Yes |
|
Translatable text |
|
Yes |
|
WDUI_VISIBILITY |
visible |
Yes |
|
STRING |
|
Yes |

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 |
ARCHIVES |
STRING |
|
CLASS |
STRING |
|
CONTEXT_MENU_BEHAVIOUR |
WDUI_CONTEXT_MENU_BEHAVIOUR |
|
contextMenuBehaviour: inherit |
CL_WD_ACF_EXECUTE=>E_CONTEXT_MENU_BEHAVIOUR-INHERIT |
|
contextMenuBehaviour: provide |
CL_WD_ACF_EXECUTE=>E_CONTEXT_MENU_BEHAVIOUR-PROVIDE |
|
contextMenuBehaviour: suppress |
CL_WD_ACF_EXECUTE=>E_CONTEXT_MENU_BEHAVIOUR-SUPPRESS |
|
CONTEXT_MENU_ID |
WDY_MD_UI_ELEMENT_REFERENCE |
|
ENABLED |
WDY_BOOLEAN |
|
HEIGHT |
STRING |
|
TOOLTIP |
WDY_MD_TRANSLATABLE_TEXT |
|
VISIBLE |
WDUI_VISIBILITY |
|
visible: none |
CL_WD_ACF_EXECUTE=>E_VISIBLE-NONE |
|
visible: visible |
CL_WD_ACF_EXECUTE=>E_VISIBLE-VISIBLE |
|
WIDTH |
STRING |
|
You can find an example of this UI element in the system in the SWDP_TEST_ACTIVE_COMPONENT package in the WD_TEST_APPL_ACFEXECUTE component.