Overview
The CS archival API was not deleting associated orchestration step criteria during the archival process, resulting in large numbers of orphan records and negatively impacting storage utilization. This was identified as a defect, and a fix was implemented in patch version 33.6.19 to include Conditional_Step_Criteria__c records in the archiving and deletion process.
Information
Issue: CS archival API not deleting associated orchestration step criteria, resulting in orphan records.
Affected Version: Prior to patch 33.6.19
Fixed in Version: Patch 33.6.19
Resolution Steps:
-
Verify Your Current Version:
- Check if you are running a version prior to patch 33.6.19 where this defect was present.
-
Install the Patch:
- Install patch version 33.6.19 from the following link: /packaging/installPackage.apexp?p0=04tDp000000JMDZ
-
Post-Installation Steps:
- Verify that Conditional_Step_Criteria__c records are now included in the archiving and deletion process.
- Run a query to ensure no orphan records remain (delete if there are any):
SELECT id FROM CSPOFA__Conditional_Step_Criteria__c WHERE CSPOFA__Orchestration_Step__c = null
-
Verify Resolution:
- Confirm that the archival process now correctly deletes associated orchestration step criteria.
- Check storage utilization to ensure it reflects the removal of orphan records.
Note: If issues persist after installing the patch, please contact support for further assistance.
Frequently Asked Questions
- How do I know if this issue affects my system?
- You will notice a significant number of orphan records and increased storage utilization due to the CS archival API not deleting associated orchestration step criteria.
- What version includes the fix for this issue?
- The fix is included in patch version 33.6.19.
- What should I do if the issue persists after installing the patch?
- If the issue persists, please contact support with details of the problem and any error messages you encounter.
Matej Storga
Comments