Data Sharing

The integration allows data sharing between OpenText PPM and QC/ALM. Business managers and IT personnel using OpenText PPM gain visibility into how a project is affected by both the quality control process and the parameters that are collected in QC/ALM. They can use QC/ALM capabilities when creating requests for changes.

  • Synchronization of mapped field values between OpenText PPM and QC/ALM. When fields are mapped between a OpenText PPM request type and a QC/ALM defect or requirement, changing the value of a mapped field in one application can automatically change the value of the associated field in the other application. For example, when you change the status of a request related to defects to Fixed in OpenText PPM, the status of the associated QC/ALM project defect changes to Fixed.

    Users can specify that one of the following occurs for any pair of mapped fields:

    • Changing the value of the field in the QC/ALM defect or requirement automatically updates the value of the mapped field in the OpenText PPM request accordingly, that is, QC/ALM is dominant for (controls) the pair of mapped fields.

    • Changing the value of the field in OpenText PPM request automatically updates the value of the mapped field in the
      QC/ALM defect or requirement accordingly, that is, OpenText PPM is dominant for (controls) the pair of mapped fields.

    • Changing the value of the field in either application automatically updates the value of the mapped field in the other application accordingly, that is, the field mapping is bidirectional.

    Synchronization of defects enables the following:

    • Developers can use OpenText PPM to manage the defect-fixing process, while QA personnel continue to use QC/ALM.

    • Project managers and IT managers can view all the defects in the system, whether the defects originated in OpenText PPM or in QC/ALM. This helps the managers to decide on content for the next release or new requirements and enhancements.

    • QA personnel can use QC/ALM to manage defects created through OpenText PPM.

  • Request hierarchy synchronization. The hierarchical structure of requirements in QC/ALM can be synchronized with the structure of the associated requests in OpenText PPM. That is, you can force the QC/ALM requirement hierarchy to match the OpenText PPM request hierarchy automatically.

  • Synchronization with OpenText PPM notes. The integration allows you to synchronize a notes-related field in QC/ALM with notes in the associated OpenText PPM request. When you update the content of the notes in a OpenText PPM request, the associated notes field in QC/ALM is updated.