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-127385 · Issue 235813
Fixed user authorization filtering error in extracts
Resolved in Pega Version 7.2.1
Extraction was failing sporadically due to the filter condition not being picked up by all the extract rules when running BIX. This was due to an error in authorizing the requestor with username/password causing differences in datetime formats, and has been fixed.
SR-129197 · Issue 197995
Fixed Silverlight "Create Word Document" error
Resolved in Pega Version 7.2.1
A Silverlight issue appeared while using "Create word document". The older flow action CreateMergedWordDoc was running on the Current Page Context and had a reference to the Word Template used in the PegaSample application. To resolve this, the new Flow Action 'pyCreateWordDocumentCMGallery' has been created. This runs on the pyFlowActionTestPage page and uses the new Word Template pyCMTemplate which has limited set of related properties.
SR-A10345 · Issue 221893
Removed unexpected validation from Page-Change-Class
Resolved in Pega Version 7.2.1
Validation errors appeared on the review screen when tracer was enabled if there was non-conforming data in the non-expanded elements. PDN help for the activity method Page-Change-Class specifies that the method does not validate property values, but the generated java ends up calling DictionaryImpl.validate() and validates the step page without expanding it. Any invalid data in the non-expanded properties would be ignored. However, activating the tracer expands the page and as a result Page-Change-Class attempts to validate all the properties in the page, resulting in errors appearing when appropriate. In order to handle this scenario, validation has been removed from Page-Change-Class method in order to bring the results into line with the help documentation, and if validation is needed it must be added explicitly.
SR-A10491 · Issue 234174
Locking corrected for WebLogic BMT transactions
Resolved in Pega Version 7.2.1
Incomplete locking for WebLogic BMT transactions caused work items in the queue to be processed by duplicate agents even though the item was already processed. This has been fixed.