SR-A14014 · Issue 227004
HTTP Connector API will dynamically set TLS protocol
Resolved in Pega Version 7.2.1
The HTTP Connector was failing to connect using TLS v1.2 protocol due to the SSL Protocol being hardcoded to TLS while setting SSLContext. To fix this, the system will not pass the protocol while instantiating SSLContext, but will leave it to the API to set to highest protocol from JRE.
SR-A14108 · Issue 242466
Better handling for rules considered duplicates
Resolved in Pega Version 7.2.1
A legacy API was not properly resolving rules present in an earlier ruleset version, leading to the creation of additional rules. The system will now consider rules already present in the earlier ruleset version and present the Other duplicate screen asking to skip, overwrite, or rename the rule.
SR-A14267 · Issue 230714
Enhancements to SystemCleaner and SystemPulse
Resolved in Pega Version 7.2.1
Insufficient allocated space for passivation data in a shared filesystem can lead to passivated requestors not being properly cleaned up and possible OOM issues. In order to provide better support, SystemCleaner has been enhanced to better diagnose issues related to insufficient allocation, and any resulting information can be found in deleteExpiredDir in com.pega.pegarules.session.internal.mgmt.base.FilesystemStorage . In addition, when the system pulse is disabled via pxSystemNodeStatus set to Unknown, it would silently run in SMA and no log messages were generated. Since critical agents should provide a more visible indication that the processes are not running as expected, both System Pulse and SystemCleaner have been modified to stop the server startup and report when the server status is unknown.
SR-A14267 · Issue 231247
Enhancements to SystemCleaner and SystemPulse
Resolved in Pega Version 7.2.1
Insufficient allocated space for passivation data in a shared filesystem can lead to passivated requestors not being properly cleaned up and possible OOM issues. In order to provide better support, SystemCleaner has been enhanced to better diagnose issues related to insufficient allocation, and any resulting information can be found in deleteExpiredDir in com.pega.pegarules.session.internal.mgmt.base.FilesystemStorage . In addition, when the system pulse is disabled via pxSystemNodeStatus set to Unknown, it would silently run in SMA and no log messages were generated. Since critical agents should provide a more visible indication that the processes are not running as expected, both System Pulse and SystemCleaner have been modified to stop the server startup and report when the server status is unknown.
SR-A14283 · Issue 232771
Service request retry works in async mode
Resolved in Pega Version 7.2.1
The Retry mechanism has been modified to correctly pass the child requestor's status when service is configured in async mode.
SR-A14307 · Issue 228196
Landing page made unique for delegated rules
Resolved in Pega Version 7.2.1
When one delegated rule is opened and 'Manage change' was selected from the dashboard without closing the opened rule, the first opened rule is getting displayed each time. This was caused by the name in the landing page action not being unique, which has now been changed to ensure the expected results.
SR-A14336 · Issue 230881
Resolved NPE when @checkForSubstitute used
Resolved in Pega Version 7.2.1
If an assignment used the "Check Availability" setting and the operator was not available at that time, a NPE was generated in cases where the timezone needed to be parsed to complete the check. To correct this, the system has been modified to support time zones with more than 3 characters, and support was added for the IST timezone.
SR-A14361 · Issue 227993
Errant "Found spec for PegaRULES (V5.x) configuration" message removed
Resolved in Pega Version 7.2.1
After upgrade, starting JBoss using externalized prconfig.xml logged the error message "Found spec for PegaRULES (V5.x) configuration using System property: D:\jboss\server1\configuration\prconfig.xml". This non-operational message was caused by a out of date code fragment which has now been removed.
SR-A14412 · Issue 229299
Corrected SLA comparisons involving daylight savings
Resolved in Pega Version 7.2.1
A calendar using the "Sao_Paulo" timezone was eliminating the user-entered close dates when calculating SLA times between that calendar and one using "America/NewYork". This was an issue with the parse API not honoring Daylight Saving for some time zones, and handling for that has been added.
SR-A14464 · Issue 228529
Enhancements to SystemCleaner and SystemPulse
Resolved in Pega Version 7.2.1
Insufficient allocated space for passivation data in a shared filesystem can lead to passivated requestors not being properly cleaned up and possible OOM issues. In order to provide better support, SystemCleaner has been enhanced to better diagnose issues related to insufficient allocation, and any resulting information can be found in deleteExpiredDir in com.pega.pegarules.session.internal.mgmt.base.FilesystemStorage . In addition, when the system pulse is disabled via pxSystemNodeStatus set to Unknown, it would silently run in SMA and no log messages were generated. Since critical agents should provide a more visible indication that the processes are not running as expected, both System Pulse and SystemCleaner have been modified to stop the server startup and report when the server status is unknown.