My data

The My Data section becomes available in the Flow Clients whenever a user works with apps that either use local data preloaded through Local Data Resources or have Queue lanes where items are uploaded asynchronously (Sync Work).

The main purpose of My Data is to support users who need to work offline. Local Data makes sure that the information an app depends on is already downloaded to the device, so the app can run without an internet connection. Sync Work, on the other hand, takes care of items created while offline and automatically syncs them once the device is back online. Together, these features make it possible to continue working seamlessly, whether or not a stable internet connection is available.

Online means the device has an active internet connection and can reach Novacura’s cloud services.

Offline means no internet connection is established.

Apps using Local Data run online in all environments, including DEV. However, offline mode is only supported in the TEST and PROD environments.

Read more about Queue lanes here.

Find an example of how to create an offline app here.

Local Data

Local Data refers to preloaded data stored locally on the device. It can be used both online and offline.

In Local Data, users can:

• Download all data used in a specific app.

• Download data for individual components.

• Download all Local Data they have access to across multiple apps.

If a user starts an app that requires Local Data without downloading it first, an error message will appear, prompting them to download the necessary data before the app can run.

User-specific storage

Local Data is stored per user. If a device is shared between users, each user only has access to their own Local Data.

Local Data is removed when the user:

• Switches environment (or re-selects the same environment).

• Changes organization (or re-selects the same organization).

• Signs out.

Sync Work

The Sync Work tab shows the items a user has created in apps that use Queue lanes. These represent work items that will be synchronized with an external system.

• If the user is online, the work is synced immediately.

• If the user is offline, work can still be created. Items will remain pending until the device reconnects, at which point synchronization happens automatically.

Sessions

Items are grouped and displayed per session, where a session begins each time the user starts an app.

If an app contains multiple lane crossings, the resulting items are queued within the session in the order they were created. This ensures data integrity in cases where one action depends on another being processed first.

Item statuses

Each item is shown with its current status:

• Pending – The item has been created but not yet processed.

• Synced – The item has been successfully processed.

• Error – The item failed during processing. Error details are available for review.

Items in Error

When a item encounters an error, users can review the error details in the Sync Work tab under My Data.

Depending on the app design and system configuration, error handling may include:

• Reviewing error details for items in Error status.

• Retrying the item if the issue in the connected system has been resolved (Retry).

• Skipping the item if it should no longer be processed (Skip).

If a item ends up in Error, any remaining items in the same session will remain in Pending until the error is resolved. The queue will only continue once the error has been handled successfully by either a Retry or a Skip.

Sync Work items Items in Sync Work are retained per user session. They remain pending or in error until successfully processed or resolved. However, items are removed when the user:

• Switches environment (or re-selects the same environment)

• Changes organization (or re-selects the same organization)

• Signs out