SUP mobile Workflows in an occasionally disconnected environment

[former_member184221]

Very interesting article by daniel.vanleeuwen on using SUP mobile workflows in an occasionally disconnected environment. Which I would say is a typical environment for most truly useful apps.

The typical recommendation from SAP for an occasionally disconnected environment is to use the Object API in a native application which provides a local copy of the synchronised data on the mobile device. The App code that is demonstrated in this example shows functionally how a mobile workflow can also be used instead and be easy to code and understand. Daniel brilliant code :smile:

Extract:

This sample looks at how mobile workflows can be used when a mobile device's data connection is occasionally disconnected.

Mobile workflows provide the following features for use in occasionally disconnected states:

- Notification or message inbox where items that require attention are stored.

-
On-device cache which stores previously executed online requests for a configurable amount of time.

-
Secure on-device storage which uses an API similar to HTML Web Storage.

- Asynchronous submit allows for Mobile Business Object (MBO) operations to be placed in a queue on the device which are processed the next time the device has a data connection

To download the ful code visit here: https://cw.sdn.sap.com/cw/docs/DOC-151623

The sample includes an excellent tutorial.