INC-177323 · Issue 672422
Search string wildcard use documentation updated
Resolved in Pega Version 8.6.3
The support article for the search API has been updated to clarify the ability to use the wildcard character "*" by manually adding it to the prefix of each term in the search string.
INC-190130 · Issue 678542
Help information updated for using Elastic Search with Report Definition
Resolved in Pega Version 8.6.3
The support article "Configuring a report definition to run against an Elasticsearch index" has been updated to clarify that the search can pass multiple values with a space in pySearchString as it does OR operation on all the fields, and that filters in the report definition will be used when executing the report directly or when calling the report in the pxRetrieveSearchData activity.
INC-164775 · Issue 681240
Web page generation security updated
Resolved in Pega Version 8.6.3
Cross-site scripting protections have been enhanced around web page generation.
INC-167704 · Issue 671629
Email timing updated to ensure content captured
Resolved in Pega Version 8.6.3
Outbound email replies constructed using a pyReply section were intermittently blank if the 'Send' button was clicked immediately after adding text. This was traced to the blur not happening immediately on click of the submit button, and has been resolved by introducing window.blurDelay to ensure the data is captured. The delay time is configurable, and by default is set to 200ms.
INC-167871 · Issue 666296
Desktop browser java render error corrected
Resolved in Pega Version 8.6.3
Attempting to open Clipboard, schedule a report, or perform any activity which generated in a pop-up resulted in a blank screen and browser errors indicating "Uncaught TypeError: (…) is not a function 2. Uncaught TypeError: cannot set property '...' of undefined". This has been resolved by adding a semicolon to the last line of pzpega_desktop_automation_support_js.
INC-176113 · Issue 661469
Duplicate messages removed from hover over smart info
Resolved in Pega Version 8.6.3
If a particular mandatory field was not selected and saved, scrolling over any help text bubble in that screen caused the error messages to pop up multiple times. This was an issue with the recreation of error tables on hover over smart info and has been corrected.
INC-178417 · Issue 670112
Flag reset added for grid with 'Expand When'
Resolved in Pega Version 8.6.3
A grid using an 'Expand When' condition worked as expected when the condition was true, but once expanded the grid did not collapse if the expand condition was changed to false even if a section/harness refresh was performed. This has been resolved by adding an update which will reset the flag when the result of 'Expand When' is false.
INC-178831 · Issue 680985
Ensured correct context for multi-select
Resolved in Pega Version 8.6.3
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-180108 · Issue 667351
Desktop browser java render error corrected
Resolved in Pega Version 8.6.3
Attempting to open Clipboard, schedule a report, or perform any activity which generated in a pop-up resulted in a blank screen and browser errors indicating "Uncaught TypeError: (…) is not a function 2. Uncaught TypeError: cannot set property '...' of undefined". This has been resolved by adding a semicolon to the last line of pzpega_desktop_automation_support_js.
INC-180322 · Issue 684230
Cosmos collapsible summary panel works with hidden tabs
Resolved in Pega Version 8.6.3
The collapsible summary panel in Cosmos was not working correctly in combination with hidden tabs. This was due to the active tab index being created from the "data-lg-child-id" value which has a constant value for each tab and did not account for some tabs being hidden. To resolve this, the process for finding the "active" tab index is now based on the actual index instead of on the "data-lg-child-id" attribute.