Run synchronizations

Note: This topic is relevant for NextGen Synchronizer only. For details about the ALM Synchronizer, see ALM Synchronizer for Agile Manager or search using the ALM Synchronizer filter.

After your link is created and configured, run an integrity check to verify that records will be synchronized correctly.

If the integrity check passes, run a simulation to verify how much data will change.

Then run manual tasks, or start automatic synchronizations.

If you make certain changes to a link's configuration after having already synchronized, such as updated rules or field mapping, you'll need to run a full synchronization to ensure that all records are aligned with those changes. Agile Manager will notify you when a full synchronization is required.

Caution: Once records have been synchronized, they cannot be removed from the synchronization. When first setting up a link's configuration, use a favorite defined with one record only. Widen the favorite slowly, as you go ensuring that the synchronizations run as you expect.

However, if you use an alternate root folder to limit the synchronized requirements or releases:

  • Requirements removed from the alternate root folder in ALM will no longer be synchronized.
  • Releases removed from the alternate root folder in ALM will no longer be synchronized, but their cycles will still be synchronized.