SR-C973 · Issue 349954
Move report shortcut shows consistent categories
Resolved in Pega Version 8.1
When opening a Report in the Case Manager Portal, the Analyze Performance category is first in the out of the box implementation. However, when attempting to move one report from a different category, the Analyze Performance category was not shown in drop-down This was caused by different field values being used to display the category label in the browser and category dropdown, which led to them being localized differently in the display on the right ( "Analyze Performance") and the dropdown ("Performance analysis"). To correct this, the field values have been updated to make them consistently localized.
SR-C9791 · Issue 350823
Code added to ensure unique IDs for control elements
Resolved in Pega Version 8.1
In order to improve accessibility, code has been added to ensure unique IDs are generated for Radio buttons, checkboxes, and other controls. This also resolves an issue where the duplicate labels caused a click to fire on an unexpected harness element.
SR-C9804 · Issue 350937
ResultCount methods updated to handle null results
Resolved in Pega Version 8.1
Autocomplete controls were not working via mobile app. This was due to the Autocomplete control not rendering a list supplied by a data page, and was traced to the results of the datapage var resultCount = res.responseText.get("pxResultCount");being returned as null. In order to ensure the correct results, an alternate way of getting the pxResultCount has been added.
SR-C9824 · Issue 355932
Behavior change for error handling when using "Call superclass data transform"
Resolved in Pega Version 8.1
Previously, when "Call superclass data transform" was enabled for data transfers, the initial data transform would continue working even if the subsequent transforms it called failed. As an example, given data transform A, which called another data transform B, which called another data transform C, and data transform A performed some actions after calling data transform B; If an error occurred while processing data transform C, data transform C ended processing, data transform B also ended processing, but data transform A continued working. This was confusing behavior. To create a more consistent environment, whether or not “call superclass data transform” is used, when any of the chained data transforms fail the entire process will exit. The documentation has also been updated to indicate this new behavior.
SR-C9887 · Issue 354825
Reports list properly updated when switching applications
Resolved in Pega Version 8.1
When switching applications, some of the report browser was displaying information from the first application. This was due to incomplete clearing of the data, and has been fixed by calling pzRBSetFilters in Data-Report-Browser!pzRBForceDataPageRefresh to reset the report browser when it is opened.
SR-D79178 · Issue 543310
SameSite cookie setting added for Mashup support in Google Chrome v80+
Resolved in Pega Version 8.3.3
The Google Chrome browser version 80 and above now treats SameSite with a blank value as "Lax" by default, causing mashup scenarios to break. In order to compensate for this change, support has been added for setting SameSite=None in Cookie Settings; this value automatically includes the “secure” cookie flag, which enforces HTTPS for the Pega server and mashup. For mashups to work, SameSite should be set as None. Create a Dynamic system setting in the Pega-Engine RuleSet with the name “security/csrf/samesitecookieattributevalue” and the value "None" and restart the server. (The SameSite value "None" works only in secure HTTPS connections.)Note: The SameSite cookie may be set to None/Lax/Strict, based on the requirement. For cookie requirements other than mashup, it should be set as either Strict or Lax, depending upon your application.
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.