SR-A4227 · Issue 209904
Fixed History-Add API error
Resolved in Pega Version 7.1.9
Within a For loop calling History-Add to add Audit information resulted in the error: "Class not defined in dictionary: History-Code-Pega-List. Details: Invalid value for aClassname passed to .createPage" . This was caused by an incomplete implementation of the function; when History-Add method is called in the method generation for an embedded page, context is switched to the Top Level Page, but when the Top Level Page is Code-Pega-List the current page context is used. This context was not correctly reflected in the History-Add function, and has been fixed.
SR-A4261 · Issue 211712
XSS security updated for LoadPulseImage
Resolved in Pega Version 7.1.9
XSS vulnerability handling has been added to the pzLoadPulseImage control.
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-A4056 · Issue 211550
Corrected validation error for Extract rule field length
Resolved in Pega Version 7.1.9
A validation error noting that the field length of the table was limited to 30 characters was occurring when trying to check in an Extract rule even if the field value had been shortened. While checking in the extract rule, a block of code in the Rule-Utility-Function validateTreeProperties was recomputing the pagelist's table name instead of using the one provided by the user. The Rule-Utility-Function validateTreeProperties function has been modified to fix the issue.
SR-A5412 · Issue 219159
Error marking fixed for TreeNavigation7 screen flow
Resolved in Pega Version 7.3.1
When using the TreeNavigation7 harness in the screen flow to call the validation from the post action, any property error in any of the flow-actions caused only the first flowaction to be marked as having an error while the rest were marked as successful. This has been fixed.
SR-B64971 · Issue 315219
Added alt text attribute to paperclip icon for accessibility
Resolved in Pega Version 7.3.1
A paperclip icon in the pzMultiDragDropControlStandard rule did not have alternative text, impacting its accessibility. An alt="" attribute has been added to the image tag to correct this.