Creating the Mapping Between OpenText PPM and QC Fields

After you enable a Quality Center project for the integration, you use the OpenText PPM-Quality Center Integration Tool to map a particular OpenText PPM request type to a Quality Center defect or requirement and to specify the desired mapping between the OpenText PPM fields and the Quality Center fields.

1. In the left pane of the OpenText PPM-Quality Center Integration Tool, expand the tree until the child node at the lowest level (defect, requirement, or both) is visible.

2. Click the child node you want to map and select Action > Add Mapping (or right-click the node you want to map and click Add Mapping).

   The Map Fields wizard opens.

3. Click Next to continue.

4. In the User Name and Password fields, type the user name and password of the Quality Center administrator.

5. Click Next to continue.

   The OpenText PPM Request Type field appears with a drop-down list.

6. Click the arrow of the drop-down list to display a list of all the OpenText PPM request types that can be mapped to a Quality Center defect or requirement (depending on which you selected in step 2).

7. Select the request type in OpenText PPM that is to be mapped to the Quality Center defect or requirement.

8. Click Next to continue.

   From the integration tool, the wizard displays the default mapping between the Quality Center fields and OpenText PPM fields for the request type you selected. In this Map Fields window, the fields map either a OpenText PPM request type for defects to a Quality Center defect, or a OpenText PPM request type for changes to a Quality Center requirement.

   For information about the provided default mappings, see Default Field Mappings for OpenText PPM and QC 10.00 .

   The Quality Center Field column displays Quality Center field names, followed by their DB field names (the names of the columns in the database) in parentheses.

   The OpenText PPM Field column displays the OpenText PPM request field names, followed by their tokens in parentheses.

   The Override column specifies which field, if any, is the "dominant" field for a pair. The Override column can have one of the following values for any pair of mapped fields (row):

   • QC. In this case, Quality Center is said to be dominant for the mapped pair. When the Quality Center entity is created or modified in any way, then the integration updates all the mapped OpenText PPM fields for which Quality Center is dominant.

     When Quality Center is dominant for a mapped pair and the value in the OpenText PPM field is changed, the value in the associated Quality Center field is not affected.

     When the integration creates a Quality Center entity, the OpenText PPM request fields have no effect on the fields for which Quality Center is dominant.

   • PPM. In this case, OpenText PPM is said to be dominant for the mapped pair. When the OpenText PPM request is created or modified in any way, then the integration updates all the mapped Quality Center fields for which OpenText PPM is dominant.

     When OpenText PPM is dominant for a mapped pair and the value in the Quality Center field is changed, the value in the associated OpenText PPM field is not affected.

     When the integration creates a OpenText PPM request, the Quality Center entity fields have no effect on the fields for which OpenText PPM is dominant.

   • BIDIRECTIONAL. In this case, both the OpenText PPM fields and their mapped Quality Center fields operate as though they are dominant—when either the integrated OpenText PPM request or Quality Center entity is created or modified, the integration updates all the associated fields in the Quality Center entity or OpenText PPM request respectively, as specified by the mappings.

9. If you want to change which field, if any, is dominant for a field mapping, click the value in the Override column for the field mapping of interest, and select another value from the list that appears.

10. If you want to add a pair of fields to the mapping, do the following:

    1. Click Add.

       The Add Field window opens.

    2. In Quality Center Field and OpenText PPM Field, select the fields you want to map to each other.

    3. Click OK.

       The pair of fields is added to the mapping and appears in the list.

    Note: If the mapped fields in a pair have different sets of valid values, you must resolve the differences so that a change to one field can update the other. See Resolving Lists of Valid Values.

11. If you want to remove a pair of fields from the mapping, do the following:

    1. Click a line to select the pair.

    2. Click Remove.

    3. When the application asks whether you want to delete the selected line or lines, click Yes.

12. Click Next to continue.

13. Click Finish to save the mapping and close the wizard.

    The new mapping is displayed in the OpenText PPM-Quality Center Integration Tool. (In the example, expand the defect list.)

14. By default, a local copy of the mapping file (ITGQCIntegration.xml) is saved in the Windows directory in which you installed the OpenText PPM-Quality Center Integration Tool. As discussed later, you will use the tool to deploy the mapping file to the PPM Server and the Quality Center server. Then the integration can operate without any dependency on the local Windows machine on which the integration tool is installed.

    If you want to save the XML mapping file elsewhere, select File > Save To and specify the location.

    If you want to open an XML mapping file stored in another location, click File > Open.

15. Click File > Exit to close the OpenText PPM-Quality Center Integration Tool.