How-to-guide: Provide navigation for your custom app or extension
Hi all,
I have seen numerous guides on how to use the webide to extend standard fiori apps. However none of the guides i have seen so far shows how to actually get the extended app into the launchpad. So i thought i would share this with you in case you were in doubt.
You could just replace the navigation inside the launchpad in LPD_CUST. However my approach should be considered a bit more best practice as we aren’t messing around with SAP created stuff.
I assume that you have already extended a fiori app, otherwise have a look at these guides.
So after you have done your extension you first of all need to deploy your project back to the gateway server. You can ifnd it in transaction SICF after this is done.
You now need to document the path to the app, in my example /sap/bc/ui5_ui5/sap/zpo_track_ext and then head to transaction SPRO.
Under the SAP Fiori menu in the IMG choose Define semantic objects for navigation
Click the new entries and give the semantic object a name that resembles what it is being used for. I was lazy and named mine zpurchase.
Afterwards click the SAP Fiori Launchpad designer, choose current or cross client depending on your scenario.
Now create a new catalog by pressing the + button.
Name the catalog something meaningful, again i was lazy and used zpurchase for both name and id.
Now click the + tile to create a new tile and choose the app launcher static
Add your newly created semantic object and give some information about your app and find a proper icon.
Click save and then head to the target mapping. You still need to handle the navigation from the tile to the actual app.
Press the Create Target Mapping and add the details from your semantic object as you have just entered them in the tile. Also you specify the target as a SAP Fiori app and add the path copied from SICF into the URL. Also you need the component name. You can find this in your component.js file
Afterwards your target mapping should look something like this.
Optionally you can create a group also for easier adding into the launchpad.
Last thing to do is to add your catalog and your group into a role in transaction PFCG.
Click the menu tab and select SAP Fiori tile catalog
Find your catalog and also add your group if you have created one.
Now all that is left is to test your newly created tile from the launchpad.
For extended app, intent(semantic object+action) should be same as the original intent, because other standard app may call other app with predefined intent.
For example, a purchaser opens "Open Purchase Order" analytical app, then navigates to "Track Purchase Order" transactional app. You expect your extended "Track Purchase Order" app comes up. Target mapping and application alias handle the logic to bring up your extended app.
Thank you for your posts so far. They've been very helpful. I wonder if it's possible to keep a standard app and an extension of this standard app in the same launchpad with working intent for both. I.e. the navigation of related apps of the standard app should still work for the standard app but for the extension of the standard app too. Is this possible?