Skip to Content

This blog is for portal content administrators who would like to learn about the change in Home page personalization in Enterprise Portal 7.5 SP5 for FLP on EP. It contains also example of common scenarios.

Background:

Before NetWeaver 7.5 SpS05 a user had only one Fiori Launchpad because a user can have only 1 personalization across FLP desktops, and the personalization of the Fiori Launchpad was defined separately for each device in use.

Starting from NetWeaver 7.5 SPS05, end user personalization data is stored separately for each Fiori desktop in use and not for each device group. This enables customers to have several desktops in parallel for same user in different scenarios: desktop/mobile, external/internal or different kinds of Portals differ by content and/or look&feel

 

What happens after you upgrade to SAP Enterprise Portal 7.5 SPS05 or higher?

As the user personalization in saved in the User Content Directory (UCD), before 7.5 SPS05 the personalization was located under the device type level . In 7.5 SPS05 and higher the UCD structure is changed and the personalization is located under desktop ID level . When a company upgrades to NW version 7.5 SP05 or higher, Home page personalization data will be migrated seamlessly from the old personalization structure to the new one.

How does personalization data migration work?

1.For existing users from previous version:

  • The migration happens in run time. It will be triggered in the first login for each combination of user/desktop.
  • The migration process copies the personalization data from the device type level to the Desktop ID level.
  • The device in used in the first login will determine which device type personalization to migrate.

2. For the new users, new personalization will be created on the UCD on the Desktop ID level (according to the new structure).

Best Practice

Cross-Device Personalization:

What is it?

Enable working with one or more mobile devices with the same personalization for all the devices.

Preparations:

The administrator using display rules should maintain one Fiori Desktop for all device types.

Cross device Personalization example:

Your company  work with FLP on EP 750 SP04:

  • End-User ID: user1
  • Fiori Desktop ID: FLPDesktop_FLP1 (Alias = FLP1)
  • Device types is use: Desktop, Tablet , Smartphone

Your home page looks as following:

  • EP Version is updated to EP 750 SP05
  • You use one Fiori desktop for all the devices: FLP1

User1 logs in for the  1st time after the version update using:
Device =Tablet
Fiori desktop = FLP1

Results:

  1. Tablet personalization is migrated from device-type “Tablet” to desktop level under Fiori Desktop FLP1
  2. The homepage content is adapted to the device type and will look like this:

User 1 logs in for 2nd time using:
Device = Desktop
Fiori Desktop = FLP1

Results:

  1. No migration happens, as it was done already in the 1st login
  2. Homepage layout will stay as in previous login
  3. “Tablet only” tiles will be filtered out. Other tiles will still appear.
  4. The homepage will look like this:

User1 runs Update home page from Option menu
Results:

  1. “Desktop only” tiles will be added to the homepage.
  2. The homepage will look like this:

User1 logs in the 3rd time using:
Device = Smartphone
Same Fiori Desktop = FLP1.

Results:

  1. No migration happens, as it was done already in the first login
  2. Homepage layout will stay as in previous login
  3. “Desktop Only” tiles will be filtered out. Other tiles will still appear
  4. The homepage will look like this:

User1 runs Update home page (see Home Page Update Mode )


Results:

  1. “Smartphone only” tiles will be added to your homepage.
  2. The homepage will look like this:

Note:
log-in again with one of the  device type used above will not requires anymore running Home Page Update Mode to reflect the device tiles.

 

Personalization per Device:

What is it?

Enable working with more than one mobile device with different personalization per device.

Preparations

Administrator, using display rules should maintain a separate Fiori desktop for each device type.

Personalization per Device Example

Your company work with FLP on EP 750 SP04:

  • End-User: user1
  • Devices is use: Desktop, Tablet, Smartphone

The home page looks as following:

  • EP  version is updated to EP 750 SP05
  • 3 new Fiori desktops were created , one for each device:FLP-Desktop, FLP-Tab, FLP-Smart

User1 logs in for the 1st time after the version update using:
Device = Tablet
Fiori Desktop = FLP-Tab

Results:

  1. Tablet personalization is migrated from device-type level to desktop level under Fiori Desktop FLP-Tab
  2. The homepage will look like this:

User1, logs in for the 2nd time using:
Device = Desktop
Fiori Desktop = FLP-Desktop.

Results
:

  1. Desktop personalization is migrated from device-type level to Desktop level under Fiori desktop FLP-Desktop
  2. The homepage will look like this:

User 1 logs in for the 3rd time using:
Device = Smartphone
Fiori Desktop = FLP-Smart

  1. Desktop personalization is migrated from device-type level to Desktop level under Fiori desktop FLP-Smart
  2. The homepage will look like this:

 

Important notes:

  1. Personalization migration will happen only once for combination of user ID and Desktop ID.
  2. Personalization migration will happen for each user separately.
  3. Cross device scenario requires update home page action in the first login of each device.

 

Fiori Launchpad UCD Cleanup Tool

Due to the change in the UCD structure, redundant entries related to the device types remain. With the Fiori Launchpad UCD Cleanup Tool administrator can clean up the redundant UCD entries and save unnecessary space which may impact performance.

 

More Info

SAP Help library links

What’s New in SAP NetWeaver 7.5 Sp05 (Release Notes)

Fiori Desktops and Personalization.

Related Notes

2340301 – Personalization data migration when upgrading to SAP Enterprise Portal 7.5

2337299 – Fiori Launchpad UCD Cleanup Tool

2301261 – Enhancements in FLP on Portal NW750 SPS05\

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply