INC-135195 · Issue 598071
PD4ML library updated
Resolved in Pega Version 8.5.2
When generating a PDF from a report definition with more than 1000 records, the system would hang abruptly and stop responding. There was also a noticeable size difference in the generated file. This was an issue with the included version of PD4ML, and has been resolved by updating the version from 4.0.6 to 4.0.9fx1.
SR-C80948 · Issue 421766
ProfileLink control updated to resolve opening issue
Resolved in Pega Version 8.1.4
The profile was not opening when the Operator Profile link was clicked. This was traced to certain functions having been moved to javascript files that were not included by default in the ProfileLink control. To correct this, the control has been modified to include the needed javascript files and the appropriate references have been updated to match.
SR-C86213 · Issue 424585
Corrected PRAuth URL handling for sessions on restarted nodes
Resolved in Pega Version 8.1.4
If a user session was in progress and the node restarted, attempting to refresh the session when the node came back up was not working. Launching a new browser session cleared the problem. A trace showed that the Authentication Selector screen was not loading because the PRAuth URL redirection was going into an infinite loop, and this has been corrected.
INC-180594 · Issue 670957
Filtering added for DisableDormantOperators
Resolved in Pega Version 8.7
When running the Disable Dormant Operators agent, many operators were seen which were dormant but not disabled. Investigation showed the activity was fetching all of the operators without filtering the deactivation state. This has been resolved by adding a filter condition in pzDisableDormantOperators to fetch only deactivate state users.
INC-175205 · Issue 652531
Agent restart made more resilient
Resolved in Pega Version 8.7
During a timeout outage, agents intermittently encountered a NoClassDefFound error and were disabled. After the database connection was restored, the agents were not automatically restarting. This has been resolved by making the code more resilient to errors; agent will be restarted when a temporary issue is detected, and the restart will be immune to most exceptions.
SR-A16256 · Issue 231874
Exception recovery added to PegaAESRemote
Resolved in Pega Version 7.2.1
The presence of a bad or missing data-admin-db-table was causing an exception and exit when the PegaAESRemote agent sent data to PDC or AES to support analysis. The code has now been updated to handle the exception and continue to build the XML and send it across to PDC/AES.
SR-A21322 · Issue 241736
CaseDesigner SLA flows updated for MSSQL and PostgreSQL compatibility
Resolved in Pega Version 7.2.1
When the SLA for a process in Case Designer is given the internal flow(pzInternalProcessFlow) as companion flow for the process, the order of pxFlow pages is different on the pyWorkPage between MSSQL and PostgreSQL based 7.2 systems. This was due to the differences in iterating these loops and removing the completed flows, and the system has been updated to produce consistent results.
INC-146564 · Issue 607856
DX API returns application specific validation messages
Resolved in Pega Version 8.5.2
When trying to validate the input swagger details with application specific conditions, the create case DX API did not return the validation messages from application but instead returned a "500 Internal Server Error". Investigation showed that the error parameter was not set on validation fail, and this has been corrected.
INC-189781 · Issue 677816
Database Transaction Log update overflow resolved
Resolved in Pega Version 8.7
When automatic.resume=false was encountered during an update, cleaning up the existing codeset from previous updates ended up filling up the database transaction logs and caused the update to fail. This has been resolved by updating the process of clearing the codeset so it doesn't overflow the transaction log.
SR-A15388 · Issue 231184
Reordered email encryption logic
Resolved in Pega Version 7.2.1
Encrypted email sent using the out-of-the-box Activity "@baseclass.SendEmailNotification.Pega-EventProcessing:07-10-09" to send out encrypted (s/mime) emails generated emails that could not be decrypted on the receiving end. This was an error caused by the getCertificate activity not being able to read the certificate from keystore, and the logic of pyGetEmailCertificates had been reordered such that the encryption and signing params/logic in SendEmailMessage do not conflict with one another.