Scenario: The app must be able to run both online and offline. If the mobile device on which the app runs is connected to the internet, the app must immediately submit the status report.

When data is submitted offline, the data must be stored in the app until the app is back online.

Mobile users often need to be productive even when they have limited or no connectivity.

LoadData and SaveData combine to form a simple mechanism to store small amounts of data on a local device. By using these functions, you can add simple offline capabilities to your app.

The SaveData function stores a collection for later use under a name.

The LoadData function reloads a collection by name that was previously saved with SaveData. You can't use this function to load a collection from another source.

Graphical user interface, text, application, email Description automatically generated

Box 1: Business Process

Scenario: If a sales representative submits a status report and assigns the At Risk status to a process, the app must prompt the sales representative to enter a detailed description for the risk. This information must be emailed to the regional manager.

Business process flows provide a guide for people to get work done. They provide a streamlined user experience that leads people through the processes their organization has defined for interactions that need to be advanced to a conclusion of some kind. This user experience can be tailored so that people with different security roles can have an experience that best suits the work they do.

Box 2: Common Data Service when a record is created

The Microsoft Dataverse (Common Data Service) connector provides the following triggers to help you define when your flows start:

When a row is created, updated, or deleted

When an action is performed

When a flow step is run from a business process flow