Adapt the data in your endpoints

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.

Before synchronizing records between Agile Manager and ALM, adapt the data in either endpoint to match the fields supported in the other endpoint, as well as synchronization requirements.

For example, Agile Manager defects can also have a feature and theme defined. To synchronize these fields, you must create corresponding fields in ALM.

In Agile Manager, user stories are often arranged in a hierarchy, under features and themes. To synchronize these records with ALM, you must create a corresponding hierarchy of requirement types.

Modify in both ALM and Agile Manager

In both endpoints, create user-defined or custom fields to represent the record ID in the other endpoint. Define these fields as Number or Numeric fields.

  • In ALM, create a field named Agile Manager ID.
  • In Agile Manager, create a field named ALM or QC ID.

Later, map these corresponding fields in the link's Field Mapping tab. For details, see Edit field mapping.

Note: Avoid special characters (~!@#$%()^&) in attachment names, as these may cause unexpected behavior during synchronization.

Modify in ALM

Notes for themes, features, and teams

Themes and feature names must be unique in both ALM and Agile Manager, and team names must be unique in ALM. If duplicate values are found during synchronization, the related record is not synchronized.

  • In Agile Manager, a workspace team and a feature team can technically have the same name. However, this is not recommended within the same release to prevent confusion or errors when synchronizing. For details, see Notes for synchronizing team fields.

  • In Agile Manager, records assigned to a specific feature must also have a theme defined. If you synchronize features, you must also synchronize themes. Therefore, if you map theme and feature fields, we recommend making them required fields in ALM to avoid synchronization errors.

Notes about maximum record sizes

NextGen Synchronizer supports a maximum record size of 12 MB. This means that synchronizing records larger than 12 MB will cause errors.

If you have records that are larger than 12 MB, move some of the data from the Description, Comment, or any other custom free text field, to a separate file. Then, add the file to the record as an attachment. Attachment sizes are not included in the maximum record size, though they are synchronized between the endpoints.