Skip to content

Offline Manager#

The Offline Manager allows selection of Business Objects in Flow when the user is offline.

Business Objects#

  • Admins can select a list of Business Models which will result in all Business Objects from these models to be downloaded automatically

Flows#

  • Admins can select which flows can be started offline, only these flows will be shown in the launchpad when user is offline

Automatic Model Selection for Offline Flows#

When an admin adds a Flow for offline use, the system checks the first UI used by that Flow. Business Models referenced by elements in that UI are added to the offline data selection automatically if they are not selected already.

This helps offline Flows work with the Business Object data they need, especially when the first UI contains Object Selection elements or other elements connected to Business Models.

The behavior is additive only: removing a Flow from the offline setup does not remove Business Models from the offline data selection. If the Flow has no accessible first UI, no Business Models are added automatically.

Users#

  • Admins can select which user should have offline functionality enabled.

Sync Period#

  • Admins can select a period of auto sync which determines how often all Business Objects will be downloaded to the users devices
  • All users can manually sync all Business Objects by clicking the "Sync" button

Offline Data#

  • Users can manually sync the data setup by the admins if they want to.
  • The offline data is automatically synced depending on the period admins set.
  • When user goes back online all the data he/she created offline will be automatically uploaded to the servers, no manual work is needed for this.

Incremental Sync#

Syncing Business Objects for offline use is incremental: instead of downloading every record again on each sync, the app first fetches a lightweight manifest of record identifiers and then downloads only the new and changed records. This makes recurring syncs noticeably faster and lighter on mobile data and battery, especially for large Business Models.

  • Only deltas are downloaded — records that already exist locally and have not changed are skipped.
  • Related objects are fetched in batches and each Business Model is written to local storage once per sync, rather than record-by-record.
  • Sync page size — an advanced setting controls how many records are requested per page during user and group sync. The default suits most tenants; increase it to sync faster on reliable connections, or lower it on constrained networks. The value is preserved when other offline settings are saved.
  • Quieter background syncs — transient per-request errors that occur while a sync is running no longer raise their own error notifications, so a sync on a flaky connection does not flood the screen with toasts. Genuine failures are still reported.

Offline Data Safety#

To prevent data loss on unreliable connections, in-progress responses are protected end to end:

  • A local draft is kept while the user fills a UI and is only cleared once the server confirms the submission. If the request fails (for example the device drops to a status-0 network error), the response is preserved and the app switches to offline mode rather than discarding the input.
  • After a reload, the app recovers the in-progress values from the cached UI response, so a refresh or crash mid-form does not lose work.

Not-synced Warnings#

Selection elements that depend on synced data now show a clear warning when that data has not yet been downloaded for offline use. This applies to:

The warning tells the user (or admin configuring offline access) that the underlying Business Objects, users, flows, or UIs still need to be synced before the element can be used offline.

Tips#

This feature works in a combination with Offline Flows