Fix Fiori application to an old SAPUI5 version while upgrading the gateway to a newer one

[Former Member]

Hi All,

Is it possible to fix a custom Fiori application (which is started from the Launchpad) to a specific SAPUI5 version? We have an custom application which is currently tested and working with SAPUI5 1.26.1. Is it possible to fix this application to always run on 1.26.1 and upgrade our gateway to SP14 (SAPUI5 1.28) or later versions? This is easy when the application is standalone (started from index.html), but the question is could this be done when the application is started from a Launchpad tile?

Thanks in advance!

Best regards,

Luben

[WouterLemaire · Accepted solution]

Hi Luben,

Normally you can define the version in the SAPUI5 bootstrap by changing the SDK source. You can change the version in the url:

/sap/public/bc/ui5_ui5/1.26/resources/sap-ui-core.js

As you already mentioned, this is easy when to app runs standalone. But when it's started from the Fiori launchpad it will not go to the index.html, instead it will start from the component.js .

You can try to configure the SDK in the component.js metadata:

"sap.ui5": {

  "_version": "1.1.0",

  "rootView": {

  "viewName": "com.view.main",

  "type": "XML"

  },

  "dependencies": {

"minUI5Version": "1.30.0",

  "libs": {

  "sap.ui.core": {},

  "sap.m": {},

  "sap.ui.layout": {}

  }

  }

If that doesn't work, I would try to create a fiori tile based on the full url and not on a semantic object or launchpad configuration.

The last one will be the easiest way

Kind regards,

Wouter

[Former Member · Accepted solution]

Hi Wouter,

Thank you very much for your answer! We already have a fiori tile which opens the full URL so I guess we will stay with this solution and will define the SAPUI5 version in index.html

I will do some research about the component.js application descriptor although we need "maxUI5Version" parameter which is not available.

Best regards,

Luben

[Former Member · Accepted solution]

Hi Luben & Wouter,

I need exactly this parameter "maxUI5Version", not "minUI5Version"... to fix a maximum version for libraries working with a custom project.

We are not able to create your workaround, creating a new Tile and calling the full URL...

I guess "maxUI5Version" doesn't exist, right? Any other workaround?

Thanks!

Miguel Angel.

[Former Member · Accepted solution]

Any workaround for this issue?

[dominik_auras · Accepted solution]

I think this is a very critical point because "standalone" app tiles open in new tab and our customer is not happy with this.

So, any solutions for this?!

[Former Member · Accepted solution]

minUI5Version

: Minimum version of SAPUI5 that your component requires; this information helps you make sure that the features of the SAPUI5 runtime version of the component are available. AsSAPUI5 does not currently enforce use of the correct version, the

minUI5Version

is used for information purposes only.