Configuration for mapped attachment fields

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

If you are still using ALM Synchronizer, we recommend migrating to the more robust NextGen Synchronizer embedded in Agile Manager's configuration area.

Some Synchronizer behavior for synchronizing mapped attachment fields depends on the settings configured in the file.

The file is located in the Synchronizer installation directory>\dat directory on the Synchronizer server machine.

Attachments with identical names in opposite endpoints

Parameter name pass.entity.sync.on.attach.conflict
Description and values

Defines whether the task run report displays a failed or passed status, when Synchronizer attempts to synchronize an entity with attachments in each endpoint that have identical names.

Default value. N

Note: Irrespective of the status of the pass.entity.sync.on.attach.conflict parameter, such attachments cannot be synchronized.

File-encoding for URL attachments created in ALM

Parameter name alm.file.encoding
Description and values

Defines the encoding used by ALM for URL attachments created in ALM.

Enter a list of comma separated values. For example: alm.file.encoding=UTF-8,UTF-16

Default value. <Null>. By default, Synchronizer attempts to match the default encoding defined on the machine on which it is installed, as well as UTF-8 and UTF-16.

If ALM uses a different encoding and it is not defined here, Synchronizer cannot determine the encoding used, and cannot synchronize the URL attachments to Agile Manager.

Deleted attachments

Parameter name delete.source.attachment.on.url.deletion
Description and values

Determines how Synchronizer handles attachments that were deleted in the destination endpoint, but were modified in the source endpoint.


  • Y = The attachment in the source endpoint is deleted.

  • N = (Default) The attachment in the source endpoint is kept, and the attachment in the destination endpoint is recreated.