INC-177263 · Issue 655830
isFutureDate edit validation fires correctly
Resolved in Pega Version 8.6.1
The date value entered was not getting converted to the user-specific time zone and resulted in an incorrect value for validation when using isFutureDate. This has been resolved by adding an update which will convert the date value to the specific time zone before comparing it with the current date.
INC-177852 · Issue 658654
Added UI handling for error message on Delegated data table
Resolved in Pega Version 8.6.1
It was not possible to navigate in the UI if there were error messages shown on properties in a delegated data table until that column was filled with a value. To resolve this, an update has been made to prevent reload or save on scroll.
INC-178639 · Issue 658056
Improved accessibility for Autocomplete Role
Resolved in Pega Version 8.6.1
Accessibility issues with Autocomplete Role have been resolved by adding role = "combobox" for autocomplete in template mode.
INC-179378 · Issue 661174
Repeating Layout renders correctly after update
Resolved in Pega Version 8.6.1
Repeating dynamic layout was not working properly after update. This was caused by a missing active class, and was traced to changes made in the pzpega_ui_layoutgroup function where reload happens on close of a modal dialog. To resolve this, a safe check has been added to setInActiveLayout in layoutgroup.js.
INC-179622 · Issue 659155
Flow action list available in navigation menu
Resolved in Pega Version 8.6.1
After update, only one flow action which had highest likelihood was visible when an assignment in a flow had multiple flow actions. Alternatives were not visible in the Action menu. This was an unintended side effect of work done to simplify the Actions menu which did not consider the usecase of an alternate flow action being configured, and has been resolved by restoring the flow action list to the navigation menu in pyWorkCommonActions.
INC-179883 · Issue 661615
Pega reference tags persist
Resolved in Pega Version 8.6.1
Cross-site scripting protections have been updated to allow Pega reference tags.
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.
SR-D26589 · Issue 496719
pxParseExcelFile activity will now parse multiple sheets
Resolved in Pega Version 8.3.1
When trying to use the activity pxParseExcelFile on an Excel file containing three sheets where each sheet had a different pagelist, the properties mentioned in sheet 1 were populated on upload but the remaining sheets only showed the error message "Could not get clipboard property for reference Work Queues.". This was caused by an error in Row index handling for the additional sheets, and has been resolved by updating the logic to populate the data in the clipboard. Additional issues for this issue in 8.4 to fix issues like formulae not getting evaluated and $ not parsed: 501592, 501383