Keeping track of — and documenting — the changes that are made to Riva sync connections, policies, advanced options, and/or custom options is very important.
Built-in change management tracking is available in Riva 2.4.43 or higher. A Change Entry window is available to record the reason for a change made to a connection, policy, or advanced options or custom options. It is also possible to record one explanation that will apply to multiple subsequent changes. The information entered in the Change Entry window is persisted with the same document that stores the connection, policy, or external settings.
Many organizations use a source code repository like Git or SVN. Those repositories can track changes as well as display changes between revisions. By placing the Riva\Configuration and Riva\Custom folders in a repository, changes to Riva can be maintained under change control.
Note: The Change Entry window is not available to record changes made in app.settings files. What is an app.setting file? This limitation is effective whether the app.setting file is edited with an external editor (for example, Notepad) or by means of the Riva Manager application.
Every change entry can record
The change entries are saved to the modified connection, policy, or advanced settings.
This example is at the top of a sync policy file named "CRM Synchronization Policy.policy",
By default, changes are saved without recording change entries.