The generated application will provide a complete CRUD access to the data of the ODATA service which is behind the selected application of the SAP CP server. It includes the Fiori logon screens for onboarding to the server, the ODATA and Foundation libraries are used to consume the service. The structure of the application is based on a simple master-master-details view template, where on the top is a list of entity sets provided by the ODATA service, then navigating down the user gets into the list of entities of a given set. Finally, selecting one of the entity a details view is opened. On the relevant screens create, update and delete operations can be triggered. The application can handle push messages and log records can be uploaded to the CP server. These features are optional, which means that they are only present, if the corresponding check boxes were selected during generation.
At the first start of the application the following "Welcome" screen is presented.
Pressing "Get Started" will trigger the logon flow. The generated application can support basic authentication, OAuth, SAML or no authentication, according to the server settings. The code is generated according to authentication type of the consumed application, which was set on the SAP CP server. If the authentication type were basic then a user name – password dialog appears.
After providing the right credentials the application will receive the client-side policy from the server, which among others contains the required passcode policy. If it required that the application should be passcode protected then an enter passcode screen is shown. This screen contains information about the passcode complexity, as well. After a proper passcode was entered a verification screen will appear.
After the passcode were created the logon flow is finished, the application will show the entity set list which is accessible on the server. By clicking the menu in the top right corner the user can get to the settings sceen which offers the possibility of setting the log level, uploading the log to the server (these are optional features, which can be selected on the Wizard during application generation) and changing the application passcode.
After selecting one of th entity sets an other list is opened, which contains the entities of the collection.
The floating button on the bottom left corner can be used to create and add a new entity to the set. Clicking it a creation screen is presented. By tapping one or more items update and delete operations can be triggered. In case of multiple selection only deleted is possible. The operations can be triggered by the action bar icons.
By selecting one of the list items the user will lend into the details view of the given entity, where by clicking one of the action bar icons the given item can be either edited or removed.
After leaving and re-opening an application where the user is already registered and the application is protected by a user defined passcode, the first screen will be an unlock screen. The generated application supports the retry limit feature, which means that the possible number of failed unlocking attempts is limited. The limit is set un the server, it is part of the client policy. The client policy is read after the onboarding is finished and after each successful unlock. If the passcode policy on the server became stronger, and weren"t satisfied by the current passcode, the user would be forced to change the passcode.
If the push feature was selected in the Wizard during project generation, then the application can receive push messages, as well. In order to process messages, the application has to be running. If it were in foreground, then the push message would appear in a notification dialog over the current activity. If it were in background, then a notification would appear on the system notification bar.