SR-C88711 · Issue 439596
Handling added for exception caused by empty page list
Resolved in Pega Version 8.2.2
Attempting to map an auto-populated pageList property in a data transform was throwing a java IndexoutofBoundException. Investigation showed that the system was trying to access the second element of an empty Page List. To resolve this, the system has been updated to use a flat list DataProvider which will return null if the list does not exist rather than return a list that is not associated with the parent page.
SR-C86457 · Issue 482083
Handling added for identifying and passivating disconnected Requestors
Resolved in Pega Version 8.2.2
An issue was seen with restarted nodes where disconnected Requestors were not being properly passivated due to Passivation Blocker permissions persisting with a non-zero value. Requestors are passivated only if permissions are zero. To correct this, code has been added to identify and correctly reset permissions for Requestors that have not been properly decremented to zero.
SR-D8650 · Issue 475300
Handling added for null sort order in file import metadata
Resolved in Pega Version 8.2.2
A NullPointerException was seen while fetching the sort order of indexes during a file import. This was caused by a null being returned for an index that did not have the sort order in the metadata, and has been resolved by adding a null check; if the metadata of the index returns "null" as sort order, then the order will be set to "A".
SR-D9119 · Issue 481687
Handlng improved for rollback of Hfix with dependent HFixes
Resolved in Pega Version 8.2.2
Attempting to rollback an HFix with dependent HFixes resulted in a Hazelcast jar exception. Investigation showed the DL included the same jar multiple times in the dependent hotfixes, which was a result of how the DL was created via the hotfix process. In order to better handle this scenario, when there are multiples of the same entries to delete the message will be logged and the process will continue if the entry is not found in the database.
SR-C93264 · Issue 437310
Inference engine enabled to resolve JourneyManager data flow exception
Resolved in Pega Version 8.2.2
Customer environments were intermittently seeing an exception with the error "Could not get ultimate primary destination for data flow .DF_JourneyManager" when trying to compile an activity that ran a dataflow that ultimately called the DF_JourneyManager data flow. This error was traced to the Inference engine being in a disabled state so the system was not able to get the dataflow output class via declare expressions. The Inference engine has now been enabled to resolve this issue.
SR-D3604 · Issue 439096
Parameter support added for openAssignment
Resolved in Pega Version 8.2.2
An enhancement has been added that will allow leveraging the Associate Requestor for Chat interactions through parameter support for the openAssignment action. This will allow an activity to be called to create the interaction and pass back the assignment and open it using the openAssignment API.
SR-D9160 · Issue 446526
Pega-RULES session decryption issue resolved
Resolved in Pega Version 8.2.2
When the Pega-RULES session encryption key was updated (rotated) after 90 days by the pyValidateKMSMetadata agent, the in-memory version of the key was then corrupted leading to a failure to decrypt the session header. This had the result of preventing any users from logging into the system. Users could connect to the login page and enter their credentials, but after clicking the Login button they were redirected back to the starting login page and their credential information was cleared. This was traced to the pulse change of SystemCDK moving the encryption and decryption process to inconsistent state where the CurrentSystemEncryptKeyIDHash still contained the old CDK ID.To resolve this, the system has been updated to use only ActiveKeyID instead of the previous behavior of using both ActiveKeyID and CurrentSystemEncryptKeyIDHash.
SR-D898 · Issue 435997
Pega0069 alert accuracy resolved for UHC FinishAssignment
Resolved in Pega Version 8.2.2
Pega0069 alerts were not raised for the CS commit and confirm harnesses, and the reported total duration was not always accurate. This has been resolved by capturing document busy/idle for CS harnesses.
SR-D9132 · Issue 461283
Performance improvements for EventStoreWriter class
Resolved in Pega Version 8.2.2
The cache protocol has been modified In order to improve performance for the EventStoreWriter class.
SR-D9511 · Issue 465301
pyPreTriage and pyPostTriage flows now default to Draft Mode Off
Resolved in Pega Version 8.2.2
The out-of-the-box pyPreTriage and pyPostTriage flows had draft mode turned on. Due to this, Email Triage cases in production systems were sent into the problem flow. This has been corrected by turning off draft mode for pyPreTriage and pyPostTriage flows.