Advanced synchronization
When you define a content type, by default, all items of that type are distributed to all mobile devices. While this setup is simple and easy to get started, it does not scale in case you rely too heavily on content items.
When you define a content type, by default, all items of that type are distributed to all mobile devices. While this setup is simple and easy to get started, it does not scale in case you rely too heavily on content items.
Configuring sync conflict resolution strategies
In iCL Portal, most of the heavy lifting is done in background jobs. So in case the system behaves "weird", e.g. your users are not receiving the data they need, reports are not sent, etc, the first spot to look for issues is the Hangfire dashboard.
While this should not happen a lot, it can rarely be the case, that one of your users cannot synchronize anymore.
As with inspections and tasks, it can happen that content items are duplicated in the iCL System.
The iCL system allows you to plan inspections for your users using tasks. In principle, every task can only be performed once.
iCL allows you to quickly create powerful checklists to gather information on various things.
Welcome to the Knowledge base. This is a collection of articles that describe the inner workings of the iCL System in order to give you a broad understanding of the system and how it works. It is intended for administrators and developers.
The App (iCL Filler) also allows the user to configure various settings.
In iCL, there is a mechanism to plan tasks for your users: Tasks.
One of the primary features of iCL Filler is, that it can work completely offline. To achieve this, we need to synchronize all data necessary to conduct inspections to the device.