Hello,
I have a rather annoying issue with Intent based navigation from one UI-technology to another.
We use the Netweaver Business client (7.70 PL 10).
system is S/4Hana 1610 (yeah, I know. it's old)
We have FES 6.0 with UI5 1.71
We start...
UI5 really sets itself apart by the heaploads of documentation and the many examples. Most of us use SAPUI5 to build applications, components and controls to use in a Fiori Launchpad for our customers. And that's where SAP has a blind spot. There are...
intro
When building large and complex UI5 apps, you will probably at some point start creating reusable components which you embed in a container app. The advantage of such a reusable component is that you can repeatedly use it in several apps. For m...
With more than 2 months to go, the event is fully booked and there is a smashing speaker line-up. If you're not registered yet and you really really really want to come, just contact us and we can work things out. Find the announcement blog here: h...
I'm currently working on a massive project for asset management in an offline UI5 application. Much of the framework and applications had already been created before I joined the project, and much more fixes and patches have been applied since.
This...
Hi Alexey,the point is that when I use "Explace" navigation (which is default), it doesn't work as expected.We want it to be "explace". That's our preference. But it doesn't work as expected.Here's the scenario with explace navigation: notice how the...
Welp, I found "a" solution...By setting the WDA_inplace_navigation to true, the POWL opens embedded on the launchpad so that it's not the initial navigation and doesn't fall into that quirky navback routine...Now I'll have to check if this is accepta...
root-cause:It all seems down to these handfull lines of code. When I debug the "isInitialNavigation" to return false, it all works as it should. But since it's an explace navigation to begin with, it always returns true.I feel like this should also c...
Interesting, If I add parameter sap-keepalive in the catalog configuration, it follows a different route through the applifecylce and does not trigger an exit-application, but it still navigates back home....So no solution yet, but at least I'm start...