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-A14132 · Issue 232550
Improved handling for values starting with "." in Developer Portal Explorer
Resolved in Pega Version 7.2.1
A value starting with "." was being treated as a property and causing an exception error when using the Recent Explorer in the Developer portal. A catch has been added to resolve this issue.
SR-A14132 · Issue 233457
Improved handling for values starting with "." in Developer Portal Explorer
Resolved in Pega Version 7.2.1
A value starting with "." was being treated as a property and causing an exception error when using the Recent Explorer in the Developer portal. A catch has been added to resolve this issue.
SR-A14151 · Issue 244440
Autocomplete select updates as expected
Resolved in Pega Version 7.2.1
An intermittent problem was found with autocomplete that selected a previously set value if text was typed in the autocomplete box and the value was selected instead of the search text. This was traced to a press of the capslock key being interpreted as an unprintable character, causing an abort of the request and change tracker not having the correct update. The function processkey of autocompleteag.js has now been updated to not abort the request when a non-printable character is typed.
SR-A14168 · Issue 230039
Unique page names generated for nested child work items
Resolved in Pega Version 7.2.1
When multiple child work items were created using pxAddChildWork in one transaction, the same page name was getting used and causing errors. This has been fixed by making pagename unique by appending currentdatetime.
SR-A14230 · Issue 230423
IconRequired fixed for repeating layouts
Resolved in Pega Version 7.2.1
The iconRequired span was only being generated for the first row of any repeating layout structure. This has been fixed in the GenerateCellContent RUF.
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.