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-A8538 · Issue 222591
RepeatIndex generation improved
Resolved in Pega Version 8.1
Controls in a triple layout included in a row repeat did not have matching unique IDs and label for attributes. This was due to incomplete generation of the repeatindex for the ID, and has been fixed.
SR-B71423 · Issue 319981
Localization added to pyAccountSettings field labels
Resolved in Pega Version 7.4
Field label localization for the pyAccountSettings section rule has been added to the Pega-IntegrationArchitect ruleset.
SR-B54277 · Issue 336406
Trimmed unneeded properties from doUIAction call
Resolved in Pega Version 7.4
Null pointer exceptions were generated when relaunching the manager portal after saving a work-object, and the error "Request-URL Too Large. The requested URL's length exceeds the capacity limit for this server" appeared. This was traced to the number of properties included in the doUIAction call; unnecessary parameters have been removed to resolve this issue.
SR-B66164 · Issue 325166
Handling improved for pzActiondropdown's Action label value
Resolved in Pega Version 7.4
When an alternate flow action was picked from LocalAction's list and then submitted, the presence of any page-set messages would cause the submission to fail and the flow remained on the same flow action. This was an issue with handling the changed value of the FlowAction label, and the pzActionDropdown control has been modified to get the correct pyDefaultActionIndex parameter value.
SR-B70422 · Issue 326897
Removed unnecessary add/delete history entries related to empty page properties
Resolved in Pega Version 7.4
The field level auditing configured for page group or list property types was creating multiple add and delete entries in the history of the case even though the pagelist/pagegroup had not been modified. This was traced to method used by the pagelist change audit process to compare current pages to the previous value of the pagelist pages: during pagetostring conversion, sometimes the empty properties in page are present in the String and sometimes they are not, resulting in a difference that generated the non-essential audit entries. This has been fixed by changing the getProperty references in getPageAsString function to use getIfPresent instead. Null checks have also been added.