SR-A4308 · Issue 211808
Corrected revalidateAndSave modifying the 'Applies to' class
Resolved in Pega Version 7.1.9
During upgrade, revalidateAndSave was modifying the 'Applies to' class of the included rule. The issue was caused by modification of the pyIncludedRuleXML in the flow action / section rules that holds the included section's information; flow action was depending on this page to set the class, but since this page no longer existed the class was defaulting to the current flow action's primary class. To resolve this, if pyPrompt class is blank in activity Rule-Obj-FlowAction.OpenDefaults, the system will try to get the page name from the flow action rule, iterate across its pages and classes, and find the class name where the page name matches and set that as the applies to class for the flow action's section.
SR-A4840 · Issue 212310
Resolved privilege issue for Attach Rule
Resolved in Pega Version 7.1.9
A RuleNotFound error was generated if a 'when' rule was part of a custom attachment category rule (specified for access control) and there was an attempt to add an attachment when the WO was opened in Review mode or if an attachment was being added to a resolved WO. Due to the error, the customer category was not then available in the category drop down list. This was due to GetListOfAttachmentCategories referring to newAssignPage to get the reference page and failing the privilege check. This has been resolved by updating the steps to default to pyWorkPage for the local variable.
SR-A4940 · Issue 211386
Improved performance for large History-Work reports
Resolved in Pega Version 7.1.9
When History-Work- contained a very large number of rows, performance issues were seen while running the History-Work-.pyGetStatusChanges report. To resolve this, the RD History-Work-.pyGetStatusChanges has been updated with modified filtering conditions and improved error handling for blank param.InsKey fields.
SR-A5054 · Issue 211505
Corrected revalidateAndSave modifying the 'Applies to' class
Resolved in Pega Version 7.1.9
During upgrade, revalidateAndSave was modifying the 'Applies to' class of the included rule. The issue was caused by modification of the pyIncludedRuleXML in the flow action / section rules that holds the included section's information; flow action was depending on this page to set the class, but since this page no longer existed the class was defaulting to the current flow action's primary class. To resolve this, if pyPrompt class is blank in activity Rule-Obj-FlowAction.OpenDefaults, the system will try to get the page name from the flow action rule, iterate across its pages and classes, and find the class name where the page name matches and set that as the applies to class for the flow action's section.
SR-A903 · Issue 204613
Added handling for agent activity with no primary page
Resolved in Pega Version 7.1.9
Running an agent activity with no primary page generated an NPE even though all step pages were correctly specified. This was caused by the out-of-the-box referring to the nonexistent primary page in a context where it was not necessary. While there was a workaround of specifying a primary page for the agent activity, a change has been made to set and retrieve messages from pyPDFAttachWorkPage instead of a primary page in this situation.
SR-A23106 · Issue 251959
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-A43745 · Issue 249270
Copied ticket shapes properly visible on Work Management
Resolved in Pega Version 7.2.2
After correcting a problem with the XML generated by ticket shapes related to work states, attempting to use a copied shape with Tickets resulted in a problem locating new entries in the Work Management Tickets landing page. This was an issue with the ticket details being embedded in the shape pages while the rule references that were created for the tickets in pyModifiers were not updated to match, and has been resolved by adding rule references for the tickets embedded inside the shapes.
SR-A77119 · Issue 255564
Fixed attaching files to pre-existing inflight cases after upgrade
Resolved in Pega Version 7.2.2
After upgrade, loading pre-existing inflight cases and attaching a file generated the error "Trying to save an invalid page: Trying to save an invalid page: page is not valid". This was caused by a missing check for LinkPage.pyMemo in cases where LinkPage.pyCategory is not set, and has been fixed by setting pyMemo from LinkPage.pyMemo.
SR-A23504 · Issue 251757
Value corrections made to "Timeliness by resolving unit" SLA functions
Resolved in Pega Version 7.2.2
After upgrade, reports which relied on the out-of-the-box "Timeliness by resolving unit" function were failing. This was an issue with the Work-Resolve application, which was not correctly carrying values for the three SLA columns "Within Goal", "Past Goal", and "Past Deadline", which has now been fixed.
SR-A86465 · Issue 257770
Updated partial search from the Case Manager portal to return consistent results
Resolved in Pega Version 7.2.2
After upgrade, the search functionality was not working as expected. Launching the Case manager portal to search and then open a case worked, but then searching for another case and opening it resulted in the contents of the first search being displayed again. This was traced to inconsistent results when partial search was used from case manager portal,, and has been resolved by showing all the results (top 20) every time partial search is used from case manager portal, irrespective of the ranking ES provides to the search results (i.e., even if the work id is present in the top 20 or not).