Better alternative than "URL" as executable type for Standalone UI5 apps on Solution Documentation?

[thalesvb]

Hi all, here is a open question to throw your dimes (no clickbait intented).

I was putting some new (on premises) developments data into Solution Documentation, then I have this standalone UI5 app that I want to register there. It was deployed on a ABAP stack system that is part of Solution Landscape.

For Launchpad plugins I was using BSP application type to have a reference where it was deployed, but BSP application type is not quite right for standalone UI5 apps since SICF BSP node for it is disabled (as we have to use that on ui5_ui5 path). This app is to be standalone: no Fiori Launchpad, no Catalog, so no Object/Action keys.

I spent some time fiddlig with available app types. Current winner for me was URL type but it have a flaw: URL is hardcode for a specific system, and defeats the purpose of having a Logical Component Group, as I intend to put some additional automated tests on it later and app URL should point to Development/QA according as selected SUT for testing.

How are you documenting standalones apps on SolDoc?

Best regards

[odedd]

Hi,

Yes I have encountered the exact same challenge in SOLDOC. Currently no alternative to UI5 URL is available. So I as no LCG works, have set up a separate URL executable for every client/system : URL- DEV/120, URL-DEV/130, URL-QA/120 etc. (in order to make them available for testing.....)

We definitely need mush more support for UI5 & FIORI development in SOLMAN. As there will not be any INFLUENCE session in 2020, I hope someone takes notice.....

Regards,

Oded Dagan