Best practice for App to App communication within Portal Service

[mihaileb]

I am trying to sort our the best solution for our customer to implement the way to refer to a UI5 application from a different UI5 application.

As of now, there is one UI5 application called “ app1”, which refers to functionality that is included in other UI5 applications. To do so, the applications builds the destination UI5 application url using the “Destination GUID” property, which is automatically generated for each applications when it is deployed into BTP .
So, for example to refer to the “common” application, “ app1” application uses the following url which includes the “Destination GUID”:
dev: "/0ffaea24-4c93-4b0d-8601-36d0f7ab62ed.common-1.0.0". Is this best practice to refer to an app by it's destination GUID. Is there another way? Thank you

[Ivan-Mirisola]

Hi bruno.mihailescu,

You can use the Cross Application Navigation service from the Launchpad in order to build Intent Based Navigation from one app to the other passing values as parameters. This is demonstrated here:

https://blogs.sap.com/2021/06/24/handling-startup-parameters-dynamically-in-sap-fiori/

Here is a blog with a more complex use-case:

https://blogs.sap.com/2021/05/24/enable-app-to-app-navigation-in-bas/

Best regards,
Ivan