In Riva 2.4.51 or higher, a tool can be used to automate complex data migrations or imports, as well as onboarding users.
The strategy behind the tool consists in creating a sequence or chain of sync policies that the users to process are automatically taken through. There is no need to manually move the users from one sync policy to the next. As soon as a user has successfully been synced through a sync policy in the chain, the user is moved to the next policy.
A successful sync is an empty sync cycle. A sync cycle is empty when there are no errors, skipped items, item creations, or item deletions. It means that all the items that had needed to be created or deleted have been created or deleted — there is nothing left to be synced by the policy — and the sync has been successful for that user.
- The sync policies that are to be included in a chain are created and edited like any sync policy.
- In a window called Edit Onboarding Chain, the sync policies are selected and placed in the desired execution order and saved as a chain.
- The users to migrate, import, or onboard are added, usually to the first policy. For some users, it may be desirable to bypass the first policy or policies, and they can be placed in any subsequent policy.
- The admin enables the sync policies and lets them execute. Generally, the first policy is the only one that executes at first, but if some users were placed in a later policy, that one executes too.
- As soon as one or more users have successfully synced, they are automatically moved to the next policy in the chain, and this policy starts executing if it had not already started.
- A policy in the chain is executed as often as it takes for every user assigned to that policy to sync successfully and be moved to the next policy.
- The migration, import, or onboarding is completed when all the users have been successfully synced by all the policies in the chain.
Note on the name Edit Onboarding Chain:
- The window used to create and edit sync policy chains is called Edit Onboarding Chain, because the onboarding of users to the sync process is a frequent scenario that can benefit from using a sync policy chain.