After clicking on a tile in the SAP Fiori Launchpad, the background calculates the jump’s destination URL and returns it to the foreground.
The white boxes in the image below are called tiles. After each tile is clicked, a corresponding Fiori app opens.
This article describes how to debug the computing logic of the jump target in the background.
First we can click on the tile directly in the browser or manually trigger the url resolution request for the jump target with Postman:
In the handler class of the ICF node, set a breakpoint under HANDLE_REQUEST:
The request is triggered in Postman, the breakpoint is triggered, and the Fiori background system is executed from Fiori’s foreground system in line 61.
For the classification of Fiori front and back systems, please refer to my wechat public account article on three deployment modes of SAP Fiori applications
Background execution logic: first fetch metadata
Take the actual data. Here is the data request body:
Get the action name:
Then invoke the corresponding processing logic based on the action name:
First read from cache:
Cache dead:
So go to the database and get:
Get the result. The string cus. Crm. myCalendar after SAPUI5.Component= is the Fiori application to be opened after the tile click. The field URL value is the storage location of the BSP application corresponding to the application.
For more of Jerry’s original technical articles, please follow the public account “Wang Zixi” or scan the following QR code:
