Show TOC

Enabling Apps for UI Adaptation at RuntimeLocate this document in the navigation structure

To enable an app for UI adaptation at runtime, all controls in the app need to have stable IDs.

UI adaptation at runtime uses stable IDs to ensure that the adaptations that a key user made can be applied again, for example after the app is upgraded. Stable IDs are based on SAPUI5 static IDs and must not be changed to prevent inconsistencies or errors. For more information, see Support for Unique IDs.

Note When adapting UIs at runtime, the key user can only edit SmartForm and ObjectPage controls with stable IDs. For more information, see Smart Form and Object Page Layout.

Test and Productive System Recommended

As UI adaptations made directly in the productive system might interfere with transported changes, we do not recommend that key users adapt the UI in the productive system. Instead, they adapt the UI in a test system and then transport the changes to the productive system where all users of the app can access the adapted version. For more information, see Transporting Your Adaptations.

Prerequisites

  • You assigned the key user to the authorization role SAP_UI_FLEX_KEY_USER.

    Note

    If you want to define your own roles, make sure to copy the SAP_UI_FLEX_KEY_USER role and create them based on this role.

  • The key user has the required authorizations for transports.

  • You activated the ICF service /sap/bc/ui2/flp and ensured that the key user uses the new FioriLaunchpad.html page. For more information, see SICF Services.