This topic is relevant for NextGen Synchronizer only, embedded in Agile Manager's configuration area. For details about the ALM Synchronizer, see for .
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 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.
Later, map these corresponding fields in the link's Field Mapping tab. For details, see Edit field mapping.
In ALM, modify the fields listed in the following table. If a field does not already exist in ALM, create a user-defined field to correspond to this data in Agile Manager. For details about mapping fields after setting up your link, see Edit field mapping.
Defining fields as Lookup List fields enables you to have empty lists, but still use this field for grouping in ALM.
Field name | Description |
---|---|
Application |
Define as a Lookup List field. Configure ALM not to verify this value. Tip: Alternately, when editing your link, map the Agile Manager Application field to the ALM Product field. If you do this, any new applications added to Agile Manager are not automatically created in ALM. To synchronize these new applications, you must first add the new Product value in ALM. |
Blocked | Define as a String field. |
Bucket |
Define as a Lookup List field. Configure ALM not to verify this value. |
Feature |
Define as a Lookup List field. Configure ALM not to verify this value. Note: This field is required if you use features and themes. |
Invested (Hours) | Define as a Number field. |
Kanban Status | Define as a String field. |
Rank | Define as a Number field. |
Remaining (Hours) | Define as a Number field. |
Story Points | Define as a Number field. |
Team |
Define as a Lookup List field. Configure ALM not to verify this value. |
Theme |
Define as a Lookup List field. Configure ALM not to verify this value. Note: This field is required if you use features or themes. |
Tip: You may want to create an additional user-defined field to distinguish between defects created directly in ALM and those synchronized from Agile Manager.
To do so, create a defects field in ALM named Creation Method. Later, when you are mapping fields, assign a constant value of created by Synchronizer. For details about assigning constant values, see Edit field mapping.
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, 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.
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.
Note: Either do this in the endpoint where you'd prefer to access this data, or do this in both endpoints. Attachments are not synchronized, so you will not automatically have access to this data in both endpoints.