If you are adding a SplitApp template, you need to specify the position parent-property in the attribute section of your page controls. It is the starting page which is displayed when the app starts. The page control should be the first sub-node of your App/SplitApp control. It is possible to navigate from one page to another throughout the app. Hierarchically, all pages should be placed at the same level. The following design best practices are a recommendation and do not necessarily include all relevant guidelines for a project.Įvery app should start with the sap.m.Shell control, which is typically named oShell.Īs sub-nodes to the App/SplitApp control, it is recommended to define a set of sap.m.Page controls that determine the needed screens of your app. We recommend designing your apps as split-apps, based on the sap.m.SplitApp control. We recommend designing all UI5 apps stateless. It is also possible to deploy and run each DXP - SAP Edition app individually and standalone. On each app in every launchpad all existing SAP user roles of your SAP system can be applied. You can host multiple launchpads on one backend server. With a launchpad, it is possible to create an app ecosystem in which apps can call and open each other and pass data.Ī launchpad is configured in the Launchpad service in the Cockpit. It is also possible to integrate legacy UI technology through such tiles. By selecting a tile, users navigate to the corresponding app. The tiles on the launchpad represent navigation anchors to the individual apps. Single point of entry is the DXP - SAP Edition Cockpit, which is the home page and central location of all DXP - SAP Edition services. Neptune DXP - SAP Edition open source library usage.Neptune DXP - SAP Edition a Mobile Application Management.Non-technical Considerations when writing Offline Apps.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |