SR-A91743 · Issue 259136
Security update for pxInitials control
Resolved in Pega Version 7.2.2
XSS (Cross Scripting Filter) has been added for potentially exploitable parameters in the pxInitials control.
SR-A99962 · Issue 266646
Wait enhanced to maintain case status for multiple children
Resolved in Pega Version 7.2.2
A Parent case that was configured to resume when the sub-case reached a particular status using "Pending-ParentCaseResume" was not working as expected if there were multiple child cases for a single parent. This was due to the Wait shape taking the current status of the activator (first child case resolved) instead of the dependency status for which the wait shape should be looking for (subsequent child case), and has been fixed by establishing a new property on the Activator page to hold the dependency status and rely on this while checking if the activator has crossed the desired status.
SR-B1873 · Issue 271608
Fork shape works with both when and percentage connectors
Resolved in Pega Version 7.2.2
An error was generated when trying to save a flow rule that contained both percentage connectors and When rules fork shapes. This was due to the 'ValidateModelProcess' activity getting all connectors in the flow and checking if there is at least one connector with Percentage, then iterating each decision shape by iterating the connectors and checking for percentage error scenarios. To fix this issue, the system will get the connectors from the decision shape in context and check if at least there is one percentage connector, then check for validation after that.
SR-B238 · Issue 271610
Fork shape works with both when and percentage connectors
Resolved in Pega Version 7.2.2
An error was generated when trying to save a flow rule that contained both percentage connectors and When rules fork shapes. This was due to the 'ValidateModelProcess' activity getting all connectors in the flow and checking if there is at least one connector with Percentage, then iterating each decision shape by iterating the connectors and checking for percentage error scenarios. To fix this issue, the system will get the connectors from the decision shape in context and check if at least there is one percentage connector, then check for validation after that.
SR-A100811 · Issue 271627
Breadcrumbs display consistently
Resolved in Pega Version 7.2.2
Case stage breadcrumbs intermittently did not display when a work item was opened. This has been corrected by updating pxDisplayStages(Pega-EndUserUI rule set) to change from grid source to data page source and pass the the pzInsKey parameter.
SR-A98885 · Issue 265576
UpdateCalculationLabel modified to get embedded property label
Resolved in Pega Version 7.2.2
In Case Default rule -> open calculation tab, the calculated property field has a maximum value of 64 characters. In order to allow the setting of an embedded property as a target value (which would exceed the 64 character limit), pyUpdateCalculationLabel has been modified to get the label of the embedded property.
SR-A99757 · Issue 265774
UpdateCalculationLabel modified to get embedded property label
Resolved in Pega Version 7.2.2
In Case Default rule -> open calculation tab, the calculated property field has a maximum value of 64 characters. In order to allow the setting of an embedded property as a target value (which would exceed the 64 character limit), pyUpdateCalculationLabel has been modified to get the label of the embedded property.
SR-A96555 · Issue 264154
RequiredSkills Declare Index fixed for Federated Case Manager
Resolved in Pega Version 7.2.2
In Federated Case Manager, skill-based routing of assignments to a workbasket generated a pyCommitError indicating "Cannot save instance of class Index-AssignmentSkills-Federated". This was due to missing index table properties needed by the Index-AssignmentSkills-Federated.RequiredSkills declare index, and has been fixed.
SR-A94737 · Issue 265585
Correspondence updated with party role change from dropdown
Resolved in Pega Version 7.2.2
On changing the party role from the drop down, the value was not updated in the correspondence. This was due to CreateSelectedCorr activity only being called when the correspondence was changed in the drop down, and has been resolved by regenerating the correspondence view any time an edit is selected and submitted.
SR-A94737 · Issue 265371
Correspondence updated with party role change from dropdown
Resolved in Pega Version 7.2.2
On changing the party role from the drop down, the value was not updated in the correspondence. This was due to CreateSelectedCorr activity only being called when the correspondence was changed in the drop down, and has been resolved by regenerating the correspondence view any time an edit is selected and submitted.