Key-user adaptation
Changing a delivered app without modifying it — moving, hiding and adding elements as a layered set of changes that survive an upgrade.
Overview
@openui5/sap.ui.core The OpenUI5 core: the module loader, the MVC runtime, data binding, routing, theming and the test stack, which is everything a UI5 app does before a single community package is added.
No community artifact is documented here.
In ABAP key-user adaptation is what the system stores: changes and app variants from adaptation projects sit in the layered repository, table /UIF/LREPDCONT, one layer above the delivered app.
SAPUI5 flexibility services on the ABAP platform manage control changes and personalisation, and store them by layer in a layered repository.
Not covered: At the repository. An app variant's changes, fragments and i18n files are kept in the system, and taking them back out as project files is written on top.
The repository here is independent; how it relates to SAPUI5 flexibility services has not been assessed.
On BTP key-user adaptation is a service an application adds: UI flexibility serviceUI flexibility serviceKey-user adaptation and personalisation for UI5 applications on SAP BTP: UI changes, shared views, drafts and versions, stored by the service and applied at runtime.sap official, btp stores the changes a key user makes, as drafts and activated versions, and the views end users save, without affecting any other customer.
SAP ships key-user adaptation for UI5 applications on BTP as UI flexibility serviceUI flexibility serviceKey-user adaptation and personalisation for UI5 applications on SAP BTP: UI changes, shared views, drafts and versions, stored by the service and applied at runtime.sap official, btp: key users change the user interface at runtime with the original app untouched, and end users save personal settings, in an upgrade-safe and modification-free way without affecting any other customer.
Not covered: At supported controls: what a key user can adapt and what an end user can personalise both depend on the UI5 control.
No community artifact is documented here.
Artifacts
Content
Seen working
Details
Coverage
For your agent
- Ref
capability:ui5-flexibility- JSON
- /capabilities/ui5-flexibility.json
- MCP
- Connecting an agent