INC-142589 · Issue 595489
Corrected tooltip evaluation for multiselect
Resolved in Pega Version 8.4.3
After adding help text for a multiselect help icon with overlay on hover field, the value was not being sourced. Changing to a different type of help text or control type worked as expected. This was due to an error in case sensitivity, using pyToolTip when it should have been pyTooltip, and has been corrected.
INC-142714 · Issue 596554
Recent Cases from different applications available to open
Resolved in Pega Version 8.4.3
An enhancement has been added which will allow opening other application assignments in the Recent Cases section of the current application when the user has access to multiple applications.
INC-143005 · Issue 596954
Fluid Overlay displays as expected in Firefox
Resolved in Pega Version 8.4.3
After upgrade, using the Overlay format "Fluid" to perform the screening matches task in CLM using Firefox had an overlay that covered the entire screen but was missing the scrollbar to manage the content. This has been resolved by adding changes to support dynamic content (with scrollbar) for center overlay.
INC-153631 · Issue 613851
Table selector updated to handle complex autocomplete dropdowns
Resolved in Pega Version 8.7.1
Whenever an autocomplete and a table were in different sections, only the first 40 results were visible in the dropdown and the other spaces were shown as blank. The issue did not occur if the table and autocomplete were in same section. This was traced to a specific configuration where Section A had an autocomplete inside the dropdown list and autocomplete was enabled to show the results in a table (presentation tab) and Section B, which contained a grid, was included in Section A in the same autocomplete dropdown list. This has been resolved by updating the table selector in ui_grid so it uses the correct dom elements.
INC-172944 · Issue 662829
Skin rule circumstancing article added
Resolved in Pega Version 8.7.1
An article on skin circumstancing best practices has been added to https://collaborate.pega.com to aid in working with this functionality.
INC-176462 · Issue 657411
Dashoard widget drilldown section adjusts dynamically
Resolved in Pega Version 8.7.1
While trying to expand the drilldown columns, text was overlapping due to the grid not adjusting the large size of data dynamically. This was traced to an unnecessary CSS rule being applied to set max-height which broke the styling. This has been resolved by removing the height limitation on detail cells.
INC-178831 · Issue 697057
Ensured correct context for multi-select
Resolved in Pega Version 8.7.1
When using multi-select controls, there was an intermittent issue with selecting values using a mouse click. Using the tab key worked as expected. This was traced to the focus being event triggered multiple times so pega.ctx.dom returned undefined values in the second call.This has been resolved by focusing the target element before creation of capsule to ensure the context remains the same.
INC-182287 · Issue 670743
Decimal places showing correctly after update
Resolved in Pega Version 8.7.1
After selecting Decimal places in the Property Panel in the section for a particular property, the decimal places were not added on tab-out at runtime. Decimal places were correctly applied if no property was specified. Investigation showed that an explicit post value call was initiated to apply the read-only formatting, but that call was suppressed by other conditions related to updating the Pega version. To resolve this, an unneeded data-auto-formatting conditional check has been removed.
INC-182803 · Issue 679724
SearchKeyword assed to HandleInput allow list
Resolved in Pega Version 8.7.1
After creating a section and placing a template grid with a button to refresh the section on click, clicking the button generated a SECU0001 alert. This was traced to gridMetadata_(uniqueID).pySearchKeyword not being registered when the property is part of a form data post request, and this has been resolved by adding pySearchKeyword to the allow list in HandleInput.java.
INC-182874 · Issue 675311
Update Language Pack for correct direct web access link localization
Resolved in Pega Version 8.7.1
When a direct web access (DWA) link was generated for an external user to perform an action on an external assignment, the shared link was corrupted when used with localization on the receiving system. This was due to the JSP fragment in the correspondence not being properly translated during localization. To resolve this, please access the most recent Language Pack available from https://community.pega.com/marketplace/language-packs/pega-platform