Synchronizations are started from the Offline Access Library page of Archer. Before synchronizing, start the Distributed Transaction Coordinator service on the laptop running offline access.
When a record is enabled for offline access, all supporting data, including cross-referenced or related records, for that record is also synchronized. Records from a retired application are not synchronized. Records in an application enabled for Advanced Workflow are read only in offline access.
Important: Appointment details are synchronized in offline access and can be updated while working offline, but when the data is resynchronized withArcher the relationships between the parent and resource applications are not saved. You must re-edit these appointment details to reestablish these relationships.
On this page
When is offline access synchronization required?
Synchronizing offline access to Archer is required:
- The first time you run offline access after installation.
- After purging offline access data.
- To update Archer and offline access with new or updated records.
Synchronization process
Offline access synchronization requires a stable connection to Archer. If the connection is lost, the synchronization fails. You cannot synchronize if the offline access version does not match the Archer version.
The initial synchronization downloads all records and any supporting data from the Offline Access Library. If applicable, this process initializes an index rebuild for keyword search that can consume significant resources.
Subsequent synchronizations ensure that the offline access data is synchronized with the Archer data. During this synchronization, offline access data uploads to the Archer, and then any updated (new and existing) records in the Offline Access Library download to offline access. If data is missing, or does not match the parent record, a conflict is created during the synchronization. You can resolve conflicts at any time from the Offline Access Library, but must resolve them before the synchronization can successfully complete.
Offline access is not available until synchronization completes.
Archer includes special synchronization options controlled by security parameters to ensure offline data is synchronized regularly. These options include:
- Sync Reminder. If the Sync Reminder option is set and the specified conditions are met, an alert prompts you to synchronize the offline data with Archer. You can continue working in offline access.
- Force Sync. If the Force Sync option is set and the specified conditions are met, you must synchronize offline access with Archer. You cannot open offline access until a sync successfully completes.
- Purge Data. If the Purge Data option is set and a you have not synchronized within the specified time frame, you are forced to purge all offline access data upon login and run an initial synchronization. Offline access is not available until all data is purged and until the initial sync is completed.
Run the initial offline access synchronization
If an initial sync is required, you are prompted to run it. This process requires a stable connection to Archer and takes several minutes.
If applicable, this process initializes an index rebuild for keyword search that can consume significant resources.
- From the User menu, click Offline Access Library.
- Click Start Sync.
- In offline access, click Continue.
Run a forced offline access synchronization
Complete this task when prompted. When a forced synchronization is required, you cannot start offline access until the synchronization completes. Your administrator determines whether this option is required.
Note: This task requires a connection with Archer and takes several minutes.
- From the User menu, click Offline Access Library.
- Click Start Sync.
- In offline access, click Continue.
Synchronize offline access
Synchronizing requires a stable connection to Archer. You run all synchronizations from the Offline Access Library.
- From the User menu, click Offline Access Library.
- Click Start Sync.
- Wait until the process completes.
If there is missing data or data that does not match the parent record, a conflict is created during synchronization. You can resolve conflicts at any time from the Offline Access Library, but must resolve them before the synchronization can successfully complete.
