SR-A13464 · Issue 227723
Tracer updated to handle encrypted URLs
Resolved in Pega Version 7.2.1
Tracer was not working properly when encrypting URLs. To resolve this, the URL will be obtained from the clipboard property instead of depending on the URL when encryption is present.
SR-A13472 · Issue 231026
History tables updated for deletion and importing.
Resolved in Pega Version 7.2.1
The history table was not properly updated for actions on Data tables when deleting or importing new records using the pzDeleteRecord activity. There were no problems for adding or updating. Previously, pzDeleteRecord activity did not modify the history table, and that tracking has been added so that activity can be used in this manner.
SR-A13691 · Issue 231105
Corrected race condition in rapid LoadDataPage requests
Resolved in Pega Version 7.2.1
If the the same Requester-level data page was rapidly invalidated and reloaded by means of "Load-DataPage", a race condition between the background requestor and main requestor caused some pending requests to be overwritten by new incoming requests before the previous load request were serviced. As a result, information was lost. This has been resolved by ensuring every queued job's ID is different and thereby never conflicts.
SR-A13784 · Issue 235357
RedirectAndRun URL built with CSRF token
Resolved in Pega Version 7.2.1
Using RedirectAndRun with CSRF enabled and redirecting to a different thread resulted in a missing CSRF token because the URL was constructed before the initialization of the thread object. The sendHttpRedirect() API has been modified to construct the URL once the thread has been initialized.
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-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.