SR-A23035 · Issue 245109
Enabled bulk delete of ADM models
Resolved in Pega Version 7.2.1
In order to support the deletion of ADM models in bulk, an enhancement has been added to remove the unwanted models from the database provided a list of them is given as input. The activity pxDeleteModelsByCriteria has been created; "Used to delete ADM models in bulk. Models to be deleted are determined by the criteria selected by this Activity's parameters; a model is deleted if it matches all selected criteria." PLEASE NOTE: activity is not constrained by Application, only by the criteria provided as parameters. Therefore in most cases you will probably want to constrain by 'applies to' class in addition to the other criteria. Please see the tooltip / description of each parameter for more info on their usage. Integer output parameter 'NumberDeleted' returns the number of models that were successfully deleted."
SR-A23050 · Issue 244774
Rule generation updated to handle related JSONs
Resolved in Pega Version 7.2.1
The system was failing to parse inbound JSONs when the corresponding Pega Data Model was generated using the same JSON, and was unable to use valuelist or pagelist properties for generating JSON to pass to connect-Rest Method. This generation and runtime of rest connector was failing when the same name property existed in multiple places with different modes and same levels. To support this use, the rule generation has been updated to correctly populate the qualifier name along with modified run time code to support mapping when same properties are there in the same class.
SR-A23134 · Issue 243870
Resolved upgrade exception caused by non-standard requestor setting
Resolved in Pega Version 7.2.1
Upgrading to v7.2 was failing if the 'Requestor Types' (DATA-ADMIN-REQUESTOR instances) ACCESS GROUPs had been modified in the previous version for the System Name 'prpc'. This modification caused the PRPC requestors to not be replaced during upgrade. To address this issue, the installation will create a RAP to import into the SDE that will check for this condition, and the PRPC Requestors have been updated such that they cannot be modified. See also: Process Commander V6 help "About Requestor Type data instances" and "When and how to change a system name" for more background information about Requestor Types.
SR-A23178 · Issue 248200
Checkout to branch ruleset handling improved
Resolved in Pega Version 7.2.1
The Checkout to branch option was not able to find a list of branches in Pega Marketing after a minor ruleset migration. To resolve this, the system will make use of a non versioned ruleset name for showing branches if an application is referring a ruleset whose major or minor version is different from the Ruleset of the Rule that is being checked out.
SR-A23208 · Issue 246610
Microsoft Internet Explorer menu highlighting tuned
Resolved in Pega Version 7.2.1
The system has been updated to resolve an Inconsistency with menu highlighting in Microsoft Internet Explorer.
SR-A23222 · Issue 244490
"Deadline date" corrected for German locale
Resolved in Pega Version 7.2.1
When a case was opened, the deadline shown in the top was in the wrong format for a German locale. This was caused by the standard translation method being used, and has been corrected by replacing the non-auto-generated pyCaseDeadline control with pxDateTime control to fix the issue.
SR-A23282 · Issue 245229
Checkout to branch ruleset handling improved
Resolved in Pega Version 7.2.1
The Checkout to branch option was not able to find a list of branches in Pega Marketing after a minor ruleset migration. To resolve this, the system will make use of a non versioned ruleset name for showing branches if an application is referring a ruleset whose major or minor version is different from the Ruleset of the Rule that is being checked out.
SR-A23339 · Issue 247921
Non-versioned class rule forms updated during upgrade
Resolved in Pega Version 7.2.1
The non-versioned class rules in an environment were skipped during upgrade due to an error in the RevalidateAndSave function. This has been corrected.
SR-A23378 · Issue 248193
Max limit removed from OperatorsInWorkGroup
Resolved in Pega Version 7.2.1
The Report Definition pzOperatorsInWorkGroup previously returned a max of 50 records per work group. This created difficulty when using pyTransferAssignment with groups larger than that. In order to facilitate large installations, this limit has been removed.
SR-A23395 · Issue 245032
Optimized decision data components
Resolved in Pega Version 7.2.1
Decision data component performance has been optimized to better handle the heavy demands of the java generated for every mapping using get property and set values API calls in all scenarios.