Changes with the Entities in PPM Version 9.20 and Later

This section describes changes with the entities in PPM version 9.20 or later.

Caution: If you already deployed an older version ALM content bundle on an earlier version of PPM, do NOT deploy the new version ALM content bundle. Otherwise you may risk losing data of your existing integrations after you upgrade Quality Center from version 10.00 to ALM 11.x.

The following two request status are added to the workflow template:

  • 3-Test Lab Setup Completed

  • 5-Test Execution Completed

Caution: Do not use the ALM - Request for Change workflow template provided in the ALM content bundle directly. The workflow template provided aims to act as a template to minimize your workflow creation effort.

To create your own workflow based on the workflow template,

  1. Customize the ALM - Request for Change workflow template by adding the following two request statuses to appropriate workflow steps as needed:

    • 3-Test Lab Setup Completed

    • 5-Test Execution Completed

    If the two request status do not exist, go to the Request Type Workbench and add two request status to applicable request types. For detailed instructions, see the Demand Management Configuration Guide.

  2. Add necessary access grants and user groups to each of the modified steps.

The following entities were renamed since PPM version 9.20 to reflect its support for Quality Center's new version, the standard edition of Application Lifecycle Management (ALM):

  • The QC/ALM Defect Information field group and its fields (see Table 6-4)

  • The QC/ALM Info field group and its fields (see Table 6-5)

    • Table 6-4. The QC/ALM Defect Information field group and its fields

    Field Name in 9.10 or earlier

    Field Name in 9.20 or later

    Quality Center Defect Information field group

    QC/ALM Defect Information field group

    Quality Center Instance

    QC/ALM Instance

    Quality Center Domain

    QC/ALM Domain

    Quality Center Project

    QC/ALM Project

    —

    Synchronize to QC/ALM Defect (added in 9.20)

    Defect Number

    QC/ALM Defect Number

    Quality Center Defect Status

    QC/ALM Defect Status

    Quality Center Message

    QC/ALM Integration Message

    —

    QC/ALM Assigned To User a

    (added in 9.12)

    Quality Center Attachments

    QC/ALM Attachment URL

    Detected in Quality Center by

    Detected in QC/ALM by

        a.    For integration configurations upgraded from QC 10, to add the new fields to your existing request types, you can run the script provided with PPM version 9.20 or later to update the existing request types: <PPM_Home>/bin/kUpgradeIntegrationRequests.sh.

    Note that the script does not update the field names.
    Table 6-5. The QC/ALM Info field group and its fields

    Field Name in 9.10 or earlier

    Field Name in 9.20 or later

    Quality Center Info field group

    QC/ALM Info field group

    Quality Center Instance

    QC/ALM Instance

    Quality Center Domain

    QC/ALM Domain

    Quality Center Project

    QC/ALM Project

    Quality Center Assigned To User

    Assigned To

    Quality Center Requirement No.

    Requirement No.

    Quality Center Status

    Requirement Status

    Quality Center Message

    Requirement Integration Message

    —

    Synchronize to QC/ALM Requirement a (added in 9.20)

    Quality Center Attachments

    Requirement Attachment URL

    —

    QC/ALM Requirement Type a

    (added in 9.20)

    —

    QC/ALM Dashboard Subject (not in use)

    —

    QC/ALM Requirements Coverage (not in use)

    —

    QC/ALM Open Defects (not in use)

        a.    For integration configurations upgraded from QC 10, to add the new fields to your existing request types, you can run the script provided with PPM version 9.20 or later to update the existing request types: <PPM_Home>/bin/kUpgradeIntegrationRequests.sh.

    Note that the script does not update the field names.

Although the two field groups were renamed respectively since PPM version 9.20, upgrading an existing integration configuration does not upgrade the names of the field groups and their field names. They still remain the same as before. The new field groups and their fields apply to new integration configurations you add in PPM version 9.20 or later.