Set Up the AccuWork Schema

The field mappings in an AccuSync Configuration rely on fields defined in both the AccuWork schema and your ITS schema: if you want to synchronize the Status field in your ITS, there must be an equivalent and compatible field in AccuWork, regardless of its name (the equivalent field might be called State in AccuWork, for example). Further, the values for fields with a type of Choose must be defined in the respective schemas as well. For example, when you define a Project field with a type of Choose, you must also define the values that can be specified for that field (Acme, Windfall, and Gimble, for example). In AccuWork, the schema also controls which fields are displayed for an issue record.

In order to set up the AccuWork schema for use with AccuSync, you can either:

Use the default AccuWork schema for your ITS that was installed with AccuSync AccuRev recommends using the default AccuWork schema for your ITS if you are using AccuSync with a new AccuWork installation, that is, one without a pre-existing AccuWork schema.
Modify your existing AccuWork schema to incorporate fields required for synchronization Modify your existing AccuWork schema if you are upgrading from AccuBridge.

Note: Regardless of whether you use the default AccuWork schema for your ITS or modify your current AccuWork schema, you must define values for your ITS projects and applications in your AccuWork schema.

IBM Rational ClearQuest and ALM users only: When you have finished setting up the AccuWork schema, you must add custom fields to your ITS schema for the AccuWork data you want to store and display in your ITS. See Add AccuWork Fields to Your ITS Schema for more information.

See also: