INC-159506 · Issue 635902
Corrected column alignment for Report Definition exported to PDF
Resolved in Pega Version 8.6
Aggregated columns such as count were not properly aligned in the PDF when a report definition was exported. This has been resolved by adding right justification styles in pyReport_ExportToPdfStyles.css. With this change, the PDF will look similar to the report definition displayed in the UI.
INC-160102 · Issue 627686
Updated resource file paths for mobile images
Resolved in Pega Version 8.6
After upgrade, a resource missing error was shown on the mobile UI when accessing a section in an offline mobile app. This was traced to the CSS file having an incorrect path to the 'requiredstar' gif file and has been resolved by updating pzbase-form-level-elements to use webwb instead of an images path.
INC-160130 · Issue 630961
MultiSelect control corrected for Google Chrome on Tablets
Resolved in Pega Version 8.6
It was not possible to expand the multiSelect control dropdown in Google Chrome on tablets. The search worked if text was typed into it. This was due to the method isMobilePhone returning true for both mobile and tablet, causing the system thought it was mobile and stopped the normal behavior. This has been rsolved by adding a regular expression check in the pzpega_control_multiselect isMobilehone() method to check if it a tablet. The isMobilePhone() method will return false if the device is tablet so the dropdown appears as expected.
INC-160497 · Issue 627714
Able to add missing headers from App Studio
Resolved in Pega Version 8.6
A missing header in pyActionArea and pyActionAreaheader could not be added from App Studio. This was due to the sections not being built using design templates, and has been resolved by updating the section to be editable in runtime.
INC-160500 · Issue 627267
Cosmos App Studio icons have helper text
Resolved in Pega Version 8.6
Enhancements have been made for accessibility by adding Helper text to icons in the Cosmos theme for App Studio.
INC-160624 · Issue 633085
Text data type correctly passed for personalized tables
Resolved in Pega Version 8.6
When using a table with personalization enabled that was sourced through a data page that had paging enabled, applying filtering through the personalized options on a Country field sourced through a declarative index was not showing any results in the table. This issue was due to the data type passed for identifier as "text" instead of "Text", and has been corrected.
INC-160843 · Issue 631728
Performance improvements for multiple visibility expressions in repeating structures
Resolved in Pega Version 8.6
After upgrade, performance degradation was seen and PEGA0069 alerts appeared frequently. Investigation traced this to performance issues with the expression evaluation on the client when there were multiple visibility expressions in the repeating structures. To resolve this, updates have been made to the pzpega_ui_ExpressionEvaluator.js to reduce the number of calls to _getCtxElement( ) in side loops.
INC-161126 · Issue 631090
Edit validation message appears on Cosmos UI
Resolved in Pega Version 8.6
When using a flow action in Cosmos, validation messages did not appear on the UI as expected but an error would be thrown while clicking on the submit. This was traced to an unneeded visibility condition present on the section "pyCaseActionArea" when "pyCaseErrorSection" was included, and has been resolved
INC-161409 · Issue 632726
Added handling for checkbox group to use form tag when field tag is not available
Resolved in Pega Version 8.6
After configuring the Checkbox group component from the UI gallery in one of the sections in an application built on Theme-Cosmos, the configuration worked as expected when creating a new case type, but opening this WorkObject from the Associated cases section on the child case caused behavior issues including being able to select select multiple options instead of a single radio button. Investigation showed this happened when navigating through the work flow under the Perform Harness, but worked as expected when navigating through the Review Harness. This has been resolved by modifying the selectors to target form tag if the fieldset tag is not available.
INC-161430 · Issue 627720
Accessibility Component/Widget role added to pyCaseErrorSection
Resolved in Pega Version 8.6
Page level errors were not accessible due to the error section being wrapped inside a dynamic layout whose contents were not readable. This has been resolved by updating dynamic layouts to use the correct accessibility roles.