Configuring Request Types

The guidelines to configure a request type for integration are as follows:

• Make sure the request header type for the request type to be associated with a QC/ALM defect includes the QC/ALM Defect Information field group. Only request types with this field group can be mapped to QC/ALM defects.

  Note: By default, the QC/ALM Defect Information field group is included in only the
  ALM - Defect Template with Quality Center Integration request header type.

• Decide which request type to map to each QC/ALM project, then make sure that the request type and project have the required mapping of associated fields.

• Make sure that each pair of mapped fields includes the required valid values. For example, if a QC/ALM field contains a lookup list, make sure that the associated field in the OpenText PPM request accepts the mapped values. If you update a field in one application with a value that does not have a valid mapped value in the other application, the field in that other application will not be updated.

  For details when integrating with Quality Center version 10.00, see Resolving Lists of Valid Values.

  Caution: QC/ALM workflows can limit the changes a user can make to a field. For example, a script might specify that at a certain point in the QC/ALM workflow, the user cannot change the status from Open to Closed.

  For integration with QC/ALM with a valid field mapping, if a OpenText PPM field is updated, the associated QC/ALM field is updated even if a QC/ALM workflow script specifies the update as invalid.