Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
GregMalewski
Contributor
2,276

This blog post should interest you if you know the Reasons to document Fiori Launchpad configuration externally and Reasons to use a tool to document Fiori launchpad.

The blog post explains how to document your Fiori Launchpad configuration using a free Fiori Tracker tool (Apache License 2.0). Fiori Tracker is available to anyone for download and installation. Once installed in your system, you can start documenting your SAP Fiori launchpad contents.

To start documenting your applications and catalogs together with links between them, you need to install "Fiori Tracker Core," which brings two new Fiori applications to your launchpad:

    1. FT Applications (with relation: To-be catalogs) – for keeping "To-be" records of applications in scope

 

    1. FT Catalogs (with relation: To-be apps) – for keeping "To-be" records of catalogs in scope



 

Fiori Tracker Core group tiles



Documenting Fiori launchpad-enabled applications


First, you need to record all applications you plan to enable in your Fiori launchpad. You do that with the “FT Applications” app. The app starts with the current list of all applications in your project scope (for starters you can list custom apps only). Whenever you add the application to your records, we recommend identifying it using the designations from the SAP Fiori library: for standard apps, App ID from Fiori library, custom, and extended apps get IDs starting with Z or Y.

 

Starting view of the “FT Applications” app


With the "Add" function, you can add a new application entry:

 

Create an application record form in the “FT Applications” app


The recorded details include the following:

    • App ID – The application prevents the creation of duplicates.

 

    • Tile title – The title might be different from the official application name.

 

    • Name – Contains the official application name.

 

    • Area – You can choose a functional area. The area comes from the configurable list of areas specific to your project.

 

    • Type – You can choose the type of application. The choice comes from the list of configurable types specific to your project. Fiori Tracker comes with predefined application types.



Technical catalog, Semantic object, action, and flags indicating if the app can start directly and is a lighthouse app is optional. They either serve as additional information, or you can use them after installing optional Fiori Tracker suite components.

Documenting Fiori launchpad catalogs


Once you finish with applications, you can create documentation entries for your launchpad Business Catalogs. The app to manage catalogs is called "FT Catalogs" and starts with the list of the catalogs in the project scope:

 

Starting view of the “FT Catalogs” app


Add button creates an entry for the new catalog:

 

Create catalog record form in the “FT Catalogs” app


The app uses the same functional area set to assign catalog and Fiori Tracker reports on a specific stream or assign a stream default person responsible for sing-offs.

Maintaining mapping between catalogs and applications


Once all catalogs are in, you can map applications to catalogs. You can do that from a catalog perspective by opening the chosen catalog detail view and its "Applications To-be" relation and selecting "Edit":


View with a chosen catalog record and its “Applications To-Be” relation in the “FT Catalogs” app

 

Edit view for mapping application in “FT Catalogs” app

 

All marked apps get assigned to the catalog. In the same way as for catalogs, the mapping function is available from an application perspective:

 

 

Edit view for mapping catalogs in the “FT Applications” app


These two apps will significantly reduce the time the project and support team need to agree on and handle the launchpad catalogs and their apps. In addition, optional components link the application and catalog to other information records like roles, test users' passwords, sign-off records, or application usage data.

I’m curious to hear your opinions on using Fiori Tracker  – feel free to comment, contact me on Linkedin, or discuss on Discord with others using Fiori Tracker.

I hope I have inspired you to give Fiori Tracker a go, and I wish you all the best in keeping your SAP Fiori launchpad team and users happy.

You can download and learn more about Fiori Track on its help page: https://fioritracker.org/.

You can integrate the Fiori Tracker with the Fiori Apps Usage Report which will give you the application start count for each of your Fiori apps. You can read more about it in Apps usage report for SAP Fiori launchpad (Monitoring SAP Fiori applications).

4 Comments
Labels in this area