In the previous posts the focus was on backend services, with the main advantages that all Hana objects are exposed with zero configuration and yet secure. But these backend services are just a necessity, the actual goal is to build UIs times faster than with SAP provided tools.
Here is the video on how this screen was build including adding the SAP Hana data. The video shows every step needed – or to be more precise – what all is not needed thanks to the HanaAppContainer.
The advantages of this approach cannot be overrated. It is one of the most difficult tasks to make the business users aware on how expensive it is to design a UI strictly according to their needs. But with this tool the business user can design the UI himself and all that is left for the IT team is to wire up the actions between the controls.
From a technical point of view the UI Editor edits the XMLView definition in a graphical way. IT can read XMLView files, it writes such when saving. All other code needed for an SAP UI5 applications, the html file, controller file etc follow the principle: if no physical file is present build a default on the fly.
For that reason, at the end of the video the page MyView.html is opened although it was never created. This file does not exist and hence a default is returned by the HanaAppContainer backend presenting the MyView.view.xml and its controller to instantiate all used oData models.
Give it a try, the docker image is available at docker hub – see other posts