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-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-A14386 · Issue 230949
Fixed issue with CSS incorrectly overriding skin rule
Resolved in Pega Version 7.2.1
The skin rule settings "Error Border" and "Error Background" were not having any effect on a text control which contained a validation error. This was an issue with the ErrorShade element being overridden my more specific CSS even though the HTML that used that CSS was never produced at run time. This has been corrected.
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.
SR-A14493 · Issue 227902
Clipboard viewing on SMA fixed
Resolved in Pega Version 7.2.1
Any user having Manager as the default portal was having difficulty viewing the clipboard pages. This was due to the XML being generated incorrectly for the clipboard of requestors with more than one thread open in them. This has been fixed.
SR-A14562 · Issue 231191
Enhanced logging to debug Composite Portal Menu rendering errors
Resolved in Pega Version 7.2.1
In order to better diagnose exceptions generated when trying to render a Section from Composite Portal Menu, more debug logs have been added when DatabaseImpl.open is called on any particular instance. The debug logs will print the authorization related information - the ruleset list, the current thread, current access group etc.