SR-A77514 · Issue 253486
@baseclass!pyMemo has been made available
Resolved in Pega Version 7.2.2
Opening up property pyMemo (which applies to Link-) and trying to save it into a custom ruleset generated an error due to @Baseclass having a final version of pyMemo. To correct this, @baseclass!pyMemo has been made available.
SR-A80686 · Issue 256090
StartCase correctly searches parent cases
Resolved in Pega Version 7.2.2
Test cases created for pyStartCase flow are saved with insname as pyStartCase, but during "record from assignment" parent test cases are searched with the flow name where the assignment is present. That resulted in no parent test cases being returned. To fix this, the activity has been modified so the parent test cases are searched to pass "pyStartCase" as a Top Level Flow Name when using "record from assignment" from pyStartCase flow.
SR-A95291 · Issue 273667
Deprecated Access Groups documentation updated
Resolved in Pega Version 7.2.2
The documentation lead-in to the Deprecated Access Groups section has been updated for clarification: These access groups are retained after upgrades to support applications created in Version 4.2 and Version 5.X systems. They are deprecated and not recommended for continued use. These access groups appear only on systems that are upgraded from PRPC 6.x or earlier.
SR-A88270 · Issue 261496
Memo text picks up translated value
Resolved in Pega Version 7.2.2
The localized text was not being correctly picked up when trying to capture the history of an instance using pyTrackSecurityChanges trigger and DataTransform and referencing the Pagelist values in DataTransform. To resolve this, the RUF addMemoForSecurityChangeTracking has been updated to better handle page/page-list property, however, it is strictly one level nesting (parent page > child page). Embedded properties nested more than 1 level would not be handled by this code.
SR-A89757 · Issue 258597
SaveAs history carries previous version and ruleset info
Resolved in Pega Version 7.2.2
When saving as a rule from particular version, the rule history did not correctly carry over the information about the origin ruleset version (Previous version and ruleset) This was an error caused by recent changes to the WBSaveAs record management API, and has been fixed with new parameters added to "call SaveAs" on Rule-!WBSave into the record management API.
SR-A100376 · Issue 271177
History classes show in app explorer
Resolved in Pega Version 7.2.2
While searching for the rule (for e.g. "displaybulkaction") from the rule search window, it was possible to look up the instances in the OOB history classes but the rules did not show up in the app explorer. This was due to a condition in the following Report Definitions that indicated rules which belonged to the class that starts with 'History-' should not be shown: -PZGETAPPCATEGORIES -PZGETAPPRULES -PZGETAPPRULETYPES This condition has now been removed.
SR-A100376 · Issue 271369
History classes show in app explorer
Resolved in Pega Version 7.2.2
While searching for the rule (for e.g. "displaybulkaction") from the rule search window, it was possible to look up the instances in the OOB history classes but the rules did not show up in the app explorer. This was due to a condition in the following Report Definitions that indicated rules which belonged to the class that starts with 'History-' should not be shown: -PZGETAPPCATEGORIES -PZGETAPPRULES -PZGETAPPRULETYPES This condition has now been removed.
SR-A87552 · Issue 257706
Implicit privileges do not generate warnings
Resolved in Pega Version 7.2.2
RARO with implicit privileges was generating warnings that affected the compliance score. There is a particular format for declaring implicit privileges. i.e. Classname:ruleName, and the system has been updated with a check for this so implicit privileges will not be adding any guardrail warnings.
SR-A102469 · Issue 271467
Application Profile correctly updates case type description
Resolved in Pega Version 7.2.2
When creating a new application profile document, the old case type descriptions were shown instead of new updated ones; this has been corrected.
SR-A101006 · Issue 272734
JDBC password handling corrected
Resolved in Pega Version 7.2.2
After upgrade, a JDBC database connection on WebSphere 8.5/Oracle 11G indicated success on test connection, but a username/password "connection could not be obtained" error was thrown when attempting to save the connection. This was due to the handling of the encrypted password, and has been fixed.