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-A99521 · Issue 266569
Localization added to DisplayStages
Resolved in Pega Version 7.2.2
Localization has been added to 'Show all steps' and 'Hide Steps' in pxDisplayStages.
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.
SR-A91802 · Issue 260001
Apache Struts JARS updated to improve security
Resolved in Pega Version 7.2.2
The Apache Struts JARs have been updated to resolve the following potential security vulnerabilities: The REST plugin in Apache Struts 2 2.3.20 through 2.3.28.1 allows remote attackers to execute arbitrary code via a crafted expression. Apache Struts 2 2.3.20 through 2.3.28.1 mishandles token validation, which allows remote attackers to conduct cross-site request forgery (CSRF) attacks via unspecified vectors. The URLValidator class in Apache Struts 2 2.3.20 through 2.3.28.1 and 2.5.x before 2.5.1 allows remote attackers to cause a denial of service via a null value for a URL field.
SR-A97544 · Issue 267587
Calendar Gadget has correct start date after Daily to Weekly switch
Resolved in Pega Version 7.2.2
The Calendar Gadget was not working as expected in Weekly Mode. This was traced to the selected day in Daily mode being considered the first day of the week when the gadget was switched to Weekly mode, leading to open tasks being displayed against wrong dates in Weekly mode. This has been fixed by adding logic to calculate the first day of week when the gadget is switched to Weekly mode.
SR-A97544 · Issue 268332
Calendar Gadget has correct start date after Daily to Weekly switch
Resolved in Pega Version 7.2.2
The Calendar Gadget was not working as expected in Weekly Mode. This was traced to the selected day in Daily mode being considered the first day of the week when the gadget was switched to Weekly mode, leading to open tasks being displayed against wrong dates in Weekly mode. This has been fixed by adding logic to calculate the first day of week when the gadget is switched to Weekly mode.
SR-A99330 · Issue 267808
Calendar Gadget has correct start date after Daily to Weekly switch
Resolved in Pega Version 7.2.2
The Calendar Gadget was not working as expected in Weekly Mode. This was traced to the selected day in Daily mode being considered the first day of the week when the gadget was switched to Weekly mode, leading to open tasks being displayed against wrong dates in Weekly mode. This has been fixed by adding logic to calculate the first day of week when the gadget is switched to Weekly mode.