Other Added Functionality to the Integration

  • Synchronize QC/ALM text fields containing 4000 or more bytes to PPM text fields

    When QC/ALM to PPM synchronization is performed, the content from
    QC/ALM text fields with text length greater than 4000 bytes (in UTF-8 encoding) is automatically truncated down to 4000 bytes when populating corresponding PPM text fields.

    To prevent the original content in the QC/ALM text fields from being truncated in future synchronizations, set the text field mapping control to QC/ALM. This ensures that truncated content in the PPM text fields not to be synchronized back to QC/ALM text fields.

  • Synchronize QC/ALM defect or requirement status to PPM request status. Status changes of QC/ALM defect or requirement can also trigger corresponding PPM request workflow steps or actions, thus changing status of the PPM requests.

  • Synchronize multi-value fields (for example, drop-down list values,
    QC/ALM list field, and PPM auto-complete list) bi-directionally.

  • Synchronize PPM usernames, instead of full names, to QC/ALM.

  • Synchronize QC/ALM requirement types to PPM requests. Changing the requirement type field value in QC/ALM updates the requirement type field value in PPM requests.

  • Automatically submit the PPM request created as a result of creating a defect in QC/ALM.

  • For integration of PPM request type and QC/ALM defect, a third option for bi-directional integration is available in the Integration Options section on the Configure QC/ALM Integration for Request Type page: Creating a PPM request automatically creates an associated QC/ALM entity and vice versa.

  • Special characters and HTML tags contained in QC/ALM fields can display properly on the Configure QC/ALM Integration for Request Type page, including, but not limited to, the follows:

    ~ ! @ # $ % ^ & * ( ) _ + { } | " : ? < > / . , ; ' \ ` [ ] - =

    However, for security concern, We strongly recommend you NOT use angle brackets and square brackets (<>, []).