on 2024 Jul 16 8:45 PM
There are many good blogs/docs about key user UI Adaptation at Runtime to customize Fiori apps and create variants, and many good blogs about developer Adaptation projects in BAS at Design time.
But which method is preferred?
Assuming only developers will be making customizations (not key users) and no additional controller logic extensions are needed, which method should be used?
Runtime Adaptations are easier with less overhead. But I'd like to see what other people think.
Thanks
This is a great question! As you rightly noted, when it comes to implementing uncomplicated UI extensions— be it adding or removing fields, setting default views, renaming labels or titles, rearranging elements, simplifying the UI or introducing mashup content—the use of Key User Adaptation is allowing to avoid overhead of development and thus is highly recommended.
So, even developers or IT specialists are encourage to extend via key user adaptation and expedite the process from requirement to go-live, thereby minimising delays usually associated with development projects.
Despite it's simplicity focusing on adapting for all end users, key user adaptation also supports extending UI for specific user roles in SAP BTP ABAP environment or, by creating application variants and assigning them to different roles, in S/4HANA.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
73 | |
10 | |
8 | |
8 | |
8 | |
6 | |
6 | |
6 | |
6 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.