Issue
On reusing a Case ID during work object creation, a duplicate key exception does not display. The existing work object data is overwritten with the new work object details, resulting in data loss.
Symptoms and Impact
Existing work objects are overwritten with new work object data. Multiple “Item Created” history records are associated to a work object.
Steps to Reproduce
- Perform an action that results in reusing the case ID when creating a work object. Examples of such actions can include (but are not limited to):
- Incorrect customization of the OOTB GenerateID activity.
- Importing work objects from other environments without adjusting the Data-UniqueID instances to account for the imported IDs.
- Manually adjusting the Data-UniqueID instances to decrease pyLastReservedID.
- Create a work object with an ID that was used previously.
Root Cause
This is a Pegasystems defect where the newObject parameter for determining if the work object is new was not being set.
Solution
Perform either of the following:
- Avoid actions that result in ID reuse.
- Update to:
- Pega Platform™ 23.1.3
- Pega Platform 24.1.1
Environment
Versions found in
The problem was reported in the following environments:
- Pega Platform 8.6.3
- Pega Platform 8.7.2
- Pega Platform 8.7.5
- Pega Platform 8.8.2
- Pega Platform 8.8.3
- Pega Platform 8.8.4
- Pega Platform 8.8.5
- Pega Platform 23.1.0
- Pega Platform 23.1.1
- Pega Platform 23.1.2
Version fixed in
- Pega Platform 23.1.3
- Pega Platform 24.1.1