In this article, learn what information gets synced to/from the mobile device, how often, and the optional sync settings available
Overview
In this article, we will review how synchronization works, the connectivity requirements for synchronization to happen, the timing of synchronization, and how to know what data will by synchronized and when.
Internet Requirements
Synchronization Levels
What Gets Synchronized?
Optional Sync Data Filtering
Data Conflicts
Internet Requirements
The Idencia OneSource Connect mobile app uses an internet connection to synchronize data to the Idencia server. Even so, it is designed to work with or without an internet connection for most operations. There is only one time where an internet connection is required, that is when you are logging a User into Connect. In all other operations, the information recorded will be stored on the device. Once an internet connection is established, the information will be sent to OneSource Gateway (your cloud environment) and then distributed back to all the devices.
It is important to note that any information you record while you are not connected to the internet will not be visible by any other devices or in OneSource Gateway. This can potentially lead to data conflicts. We recommend an internet connection while you are using the Connect mobile app so the information is immediately synchronized and available to everyone.
Synchronization Levels
When the OneSource Connect mobile app is installed and configured on a device, data synchronization will be continuous with an internet connection. Synchronization occurs at the following times:
- When the device has been idle for the amount of time indicated in the Connect mobile app's configuration settings.
- When the user manually executes the syncing process by tapping the Sync button.
What Gets Synchronized?
Data synchronization in Idencia is bi-directional, meaning data added or updated on the Idencia OneSource Gateway needs to sync with the mobile device, and vice versa. Here are the synchronization rules:
Synchronization from Idencia OneSource Gateway to Mobile Device
Processes:
- All processes and changes are synchronized to the mobile device. The next time the user initiates the changed process, the new version will be used.
- Incomplete processes are not affected by synchronization. Changes take effect the next time the process is initiated.
- Devices in offline mode will use the old process version until a sync is performed.
Projects:
- All incomplete projects are synchronized, regardless of age.
- Incomplete projects are those where the “Mark Job as Complete” checkbox is not checked.
- Items within each synced project are synced based on the Item rules below.
Item Types:
- Item Types:
- All active stock item types are synchronized.
- Inactive item types are not synced.
- Custom Item Types:
- Any custom item type where the job is not complete, and the “Limit Items to Number Required” indicator is not set.
- Any custom item type where the job is not complete, the “Limit Items to Number Required” indicator is set, and the required quantity has not been met.
Items:
- The synchronization time frame selected in the mobile application settings.
- The last synchronized date and time on the mobile device.
- The last modified date of each item.
- The status of any processes linked to the item (complete or incomplete).
- The value of any custom property used for Sync Data Filtering.
When synchronizing, the mobile application checks:
- If the item has an incomplete processes, it will be synchronized.
- The “last synchronized” date and time on the mobile device compared to the “last modified” date of each record in the Idencia OneSource Gateway. If the “last modified” date is greater than the "last synchronized" date and within the sync time frame, the record will be synchronized.
- Optional Sync Data Filtering: If an item’s custom property value excludes it from synchronization, it will not be synced, even if its “last modified” date is within the sync time frame.
Example: A shipping crew member works with inventory items not updated in Idencia for a long time. They choose to sync 2 years’ worth of data. This includes all items shipped to customers within the last 2 years, which may no longer be relevant but will be synced due to their “last modified” date. This can increase data volume and cause sync timeouts. To avoid this, configure your website to exclude items based on a custom property value, such as ‘Shipped’ status.
If you experience long sync times or timeouts, contact your customer liaison to configure your website to exclude unnecessary items from synchronization.
Synchronization From Mobile Device to Idencia OneSource Gateway
With the exception of data conflicts outlined below, all information collected or updated on the mobile device since the last sync will be uploaded to the Idencia OneSource Gateway. To speed the syncing of process data, photos and signature files can be separated from other process data and synced on-demand. See How do I configure my mobile application? article for information on how to delay syncing photos and signature files until you're ready.
Data Conflicts
Because Idencia can work with or without an internet connection, it is possible to have multiple users update the same record in different places. One user could update the item directly in the Idencia OneSource Gateway, another user could run a process on the item on a connected device, while still another user could run a process on the same item in off-line mode. This can result in the data on any one device becoming out of sync with the Idencia OneSource Gateway and other mobile devices.
This doesn't happen very often, and is more likely to happen when working in offline mode for extended periods of time, but when it does happen, changes that exist on the Idencia OneSource Gateway that have not been synchronized to the mobile device will supersede data captured on the mobile device that has not been synchronized to the Idencia OneSource Gateway. This means that your data may be discarded to avoid irreparable data conflicts. When this happens, you will receive a notification on your device that your process was not saved because another user had updated the record. You will need to complete the process again.