Synchronizing Custom Fields
The fields described in the preceding table are required for AccuSync to successfully synchronize AccuWork issues with ClearQuest requests and tasks. See IBM Rational ClearQuest Configuration Reference to learn about the fields that are synchronized by the default ClearQuest configuration (Owner, Description, and so on).
In addition to the required and default configuration fields, AccuSync allows you to create and synchronize up to 30 additional fields, called custom fields. You follow the same basic process for adding custom fields that you use for adding required fields, with these exceptions:
|Custom fields have required names||Due to limitations in the ClearQuest API, custom fields must adhere to a strict naming convention in order to be recognized by the synchronization engine. You can name these fields however you like in the AccuWork schema, but in ClearQuest they must be created as customField1, customField2, <![CDATA[ ]]>customField3 and so on, and cannot exceed customField30. Note that these names are case-sensitive.|
|Custom fields must be added to the AccuWork schema||Once you create a custom field in ClearQuest, you need to add the corresponding field to the AccuWork schema and the issue form as described in Modifying an Existing AccuWork Schema. For example, if you add customField1 to ClearQuest to store a customer name, you might add an Interested Customer field to the AccuWork schema to allow this value to be synchronized.|
|Custom fields must be added to AccuSync field mappings||The custom fields you create in ClearQuest must be added to an AccuSync field mapping, to associate the custom field with a corresponding field in AccuWork. See Editing Field Mappings for more information.|