Date: Thu, 28 Mar 2024 23:32:12 +0000 (UTC) Message-ID: <962701530.1117.1711668732582@confluence-prod-0.confluence-prod.confluence.svc.cluster.local> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1116_1686224380.1711668732581" ------=_Part_1116_1686224380.1711668732581 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Description: In this topic, the user = 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 conn= ected to the internet or loses connection while the app is in use. This fea= ture is useful for those who have limited or no cellular or WIFI connection= s at their service location.
*Please note: Us= ing Mobile App Offline Mode requires an instance-level setting change. Please contact D= CI to enable this feature.
Role Required: Super User
Permission Required: Funding Source A= dmin
Offline mode allows end users to use the mobile app on a registered devi= ce when the device is not connected to the internet or loses connection whi= le the app is in use. A user can only have one registered device. Mob= ile app functionality is limited due to available data and to maintain secu= rity.
The mobile app will assess the internet con= nection and automatically switch to offline mode in the event that no conne= ction is found or a connection is lost
The user does not need to do anything to sw= itch to offline mode
A red bar stating Offline will display acro= ss the top of the mobile app screen when it is in offline mode
Client Transportation is not available
<= /li>Users are limited to logging in and making = real-time punches:
Selecting Clock In
Completing EVV on an open punch
Selecting Clock Out
All other tasks are unavailable in offline = mode
Unavailable tasks are grayed out and not ab= le to be selected
Information that is usually displayed (such= as client name and remaining balance) will be abbreviated or blank for sec= urity purposes
There are several instance-level settings that must be enabled in order = to use mobile app offline mode. These settings include:
Mobile = App Offline Enabled - Determines whether or not offline mode can be used in= the system
Offline= Days Threshold - Determines the maximum number of days in a row a device c= an be offline. This value can be between 1 and 7. After the offline days th= reshold is reached, the user will not be able to enter any more punches unt= il the device is reconnected to the internet.
Maximum= Offline Punches - Determines the maximum number of offline punches a user = can make in a row. After the maximum offline punches are reached, the user = will not be able to enter any more punches until the device is reconnected = to the internet.
Multi-F= actor Authentication - Determines if the system will require two-step authe= ntication for logging into the mobile app
If = enabled, is only available on devices that support biometric authentication= (fingerprint and/or face recognition) and for users that have verified a m= obile phone number in DCI.
After 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 wheth= er or not offline mode can be used for the specific funding source. This fu= nding source level setting will only be visible if the instance-level setti= ng Mobile App Offline Enabled is set to Yes.
End users can use offline mode on a registered device. The end user=E2= =80=99s registered device is the first device used to log in to the mobile = app. An end user can only have one registered device.
The mobile app will assess the internet connection status and automatica= lly switch to offline mode if no connection is present or if the connection= is lost. A red bar will display across the top of the mobile app screen wh= en in offline mode. No action is needed from the end user to switch to offl= ine mode.
When the mobile app is in offline mode, end users are limited to real-ti= me punching. All other mobile app functionality is unavailable in offline m= ode. Additionally, data that is usually displayed (such as client name and = remaining balance) will be abbreviated or blank for security reasons.
End users follow the same workflow for real-time punching in offline mod= e as 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 p= rompted to confirm synchronization when an internet connection is made. Whe= n offline punches are synced, they will appear in the Entries table.
If the end user exceeds the Offline Days Threshold or the Maximum Offlin= e Punches limits, they will receive a message directing them to bring the d= evice online to sync their offline punches before they can enter more. They= cannot clock in again until this happens.
On some occasions, the end user will receive an internet connectivity er= ror and the mobile app will not operate in offline mode. This means there's= an issue with the device registration in DCI. Deregister the end user=E2= =80=99s device and ask them to log in from the device they wish to use movi= ng forward. To deregister the device:
Log in = to the DCI portal
Click Home on the main menu=
p>
Click Employees on the submen=
u
Enter t= he employee's name in the filter and click Search=
Click anywhere in the employee row to open the Employee Details p= age
Click Actions
Select<= span> Deregister Mobile Device from the drop-down menu
If = no device is registered to the end user, Deregister Mobile Device will not = be an option.
Doe= s the end user share the device with another user? If that user logged in f= irst, the device is registered to them. The solution is either:
The end= user must use a different device OR
If the = device was registered to another user by mistake, the supervisor/employer m= ust deregister the device from the other user then the user may log in from= the device.
Click <= strong>Yes to confirm deregistering the device