Cross-App Navigation : Navigate from one Fiori app to Another

There is mechanism available in Fiori to navigate from one application to another application using Fiori extension (CrossApplicationNavigation service).

Developing Navigation to Another SAP Fiori App

In this article we will talk about how to achieve cross-app navigation using CDS view.

Configuring Navigation

An intent is a mechanism that allows users to perform actions on semantic objects (such as navigating to a sales order or displaying a fact sheet), without worrying about the UI technology or technical implementation of the navigation target.

Intents are comprised of the following parts:

Semantic object : Represents a business entity such as a customer, a sales order, or a product. We can either use semantic objects shipped by SAP, or create new semantic objects.

Action : Describes which operation (such as display or approvePurchaseOrders) is intended to be performed on a semantic object (such as Purchase Order or Product).

Semantic object parameters: Define the instance of the semantic object (e.g. by specifying the employee ID).

Lets take an example to navigate from custom list report (which displays purchase order information ) to standard Purchase order Fiori application.

Custom List Report

Requirement : Purchase order should get open in display mode if user clicks on any of the purchase order.

Let us first find out the semantic object details of target application i.e. Purchase order display through Fiori application library.

Now search desired target application.

Go to Implementation information tab >> Configuration

Here we can find out semantic object details .

Semantic Object : PurchaseOrder

Semantic Action : Display

We need to use these details in our CDS consumption view to navigate to target application.

@Consumption.semanticObject: 'PurchaseOrder'
@UI.lineItem: [
{ position : 10, semanticObject: 'PurchaseOrder' , semanticObjectAction: 'display',
  type: #WITH_INTENT_BASED_NAVIGATION, value: 'PurchaseOrder' }
]        

we can use the following dataField types to include navigation concepts:

• #WITH_NAVIGATION_PATHUsed for navigation within an application.
• #WITH_URLUsed for navigation from an application to an external web site.
• #FOR_INTENT_BASED_NAVIGATIONUsed for navigation based on an action that is related to a semantic object.

Lets open the application.

Its visible that Purchase Order no has hyperlink that is holding URL to navigate to Purchase order display application.

Note: Navigation will only work if application is deployed, in this example we have not deployed the application but viewing in pre-view .

We can always refer this link for more information.