Best Practices on Mapping QC Field "Detected By"

When you upgrade the integration from Quality Center 10 to ALM 11.00 or later, keeping the same configuration mapping settings, you may encounter an error with the QC/ALM field Detected By. In this case, you may try one of the following approaches for mapping the QC/ALM field Detected By:

• Mapping QC/ALM field Detected By with OpenText PPM request field Created By. When OpenText PPM user list and QC/ALM user list are the same, this approach would be the best choice.

• Mapping QC/ALM field Detected By with OpenText PPM custom field (text field). This approach would require you to enter correct information into OpenText PPM custom field.

  For example, you create a text type field in OpenText PPM and map it to QC/ALM field Detected By. If you set the control mode to QC, then synchronization populates the new OpenText PPM field automatically with the Detected By field.

• Mapping QC/ALM field Detected By with OpenText PPM custom field (using validation QC/ALM Defect Assigned User). If you want to get user list from QC/ALM directly, this approach would be the best choice.

If you leave this mapping field blank when creating a OpenText PPM request in order to create a defect in QC/ALM, you can set the control mode to QC, then the system populates Detected By field in QC/ALM with the value you specified in QC/ALM Username field on the integration configuration page.