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-D92352 · Issue 553615
Completed onChange will reset FileInput value to null
Resolved in Pega Version 8.3.3
When attaching a file using the "Select File" button, it was not possible to attach the same file after deleting it. Re-attaching the file worked as expected when using Drag and Drop. Investigation showed that the onchange event occurred only when the value of an element was changed, so in this case trying to attach the same file did not change the value of the element and did not fire the onchange. To resolve this, the value of FileInput in pzMultiFilePath Control will be set to null at the end of the onChange event so that an onChange event will be triggered next time even if the same file is added.
SR-D73536 · Issue 538401
FetchApplicationLogo modified to Filter by rule resolution
Resolved in Pega Version 8.3.3
It was observed that the Report Definition rule "pzFetchApplicationLogo", referenced by Activity rule "pzLoadApplicationLogo", always returned the older version of the Binary File "webwb • pyapp-logo • svg" because it had been set to retrieve a maximum of one record and in this case the results were sorted in an order where the oldest record was at the top. As the Report Definition did not indicate any sorting, most DBMS were returning the results in no particular or predictable order. To resolve this, "Filter by rule resolution" has now been enabled for Report Definition pzFetchApplicationLogo.
SR-D84480 · Issue 546187
FilterHistory decision tree used for audit log status
Resolved in Pega Version 8.3.3
Attempting to use the “FilterHistory” decision tree in the work class to return value “false” for “pyCloseOpenAssignmentsOnResolution” to hide the “pyCloseOpenAssignmentsOnResolution” field value (“Unfinished assignments were cleaned up by the system after the completion.. ”) from history was not working as expected, and still returned the audit message. This was due to the system setting this AuditNote parameter within the “pzProcessResolutionStage” activity, where Param.UpdateHistory was set to true always. In order to support more flexibility, the Param.updateHistory paramter in step3 of the pzProcessResolutionStage activity will be set based on the FilterHistory decision tree. When set to false in FilterHistory decision tree, pyCloseOpenAssignmentsOnResolution will be set as false and audit will not be logged.
SR-D90528 · Issue 550665
Localization added to File upload alerts
Resolved in Pega Version 8.3.3
When uploading files as part of adding attachments, error and warning messages were displayed as alerts in English despite using localization. This was traced to the pzMultiDragDropControlStandard control rule having the HTML alert messages hard coded instead of using field values which could be localized. To resolve this, field values have been created for the messages related to DragDropMaxSize, FileNotExistMessage, FileUploadSupportMessage, and UnableToLoadFileMessage.
SR-D84754 · Issue 548163
Resolved erroneous problem assignment error
Resolved in Pega Version 8.3.3
If a user processed a work item while the SLA agent was also attempting to process it, it sometimes resulted in an assignment with the error: "Error: Flow Not At Task." In this scenario, an error message was displayed stating that "Assignment already completed" even though the assignment was not yet finished, causing confusion. Investigation showed that in cases where the success indicator was -28, the assignment was marked as problem assignment even though it was processed. To resolve this, the system has been updated to skip marking the assignment as a problem when the success indicator is -28.