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.
INC-173068 · Issue 654064
HTML tags escaped in Audit History field values
Resolved in Pega Version 8.4.6
The case narrative section was showing case statuses with encoded special characters such as % or ( ), resulting in entries such as "Status changed to Complete &# 40;approved& #41; !@#$ %^& amp;*&# 40;&# 41;_&# 43;.". This has been resolved by updating the PyMemo field from type Text Input to DisplayAsLiteral for case narrative, which matches the setting for case history.
INC-175882 · Issue 658642
Updated bulk action audit history logic and security
Resolved in Pega Version 8.4.6
After update, using the standard bulk action feature did not record an audit history entry for the SLA action on a case. This was traced to changes made around authorization for opening worklists when using pzBulkProcessItem that limited the audit history to reassign, transfer or transfer assignment, and has been resolved by updating the login the Work-pzBulkProcessItem activity. In addition, the Require authentication to run checkbox has been enabled on the Security tab of the activity, and the Allow invocation from browser checkbox has been disabled.
INC-177183 · Issue 660537
Refresh assignment checks updated
Resolved in Pega Version 8.4.6
Additional privilege checks have been added to refresh assignment.
INC-178650 · Issue 673550
Cross-site scripting protections updated
Resolved in Pega Version 8.4.6
Cross-site scripting protections have been updated around the DisplayAttachment function.
INC-183947 · Issue 673735
Query split added to handle Oracle expressions limit
Resolved in Pega Version 8.4.6
The PXCHECKFLOWDEPENDENCIES activity was throwing the Oracle error message "ORA-01795: maximum number of expressions in a list is 1000" when a case had a very large number of sub-cases, causing a failure in trying to submit additional child cases which sent them into the broken process. This has been resolved by updating the pxCheckFlowDependencies rule to break down the query parameter into batches of 999 so they can be handled by Oracle.