SR-D95419 · Issue 563397
Updated Multiselect control behavior for incorrect value
Resolved in Pega Version 8.4.2
After upgrade, a difference in behavior was seen. Previously, when a user entered an incorrect value in a multi-select where the required field was checked and then clicked anywhere outside of the field, the value would erase before displaying the message "Value cannot be blank”. After upgrade, the value was not erased when the message was displayed, causing confusion. This has been resolved by adding logic which will determine the correct message to display, such as "Value cannot be blank" or "Please select a Valid Value".
SR-D96224 · Issue 556782
Validation error messages correctly cleared
Resolved in Pega Version 8.4.2
The error message on a checkbox field, radio button, or text area with a on-change post value was persisting even after the correct input was provided. This occurred when the area had a caption, and was due to an additional wrapper span that caused the error div to be the span's sibling instead of the span itself. In the post value success, the system checked whether the error div was present in the area's parent, i.e. span, and when no div was returned the error msg was not removed. It was possible to add an action 'Refresh this section' on change as a workaround, but this has been corrected by updating the system so that Instead of checking the error div in src.parentNode, it will access the correct parentNode using 'closest' and check for the error div.
SR-D96754 · Issue 560220
Column filtering corrected for Microsoft Internet Explorer 11 AJAX containers
Resolved in Pega Version 8.4.2
Column Filtering was failing when used in tables inside an AJAX container in Microsoft Internet Explorer 11. This was due to the filter popover close method changing the visibility of the popover and triggering a context switch, and has been resolved by setting the flag pega.ctxmgr.skipContextSwitching to true before changing the visibility.
SR-D96909 · Issue 558141
Removed extra scroll bar in Multiselect
Resolved in Pega Version 8.4.2
An extra scroll bar was appearing when opening the multi-select control case manager portal using the "Results displayed Maximum 500 results to display" setting. This was a result of recent updates to the popover scroll and height that caused on overflow condition. To resolve this, the logic for Multiselect has been updated.
SR-D99025 · Issue 558222
Refresh-Other section correctly shifts focus on tab out
Resolved in Pega Version 8.4.2
After upgrade, a difference was seen in the behavior of the Refresh-Other section action functions. Previously, focus was shifted to the next field when tabbing out, which is the desired behavior. Investigation showed that this was a result of modifications made to resolve other focus issues, and the previous behavior has been returned by updating the conditions used to call the "focusNextElement" method to include a check whether the reloadElement is stale, and to get the focusElement from DOM based on name (pega.util.Dom.getElementsByName(focusElemName)) if needed.
SR-D20439 · Issue 496405
Hotfix hashmap cleanup improved
Resolved in Pega Version 8.1.7
A DL installation failed with an out-of-memory error. It was observed that many CacheEntry(VersionedJdbcJarRwader.java) hashmaps were being created to store the details for each hotfix but that were then never cleared. This has been resolved by adding the finally block in CodeImportProcessImpl.java class to call the shutdown method for proper cleanup. In addition, the default command line utility (prpcUtils) has been updated to use JVM settings of Xmx 4GB and capture a heap dump if an out-of-memory error is encountered. The auto-generated prconfig.xml has also been updated to leverage its minimal startup setting which will avoid loading the conclusion cache into memory.
SR-D45101 · Issue 512530
Added support for Helper Text Question Mark with visibility condition
Resolved in Pega Version 8.1.7
The Helper Text Question Mark was not displaying if the control was configured with "Help icon with overlay on hover" combined with a visibility condition. This was a missed use case, and the expression visibility support for controls.changes have now been added in the pzpega_ui_DLCellTemplate.js file.
SR-D17825 · Issue 494700
PreSaveAs updated to set the correct ruleset value when saved into a different ruleset
Resolved in Pega Version 8.3.1
When using a BIX Extract rule already configured with properties and filter criteria, attempting to update the filter criteria system resulted in an "invalid property error" and inability to save the updated rule. This was traced to the extract rule being created from another extract rule with 'save as', resulting in the new extract existing in a different ruleset. Because the pxBixReportPage.pyRuleset had the value of the original ruleset instead of rule set in which it had been saved, the system was attempting to find the filter properties in the original ruleset. To resolve this, the Presaveas activity in rule-admin-extract has been modified to check and set the correct value when both the rulesets are not equal.
SR-D22415 · Issue 493439
Enhancement added to expose BrowserAttachmentTypeTable
Resolved in Pega Version 8.3.1
By default, the inline view of PDF files appears with the thread name visible. An enhancement has been made to expose pzBrowserAttachmentTypeTable as a py rule: when the DT is overridden such that return is false for PDF, the inline view is not displayed but instead the PDF is downloaded when clicked.
SR-D23723 · Issue 503087
pxGenerateExcelFile updated for handling blank dates
Resolved in Pega Version 8.3.1
When using a custom template for exporting to Excel, blank DateTime property column values defaulted to the current date. To resolve this, the pxGenerateExcelFile activity has been updated to ensure that an empty date will be exported as blank and that given dates will appear in the correct datetime format.