SAP Fiori Launchpad on Portal – Sample Content for Administrators
This blog is for portal content administrators who would like to learn about the administration tasks required for enabling SAP Fiori launchpad on Portal (FLP on EP). It contains pre-configured sample content that you can import into your portal. In only a few steps you can easily run the SAP Fiori launchpad experience within the SAP NetWeaver Portal environment.
SAP Fiori launchpad on Portal is available for portal customers as of NW 7.31 SP12 and NW 7.4 SP7. It is highly recommended to update to EP latest patches before running FLP on EP in order to get the most updated version.
With FLP on EP, portal users can control which applications appear in their launchpad on mobile devices and on the desktop. Portal iViews appear as tiles in the launchpad and access to content is based on portal roles, per device. Administrators can configure content to appear by default in the home page for all users and tag content as New and Recommended.
SAP Fiori launchpad on Portal provides the following capabilities:
- The ability for administrators to configure content for different devices.
- A dedicated framework page for displaying the SAP Fiori launchpad.
- Access to the tile catalog containing the content that users can add to their home page.
- The ability to save personalization per device.
Let`s get started:
1) In versions NW 7.31 SP12, NW 7.31 SP13, NW 7.4 SP7 and NW 7.4 SP8, create a URL alias and add it together with the Fiori desktop to the Master Rule Collection:
a) Create a new URL alias using the URL Alias Manager:
b) Add the alias together with the Fiori Desktop to the Master Rule Collection:
Starting NW 7.31 SP14 and NW 7.4 SP9, the URL alias “portal/Fiori” is already maintained in the URL Alias Manager. Only required to add the rule in the Master Rule Collection. For details see SAP Note 2042363.
2) Define the relevant device types using the Device Group Manager:
3) Import the OOB_Admin.epa file located in Out of the Box FLP-EP Admin Content, using the Transport Packages import tool.
This transport package contains the following:
a) Fiori Launchpad Categories iView – Manages categories in the tile catalog. Administrators can create categories to group applications in the tile catalog. The iView is configured with sample categories:
b) A role for assignment to users, containing iViews that are configured to demonstrate the different properties available for FLP on EP, and web resources for the tiles:
In order for the content to be visible in the home page and tile catalog, set a container in the hierarchy as entry point (role, workset or folder). Make sure that the iView is set to visible.
4) Work with the iViews and different properties to manage the content for FLP on EP. The following properties are available on each iView, allowing you to configure tiles according to your requirements.
Note: The iViews in the sample content has already been configured to highlight the various capabilities of FLP on EP.
- Mandatory: Set the device groups on which the application will be displayed using the property “Object ID of Device Group“. Separate the device groups with a semicolon (;). If this property is not set with any device group, the tile will not appear at all.
- Set the categories in which the application will appear in the tile catalog using the property “Mobile App Categories“. Separate the categories IDs with a semicolon (;). If this property is not set with any category ID, the tile will appear under the General default category.
- Mark an application as default using the property “Permanent in Launcher” to make it appear in the user’s home page the first time that the user logs in. Users can remove default applications from their home page. If this property is set to “False”, the application will only appear in the tile catalog.
- Set an image on the tile using the property “Image Type“.
- Promote applications in the tile catalog:
- Set property “Mark as New Until“.
- Set property “Mark as Recommended Until“.
- Indicate a native application using the property “Native App“. If this property is set to “True”, the application will only appear in mobile devices (even if the device type is set to desktop).
Here are some examples of configured properties on the iViews from the Out of the Box FLP-EP Admin Content:
Without making any changes to the sample content, this is how the user`s home page will look:
This is how the user`s tile catalog will look:
Now you can play around with the Fiori launchpad on Portal. Enjoy the new experience and let us know what you think!
To learn more about FLP on EP:
This is a scenario of FLP integrated on SAP Portal.
I am facing an issue in display of SAP Fiori Launchpad contents when being launched from portal Role (web-dispatcher portal url). I am getting the content as in below screen-shot. Please note that the same content is being launched properly when using direct web-dispatcher fiori launchpad url.
My EP version is NW7.4SP09 & FLP is NW7.4SP13
Please help in resolving the same, if anyone has faced similar issue earlier.
* Web-dispatcher is configured for integration scenario and we are able to access portal using same.
link to discussion: https://answers.sap.com/questions/228636/flp-content-not-displaying-properly-when-being-lau.html
Need your help.
How Shall I add UI5 icon to my Fiori tile Iview in Portal ? There is a property in Portal Iview called SAPUI5 Icon Name : , here I will give values as SAP-Icon://ImageName. From where this source image is being called, and where is the UI5 image library exists in Portal. Could you explain please.