In this example from the SAP Fiori apps reference library, you see the technical name of the SAPUI5 application, the ICF-path, and the SAPUI5 component. The semantic object and action form the intent.
SAPUI5 apps may consist of multiple SAPUI5 components. One central component is the core of the app and represents the starting point. All other components are referenced or reused in this central component. The idea is that these other components consist of features and functions also valid or even needed for other apps. Therefore these component are called reuse components.
In the SAP Fiori launchpad designer (FLPD), the intent can be found in the target mapping of the catalog. The application type SAPUI5 Fiori App is set as target. The URL holds the ICF-path and the ID holds the SAPUI5 component.
LPD_CUSTwas the first way to map an intent-based navigation to the implementation of an app before the FLPD fully took over. URL and ID were defined in an LPD_CUST instance of an LPD_CUST role and referenced in the FLPD via an application alias.
An SAPUI5 app is saved as a Business Server Page (BSP) in the FES. The central file of an SAP Fiori app based on SAPUI5 is
Component.js. To start the app, the path to this file is visible in the statement
In this example, the BSP holding the SAPUI5 app has less files than usual. This is a sign for an SAPUI5 extension, which reuse other SAPUI5 components. This also applies if a customer extends an SAPUI5 app delivered by SAP. In this case, the extension only consists of the changes to the original app.
Checking the content of the
Component.js, there is no statement
jQuery.sap.declare. To start an SAPUI5 extension,
return U.extend provides the path to the