Skip to Content
Author's profile photo Krishna Kishor Kammaje

Options to disable Fiori Personalization

Problem

Many a time we get requirements to disable Fiori Personalization. This mainly arises out of difficulty in supporting such users who have widely personalized their launchpad without any clue. Few examples are

https://launchpad.support.sap.com/#/notes/0002465437

https://archive.sap.com/discussions/thread/3532845

https://archive.sap.com/discussions/thread/3692065

So how to do it?

 

Solution 1

SAP’s standard documentation provides a solution below.

https://launchpad.support.sap.com/#/notes/0002520812

Problems with this solution are

  • If you specify the personalization file in the URL, you might have to inform all the users to use a new URL. If the users access the Fiori Launchpad without specifying the personalization file, they will still be able to do personalization.
  • If you refer to the personalization file in the Fiori Launchpad, that would be a ‘modification’. So whenever you upgrade, your modifications will be lost and you need to redo your modifications.

 

Solution 2

SAP ships a catalog with name /UI2/CONFIG_PERS_OFF. Assigning this to users will disable personalization to those users.

  • You no longer have to do the ‘modification’, so your changes are safe across upgrades.
  • Using Fiori config, you can decide which set of users have access to personalization.

 

Solution 3 (my favorite)

Another solution is to use Fiori Launchpad plugins and disable Personalization. This allows you to programmatically decide.

  • You no longer have to do ‘modification’, so your changes are safe across upgrades.
  • Using Fiori config, you can decide which set of users have access to personalization.
  • If the use case needs, you can programmatically decide to enable and disable personalization for a set of users.

Here is how to do it.

  1. Create a Launchpad plugin as specified in SAP documentation here. https://help.sap.com/viewer/webide-flpextensibility
  2. In the init function of the Component.js have these two lines of code.
//Diable Fiori Personalization
var renderer = sap.ushell.Container.getRenderer("fiori2");
renderer.getComponentData().config.enablePersonalization = false;

 

Note: Even though you have disabled personalization, current personalizations by the users still remain. To clear them, run /UI2/INVALIDATE_GLOBAL_CACHES in the Gateway server.

Assigned tags

      3 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Rohit Gupta
      Rohit Gupta

      Hi Krishna,

      I was trying for option no 2, but the catalog /UI2/CONFIG_PERS_OFF is not available in our system. Not sure it is because of FIORI version.

      Then I tried the third option, I created the launchpad plugin and put the code. In debugger i can see the value of enablePersonalization is changed to false but the personalisation option is still there.

      I appreciate your help here.

      Thanks.

      Author's profile photo vipul soni
      vipul soni

      I also tried but it also not work for me

      Author's profile photo Mynyna Chau
      Mynyna Chau

      Do you need help by the community? For the benefit of all SAP Community members having similar questions, please post your question here: https://answers.sap.com/questions/ask.html That way, your question is addressed with all related experts within SAP Community and your answered question can be found and be helpful for others in future.

      Have a look at our tutorial for asking and answering questions in SAP Community: https://developers.sap.com/tutorials/community-qa.html

      Best regards

      Mynyna (SAP Community moderator)