Executive Summary
If you are a Customer Decision Hub client using 1:1 Operations Manager to manage change requests, you may find that your engagement policies can be inadvertently cleared during regular workflow operations when a Change Request is returned to Plan or Build stages.
Background:
The root cause occurs when you use the rollback mechanism during "Return to Build” or “Return to Plan" operations. If you manage change requests in this way, the system may mistakenly remove both your unedited and edited criteria. As a result, engagement policy values you haven’t changed can be lost, even if you made no updates to the applicability settings.
How can I determine if I’m affected?
You are affected if:
-
You use Customer Decision Hub versions 24.2.x, 24.1.x, or 23.x.x
-
You utilize 1:1 Operations Manager for business change management
-
Your actions have engagement policies configured
-
You perform "Return to Build” or “Return to Plan" operations
If you are NOT using 1:1 Operations Manager, then this issue does NOT affect you.
|
Hotfix Reference |
Root Cause Analysis |
Customer Impact |
Resolution |
|---|---|---|---|
|
HFIX-C2526 (24.2) HFIX-C2527 (24.1) HFIX-C2529 (23) |
Rollback mechanism incorrectly removing unedited criteria along with edited ones, causing data loss |
Critical severity issue affecting customer's ability to maintain engagement policy configurations, potential for data loss and workflow disruption |
Apply appropriate hotfix - Added validation logic to ensure cleanup process only affects modified criteria, preserving unedited values during rollback operations |
Obtaining your hotfix
If you are affected by this issue, please review the above hotfix and take appropriate action.
If you are a Pega Cloud client, your Pega Cloud® environments are being proactively remediated by Pega. Cloud Maintenance (CM) cases are being created for each of your environments which provides the schedule of when the hotfixes will be applied.
If you are a United States Pega Cloud for Government (PCFG) client, Cloud Change (CC) cases are being created for the hotfix, which will be applied by Pega.
If you are an on–premises or client managed cloud client, please submit a hotfix request using My Support Portal. As always, be sure you have appropriate backups in place before applying the hotfix.
For any questions, contact Global Client Support via My Support Portal.