This topic is relevant for NextGen Synchronizer only, embedded in Agile Manager's configuration area. For details about the ALM Synchronizer, see for .
Agile Manager and ALM fields are mapped to specify pairs of fields with synchronized data. Field mapping includes specific field value mapping (for list fields), as well as the direction in which the data is synchronized.
For details about mapping user list field values, see Map user list fields.
When you first create a link, some system fields are mapped automatically. Use the link configuration Field Mapping tab to verify the automatic mapping, as well as to map user defined and other optional fields. Mandatory fields must be mapped to synchronize records correctly. For more details, see Automatically mapped fields.
Caution: Once a record in one endpoint is mapped to a record in the other endpoint, it is always synchronized if there is new data, regardless of whether the record still matches the link's filter.
Therefore, before you start synchronizing, it is highly recommended that you read Field mapping guidelines. For additional recommendations before synchronizing, see Adapt the data in your endpoints.
For details about the options available on this tab, see Field mapping references. Click Edit to modify settings, and
Save to save your changes.
Above the grid, toggle between showing Agile Manager Fields and ALM/QC Fields to determine how the fields are listed in the grid.
Select the row for the field you want to map, and define the following:
In the Direction column , select whether you want to map the field from Agile Manager to ALM, vice versa, or as bi-directional.
If the field has no corresponding field in the other endpoint, select Constant.
In the mapped field column (Agile Manager Field or ALM Field, depending on how you are viewing the fields) select a field from the dropdown list.
The Type, Attributes, and Required columns are populated automatically.
If you are mapping a constant value, enter the value in the corresponding column cell. The constant value is assigned to the field when Synchronizer creates new entities, and is not updated in subsequent synchronizations.
For example, if you created a Creation Method user-defined field in ALM to distinguish between defects created directly in ALM and those synchronized from Agile Manager, enter created by Synchronizer as the mapped constant value. For details, see Adapt the data in your endpoints.
If you need to map multiple fields in the opposite endpoint, click in the Mult. Mapping column. When you do this, your direction options are limited to prevent conflicts.
Define a Dominant Endpoint to determine the source of the synchronized value in case of conflicts.
Mapping specific field values is relevant only for mapped string or list fields. Select and map values and mapping directions for each field in the endpoints.
Caution: If you have different numbers of values in the field for each endpoint (such as 5 values in Agile Manager and 6 values in ALM), bi-directional value mapping may result in some data loss when records are synchronized back and forth. For details and recommendations, see Guidelines for mapping specific field values.
On the Field Mapping tab, select a pair of mapped fields to view additional properties on the right.
On the right, expand the Values section.
On the Field Mapping tab, select a pair of mapped fields to view additional properties on the right.
Expand the Field Properties section to view the available properties, such as the field schema names in either endpoint, or whether the field is read-only.
The displayed properties differ, depending on the type of field you select.
To unmap a pair of ALM and Agile Manager fields, when there are multiple fields mapped in one endpoint to a single field in the opposite endpoint, click in the Mult. Mapping column.
To remove a single field mapping (a pair of ALM and Agile Manager fields that have one field in each endpoint), click in the mapped field.
For example, when viewing fields sorted by Agile Manager field, click the in the mapped ALM field:
Note: You must always run an integrity check after modifying a link's configuration. We also recommend running a simulation to prevent errors occurring in the actual synchronization.
For details, see Run synchronizations.