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-A14313 · Issue 227652
Autocomplete displays properly after screen rotation
Resolved in Pega Version 7.2.1
A black gap appeared on the screen of iPad and iPhone devices when tying to use the autocomplete window after the screen was rotated between Portrait and Landscape modes. This was due to the autocomplete popover not accepting a % width setting, and the display method of the popover has been modified to display properly.
SR-A14325 · Issue 228543
Repositioned BusyIndicator to cover Target element
Resolved in Pega Version 7.2.1
If the section with busy indicator was taller than the viewport height, the busy indicator mask did not cover the lower part of the section when scrolling and the section was editable. This has been fixed by repositioning the mask to cover the part of the section editable in the viewport and also show immediately on scroll.
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-A14359 · Issue 232227
Context-aware paths for SMA jmxclient.css and global.js files
Resolved in Pega Version 7.2.1
In some cases the jmxclient.css and global.js files were not found when running SMA due to the use of relative path names. The path names have now been made context-aware.
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.