Description: In this topic you will learn how to set up the mobile app for offline mode. This guide is for system administrators. Offline Mode allows the end user to use the Mobile App on a registered device when the device is not connected to the internet or loses connection while the app is in use. This feature is useful for those who have limited or no cellular or WIFI connections at their service location.

*Please note: Using Mobile App Offline Mode requires an instance level setting change. Please contact your DCI representative if you are interested in using this feature.

Role Required: Superuser

Permission Required: Funding Source Admin

Overview

Offline Mode allows end users to use the Mobile App on a registered device when the device is not connected to the internet or loses connection while the app is in use. A user can only have one registered device. Mobile App functionality is limited in Offline Mode due to available data and to maintain security. The only functionality available in Offline Mode is making real-time punches.

The user is limited in what they can do when in Offline Mode.

  • The Mobile App will assess the internet connection and automatically switch to offline mode in the event that no connection is found or connection is lost.

    • The user does not need to do anything to switch to Offline Mode.

  • A banner will display across the top of the Mobile App screen when it is in Offline Mode.

  • When in Offline Mode, users are limited to logging in and making real-time punches.

    • Client Transportation is not available in Offline mode.

  • The only tasks you can do in Offline Mode is real-time punching and logging out.

    • Real-time punching includes:

      • Selecting Clock In

      • Completing EVV on an open punch

      • Selecting Clock Out

  • All other tasks are unavailable in Offline Mode.

    • Unavailable tasks will be grayed-out and you will not be able to select them.

    • Information that is usually displayed (such as client name and remaining balance) will be shortened or blank for security reasons.

Instance Level Settings

There are several instance level settings that need to be set in order to use Mobile App Offline Mode. These settings include:

  1. Mobile App Offline Enabled - determines whether or not Offline Mode can be used in the system.
  2. Offline Days Threshold - determines the maximum number of days in a row a device can be offline. This value can be between 1 and 7. After the Offline Days Threshold is reached, the user will not be able to enter any more punches until the device is reconnected to the internet.
  3. Maximum Offline Punches - determines the maximum number of offline punches a user can make in a row. After the Maximum Offline Punches is reached, the user will not be able to enter any more punches until the device is reconnected to the internet.
  4. Multi Factor Authentication - determines if the system will require two-step authentication for logging into the mobile app.
    1. Please note that if enabled, Offline Mode will only be available on devices that support biometric authentication (fingerprint and/or face recognition) and for users that have verified a mobile phone number in DCI.

Funding Source Settings

Once the instance level settings have been enabled, Mobile App Offline must be enabled for each Funding Source that is allowing offline mode.

  • Allow Offline Mobile App - determines whether or not Offline Mode can be used for the specific funding source. This Funding Source level setting will only be visible if the instance level setting Mobile App Offline Enabled is set to “yes.”

Offline Mode Functionality

End users can use Offline Mode on a registered device. The end user’s registered device is the first device used to login to the Mobile App. An end user can only have one registered device. Please see “Resolving Connectivity Issues” for instructions on how to change an end user’s registered device.

The Mobile App will assess internet connection status and automatically switch to Offline Mode if no connection is present or if connection is lost. A banner will display across the top of the Mobile App screen when it is in Offline Mode. No action is needed from the end user to switch to Offline Mode.

When the Mobile App is in Offline Mode, end users are limited to real-time punching. All other Mobile App functionality is unavailable in Offline Mode. Additionally, data that is usually displayed (such as Client name and remaining balance) will be abbreviated or blank for security reasons.

End users will follow the same workflow for real-time punching in Offline Mode as they do when the device is connected to the internet. Punches made in Offline Mode are saved in the Mobile App as Offline Punches. The end user will be prompted to confirm synchronization once internet connection is restored. Once offline punches are synced, they will appear in the Entries table.

If the end user exceeds the Offline Days Threshold or the Maximum Offline Punches limits, they will receive a message that says they need to bring the device online to sync their offline punches before they can enter more punches. They cannot clock in again until this happens.

Resolving Connectivity Issues

On some occasions, the end user will receive an internet connectivity error and the Mobile App will not operate in Offline Mode. This means there's an issue with the device registration with DCI. You need to deregister the end user’s device and tell the end user to log in from the device the end user wishes to use moving forward. To deregister the device:

  1. Log in to the DCI Portal
  2. Navigate to the Employee Profile Details Page.
  3. Click Actions, then click Deregister Mobile Device.

If no device is registered to the end user and they are still receiving a connectivity issue error, it may be that the end user shares the device with another user and that user logged in first and therefore registered the device to that user. The solution is either:

  1. The end user needs to use a different device, or
  2. If the device was registered to another user by mistake, the supervisor/employer needs to deregister the device from the other user. After the device is deregistered, the end user needs to log in from the device.