How to Map a Traditional SAP Enterprise Portal Hierarchy to Fiori Launchpad

[Former Member]

This blog is for portal administrators who would like to implement Fiori Launchpad in their organizations.

Motivation:

The existing L-shape hierarchy has several drawbacks:

• It takes a number of clicks to get to the required application
• The navigation logic is not easy to memorize
• To easily find the required object a user has to be familiar with the hierarchy structure.

Fiori Launchpad provides a flat structure with the following:

• Personalization: allowing the user to organize the homepage as he wants.
• Search and filtering functionality.
• A required application can be found and launched in one click without screen navigation.

Challenges:

The traditional portal L-shape hierarchy has to be mapped into Fiori Launchpad structure.

Prerequisites:

• SAP Enterprise Portal (EP) 7.31 SP 16 and higher or SAP Enterprise Portal 7.4 SP 11 and higher
• Fiori Launchpad on Portal (FLP on EP) is enabled

Fiori Launchpad navigation paradigm:

Fiori Launchpad consists of 2 pages: Homepage and Tile Catalog page.

Home page is controlled and personalized by an end-user. A user can create/delete a group, fill a group with content or remove content from the group.

Tile Catalog page serves as a repository for the entire content assigned to the end-user via EP roles.

The content is provided in the form of tiles, which have a number of properties used for navigation and identification:

• Category
• Name
• Subtitle
• Keyword
• Promotion properties: New, Recommended.

FLP on EP provides various search and filtering possibilities, on both Homepage and the Tile Catalog.

Both pages have a header line with the Quick Launcher and Fiori Search Application functionality:

• Quick Launcher (search by tile title)

The search searches for the tiles in the entire Fiori Launchpad content (Homepage and Tile Catalog) by the tile title. By clicking the selected entry from the drop down list you can run the application directly.

Example: tiles from Homepage and Tile Catalog are found

• Fiori Search Application (search by tile title, subtitle, info and keyword properties)

With the same search criterion as in Quick Launcher there are more results now as subtitles and keywords are also used:

Note: first enter a search criterion into an entry field and only then click on the magnifying glass.

On the Tile Catalog page the content can be filtered by category:

Or by tile title, subtitle, info and keyword in the right input field:

Or by combination of both.

On the Homepage the navigation can be done by clicking on the group in left-side menu. Then the group is moved to the top of the screen:

Mapping principles:

The traditional EP navigation hierarchy has unlimited hierarchy levels whereas FLP hierarchy is limited.

For mapping the meaningful part of the navigation context should be identified and used in the new environment as the categories and information on the tiles. (Note that parts of the navigation structure may be omitted)

This context information will help to find and navigate to the needed tile and to identify the required application.

Mapping Example:

As an example we take Standard MSS (Manager Self-Service) SAP provided content and see how it might look like on FLP on EP.

Traditional Portal hierarchy:

Let’s look closer on the hierarchy:

FLP on EP representation of MSS content:

• Tile Catalog:
  

• Homepage:

Steps to transform to FLP (an example)

1. Create categories in Portal Content ->Portal Users->Standard Portal Users->iViews->Fiori Launchpad->Fiori Launchpad Categories. Use concatenated values of Hierarchy Level #1 and Hierarchy Level #3, e.g. Manager Self-Services – Team

2. Change iView or Page properties as following:

• Set Assigned Category  to a created category
• Set Subtitle to Hierarchy Level #4, e.g. General Information
• Set Object ID of Device Group to the list of supported devices groups or devices
• Set Keyword to any hidden search criteria that can use in Tile catalog and Homepage search

 

The result for our example looks like this:

For mass update of several iViews a mass editor can be used. This editor allows “Changing Property Values of Multiple Objects”.

After the mapping is finished both structures co-exist in EP: the unchanged L-shape and Fiori Launchpad providing a new user experience for the same EP content.