Related objects and associated source members not deleted in target environments

Products

• CA 2E

Issue/Introduction

We performed the following

a) Check out the object from *PRD to *TST in PTC Implementer, for the purpose of "Delete".
b) Promote the lock across from *TST to Target Environments (*QAC/Local *PRD/Remote *PRD).

The lock is promoted successfully to the Target Environments but the related objects associated with the delete lock and the corresponding source members are not deleted. This leads to redundant objects and source members in the Target environment libraries. These objects are now standalone independent objects and are no longer audited/tracked in Implementer. How can we get rid of these redundant objects and source members in the Target environment linraries?

Environment

2E: r8.7 GA, r8.7 + CUM PTF A, r8.7.1, r8.7.2, r8.7.3, r8.7.4
Implementer: 12.5, 12.6

Cause

Some oversights in the 2E CM and PTC Implementer integration.

Resolution

Please open a support case with Broadcom Support for a fix to address this issue.