INC-144778 · Issue 619616
Performance improvements for Ajax tab switching
Resolved in Pega Version 8.6
When using a 360-view of members in a portal implemented with an Ajax container that showed information in multiple tabs, tab switching was taking a lot of time even though the data was already in the memory. Updates have been made to improve performance.
INC-144851 · Issue 604480
Date Time picker works with locale es_US
Resolved in Pega Version 8.6
When an Operator had the locale es_US (Spanish) set on the Profile, the Date Picker on the application was throwing validation errors when a date or time was chosen from the out-of-the-box Date Time Control. Investigation showed the date-time format for locale es_US was not supported, and the getDateTimeFormat API has been updated to support this format (11:00 a.m.).
INC-144888 · Issue 603617
Custom Rich Text Editor plugin support updated
Resolved in Pega Version 8.6
At runtime, two Rich Text Editors were used in the same harness under two different sections, one regular and one hidden till clicked. A custom plugin was implemented for Rich Text Editor at the harness level. After upgrade, the custom plugin was not getting displayed in the hidden Rich Text Editor. Investigation showed that if plugins were added to pega.ctx.customRTEPlugins, then the plugin manager discarded plugins from pega.u.d.customRTEPlugins. To resolve this, the Rich Text Editor plugin manager has been modified to merge the plugins from pega.ctx.customRTEPlugins and pega.u.d.customRTEPlugins.
INC-144924 · Issue 618734
Security alerts resolved for ActiveDocumentType
Resolved in Pega Version 8.6
SECU0001alerts indicating "HTTP Request Corrupted" were seen in the log files. These were related to the pyActiveDocumentType properties which are included in an Ajax request, and were caused by a condition where a new thread request results in an unexpected property check that encounters a clipboard which doesn't have any pages created for that thread. To resolve this, the pyActiveDocumentType properties have been added to an allow list to handle the unexpected properties check.
INC-144924 · Issue 614768
System improvements related to ActiveDocumentType
Resolved in Pega Version 8.6
Alerts were seen for unexpected properties in HTTP requests related to pyActiveDocumentType, and system slowness was seen when the request was trying to update the properties. This was traced to a condition where a page remove cleared property registration, and has been resolved.
INC-144951 · Issue 601976
Updated specificity for custom-format inputs
Resolved in Pega Version 8.6
After upgrade, custom formatting for a link control was not working in the skin or during runtime. This was an issue where identical format names used for links and text components caused selectors from the text area to take precedence over link styles, and has been resolved by updating styles to increase specificity for inputs instead of links.
INC-145119 · Issue 601711
Client side validation works with Reference page property
Resolved in Pega Version 8.6
A reference page property in a 'when' rule was not evaluating properly for checking a Date field when client side validation or Client side template UI was checked on the Harness level. This was traced to pyRequired being boolean: the boolean being compared to a string false value yielded a wrong comparison, leading to the wrong validation type required. To resolve this, the system will use the === comparator to compare boolean false in datetime to remove the required validator.
INC-145225 · Issue 602947
Resolved error in personalized table
Resolved in Pega Version 8.6
After creating a section and adding a table, checking the personalization option in the table properties and clicking refresh caused the UI to become unresponsive. This was traced to a missing check in the template that was needed before accessing the busy indicator, and has been resolved.
INC-145263 · Issue 600035
Query logic modified for Anypicker
Resolved in Pega Version 8.6
A search for results in the Anypicker control for the first time showed the results, but if the results were deleted and the search run again without focusing out from that field, no results were found for the second search. This has been resolved by using slice than splice in the query to avoid mutating the original array source.
INC-145467 · Issue 617214
isDCSPA flag added to ensure correct harness after reload
Resolved in Pega Version 8.6
When moving from a Process Flow to a Screenflow configured with tabbedscreenflow7, the first reload caused a switch to a Perform Harness that resulted in the error "Unable to open an instance using the given inputs", and footer buttons disappeared until multiple refreshes were done. This was an issue specific to the environment configuration at the site, but to avoid future issues a code update has been made that will add the isDCSPA flag if the value is not present in the parameter page.