How Can We Help?
Configurable Rules for Data SynchronisationConfigurable Rules for Data Synchronisation
What
There are a several synchronisation jobs that get your data into Pure. They often are configurable so it is possible to configure how to synchronise your data and how it is locked in Pure.
How
You configure this in each specific job in Administrator > Cron job scheduling > Edit Configuration.
- The synchronisation rules will apply on all active synchronised content but not on imported or manually created content.
Before you set up a job for the first time, it is a good idea to familiarise yourself with these rules.
Lock relation list
- Lock: Will lock the field in the Editor so that no new items can be added manually.
- Do not lock: Will unlock the field in the Editor so that new items can be added manually (but the lock status of any synced items will remain the same).
Synchronisation fields
- Sync:
- Will import the data and update the data every time it is synchronised. It will lock the field in the Editor.
- Sync Once:
- Will only import the first time the whole content is synchronised. It will not lock the field in the Editor.
Note: That Sync Once cannot be used on a field on content already synchronised. It can however be applied on lists (e.g.: organisation association) the first time it is synchronised in with its association.
- Will only import the first time the whole content is synchronised. It will not lock the field in the Editor.
- Do not Sync:
- Will not import the data and will not lock the content in the Editor.
Note: That not all rules are available on all jobs.
If you wish to unlock parts of the content, changing the configuration will help.
Examples:
- Changing the configuration from Sync to Sync Once should unlock the field immediately - also on those already synchronised. You do not need to run the job to unlock those fields.
- Unlock relation lists: Changing Lock to Do Not Lock: You will need to run the job, if you need to unlock relations (lists of items).
Also removing a job from schedule will unlock all parts of all synchronised content. But only if it is stated specifically in the job schedule in the job overview:
"Managed in Pure"
A record or part of a record can be set to "Managed in Pure = True/False". This is done within the source data.
- True = The data will be imported, the job configurations are ignored and the content will not be locked.
- False = The data will be imported and locked according to the job configuration.
If you have a specific record, that you would like to be handled differently than the others, you can use this 'managed in Pure' option.
More information
Master Class on Person & Organisation synchronisation
General information about data structure
Migrating from old to unified synchronisation
KB-87 Transitioning to the Configurable synchronisation
KB-93 General Configurable Syncronisation errors
Note: Some links are for internal use only and might not be accessible
Updated at October 31, 2024