INC-150407 · Issue 605840
Validation error messages correctly cleared in nested markup
Resolved in Pega Version 8.5.2
A UI Freeze issue was seen whenever mandatory input was missed and the form was submitted. Continuing was possible after browser refresh, but a new Next>> button appeared. This was an unintended side effect of work done to correctly clear validation messages when areas had captions, and has been resolved by modifying that work so it performs as expected on nested markup.
INC-150472 · Issue 607392
Sorting works after selecting a view on GRID
Resolved in Pega Version 8.5.2
After configuring an optimized table with personalized view, saving a view and toggling to the new view, the sorting on the grid did not work anymore. Returning to the default view did not fix the problem, but sorting was reenabled after a browser refresh. This was traced to duplicate removeinstance calls of the grid which deleted the click event listeners for sort, and has been resolved.
INC-150189 · Issue 608911
Handling added for new doc.write with Google Chrome 85
Resolved in Pega Version 8.5.2
Document.write was not working as expected on Google Chrome 85 due to the DOM elements not being updated. This has been resolved by updating the code to do doc.write by checking the if the document body has no child nodes in a time out.
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.
SR-A10532 · Issue 226036
iOS8 Mobile Autocomplete design reworked for better display
Resolved in Pega Version 7.2.1
When new auto-complete was used in an iPhone/iPad device running on iOS8 in landscape mode, the display moved to the top and the auto complete field was not visible. This was an issue with the window handling, and the Mobile Autocomplete design has changed in 7.2. to resolve this and other related landscape display issues.
SR-A10653 · Issue 236942
Fixed NPE in the Connector and Metadata wizard
Resolved in Pega Version 7.2.1
The Connector and Metadata wizard was throwing a NPE in logs due to the inability to resolve a header schema definition during import. To fix this, the system will skip the unresolved header mapping processing and log an error message instead of creating an empty entry.
SR-A10871 · Issue 231166
Extra parameter support added to CreateNewWork
Resolved in Pega Version 7.2.1
Code changes in _navigateGadgetFrame caused issues when calling createNewWork function in a custom control. Support has been added to pass parameters along with flow name to correct this.