![]() ![]() The pace in which SAP introduces new controls and approaches will make any UI5 app look ridiculously old after just three years (or so) of its issuing. One may think the resulting UI5 app will hold for the next 3-5 years. Like any newly developed code, it’s exposed to bugs and data errors for quite a long time until it reaches maturity. ![]() No, we are talking about a brand new object composed of a new UI, a new ODATA service, and a new set of back-end methods. One may think the resulting UI5 is a clone of the original report. That process, its UI, along with the supporting code, must be rewritten. Every legacy SAP GUI process, which is converted to a UI5 app, must be revised. When developing a new UI5 app, the old SAP GUI processes are not reusable. UI5 Technology leads to a reduced need for development and improved mobile work capabilities. Somebody can do this by enabling customers to enhance their existing ABAP-based reports and expose them as UI5 apps. The author suggests seeking tools to keep the extensive investments in SAP made by both SAP and its customers. The development of new UI5 apps is a costly and time-consuming project. ![]() We must use tools that keep the extensive investments in SAP made by both SAP and its customers. Developing new UI5 apps is costly and time-consuming. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |