1. Overview : Synchronization Behavior Defined by the AccuSync Configuration

Synchronization Behavior Defined by the AccuSync Configuration
The details of how AccuSync synchronizes AccuWork issues with issues in an ITS project are described in the AccuSync Configuration. You use a separate AccuSync Configuration for each AccuRev depot you want to synchronize with an ITS project.
The information in an AccuSync Configuration includes:
The specific fields in these issues whose data you want to synchronize. For example, you might want to map the Comments field in an AccuWork issue to the Description field in an ITS issue, and you might choose not to synchronize a field that is peculiar to one system. You can create a mapping definition, a named group of field mappings, and use it as a building block to create other, more specialized mapping definitions. You might have different mapping definitions for defects and tasks, for example.
How frequently you want AccuSync to synchronize AccuWork with your ITS. You can perform an initial synchronization of all issues in a depot based on a transaction number or date you specify. After the initial synchronization, you can use a synchronization pattern to schedule synchronization of AccuWork issues and ITS issues at any interval you specify. You can also perform synchronizations manually whenever you choose.
Optional transformers that let you convert values in one system to different values in the other. For example, you can use transformers to strip the @domain_name suffix from user names for inclusion in an AccuWork issue. You can also create custom transformers.
See AccuSync™ Configuration Components for a complete list of the components that can make up an AccuSync Configuration.

Micro Focus