Generated Application

The generated application provides a complete create-read-update-delete (CRUD) access to OData service data behind the selected application of the SAP Cloud Platform server. It includes the Fiori logon screens for onboarding to the server and the OData and Foundation libraries which are used to consume the service.

The generated application presents a top level that provides a list of entity sets from the OData service. From here, you can navigate down to access the list of entities for a given set where you can select one of the entities to open a details view.

On the relevant screens, you can execute create, update, and delete operations.

The application can handle push messages and upload log records to the server. It can also upload client usage data to the server if the feature is enabled in the SAP Cloud Platform Mobile Services cockpit and the user has agreed to allow tracking usage. Please note that these features are optional: they are only present in the app if the corresponding check boxes were selected during generation.

Onboarding Flow

At the first start of the application the following "Welcome" screen is presented.

Tapping the Get Started button triggers the logon flow.

The generated application supports basic authentication, OAuth2, SAML, or no authentication. The code is generated according to the authentication type of the consumed application, which was set on the server. If the authentication type is Basic, then an Authentication dialog appears.

After providing the right credentials, the application receives the client-side configuration policy from the server which contains the required passcode policy. If the application requires passcode protection, then an "Create Passcode" screen is displayed. This screen also contains information about passcode complexity. After a proper passcode is entered, a verification screen appears.

After a passcode is created, the logon flow is finished. The application displays the entity set list which is accessible on the server.

By tapping the menu in the top right corner, you can open the Settings screen. The Settings screen allows you to configure and enable settings such as log level, log upload, and client usage collection. Please note that logging and client usage are optional features that are selected in the Wizard during application generation.

From the Settings screen, you can also change the passcode or reset the app which deletes the credentials of the app and any downloaded data. Please note that setting or removing the passcode is only available if client policies have not been applied to the application or the Passcode Policy feature has not been enabled on the server.

Business logic

After selecting one of the entity sets, another list is opened which contains the entities of the collection.

When the screen width is at least 900 dpi, for example on a tablet in landscape orientation, both the collection and detail screens are visible. In this mode, the right frame contains the create/edit/detail screen, while the left contains the list.

When the entityset includes an image, this is loaded. Otherwise, the first letter of the item is used.

The floating button on the bottom right corner can be used to create and add a new entity to the set. Tapping it opens a creation screen. Select one item to update or one or more items to delete using buttons on the action bar.

By selecting one of the list items, you can open the details view of the given entity and then use the buttons on the action bar to edite or delete it.

On a tablet in landscape view, the details for an item are visible as is the list. Using the action bar buttons, you can edit or delete the given item. in master-detail view, every frame has its own toolbar.

Additionally, if the entity provides navigation links, you can navigate to another screen to view related entities.


When you re-open the app after registration, you will be presented with an unlock screen if the app is protected by a user-defined passcode. The generated app supports the retry limit feature, which means that the possible number of failed unlocking attempts is limited. The limit is set on the server as part of the client policy.

The client policy is read after the onboarding is finished and after each successful unlock. If the passcode policy is changed and the current passcode does not meet the requirements, the user is prompted to change the passcode.

Push Notification

If the push feature is selected in the Wizard during project generation, then the application can receive push notifications. In order to process notifications, the application has to be running. If the app is in the foreground, then the push message appears in a notification dialog over the current activity. If it is in the background, then a notification appears on the system notification bar.