INC-133951 · Issue 584148
Try catch added for templated refresh when
Resolved in Pega Version 8.3.5
After configuring a refresh when condition on a dynamic layout triggered by changes on D_worklist.pxResults, a component stack mismatch error was generated if client side UI template is enabled. Without templatization it worked as expected. This has been resolved by adding a try catch block to DynamicLayoutGenerator.java.
INC-175630 · Issue 653863
Application selections only announced when visible
Resolved in Pega Version 8.7
The elements of the application switcher were being announced by the NVDA screen reader even when toggled off, i.e. not visible. The issue was occurring because the focus was remaining at the search bar even after closing the app switcher window, and has been resolved by adding the necessary logic to switch the focus.
SR-C16961 · Issue 357154
BasicLocaleImpl logic updated to use ConcurrentHashMap
Resolved in Pega Version 8.1
To improve performance, the logic for com.pega.pegarules.exec.internal.util.BasicLocaleImpl has been changed to use ConcurrentHashMap instead of HashTable.
SR-C17056 · Issue 356994
Memory use performance improvements for surveys
Resolved in Pega Version 8.1
The inline scripts for question shape have been eliminated and the dynamic generated arguments process has been moved to the global survey namespace. This enables the download of one common script for all question screens to conserve memory usage.
INC-195387 · Issue 681673
HandleResponses updated for use with optimized campaign
Resolved in Pega Version 8.7
After updating from Pega 8.4, responses were not processed in the pxHandleResponses Data flow if the "pyCampaignOptimization" flag was set to true. This was traced to a missed use case for an optimized campaign, and has been resolved by modifying the condition in HandleResponses.
SR-C11041 · Issue 352810
UI retains layout when RTE maximized for editing
Resolved in Pega Version 8.1
After using the 'Maximize' button in a Rich text editor in a section, the screen layout was incorrect after visiting another window and toggling back to the one with the RTE. This was a timing conflict: when the RTE is maximized CSS styles are captured and removed from the Harness, and whenever refresh section fires onChange, RTE is destroyed and recreated. To make sure the UI does not get distorted, pzpega_ui_richtexteditor.js has been modified to resize the RTE before destroy and to set the CSS styles back to the harness.
SR-C15546 · Issue 362398
'Close' button hidden when browser doesn't support it
Resolved in Pega Version 8.1
Attempting to access an external NPS survey assignment a second time generates an Access Denied / Logon Denied window; the resulting window was not closeable by using the 'close' button in Google Chrome and Firefox. This was traced to browser security restrictions imposed by Firefox and Google Chrome that disable Window.close()for URLs launched directly by hitting the URL. To avoid confusion, the DenyExternal HTML rule has been modified to avoid showing the 'close' button for browsers that do not support it in this case.
INC-180184 · Issue 665091
Assistance and diagnostics added for issue with opening imported 'when'
Resolved in Pega Version 8.7
After upgrade, attempting to open rules that were developed on lower environments and then imported resulted in unknown errors. A workaround has been added to skip and log any corrupted property that might be interfering with the rule opening: enable Skip-Corrupt-Property to put this in place. To improve diagnostics, the new logger NBA-WME-DEBUG has been added. If the error continues after using Skip-Corrupt-Property, Skip-Corrupt-Property should be disabled and NBA-WME-DEBUG should be enabled and kept active until the issue occurs again.
SR-121183 · Issue 180073
Clarified complex visible 'when' usage with Expression Builder
Resolved in Pega Version 7.1.8
Execution was failing while using a complex visible 'when' expression with more than one Boolean operator. This is not incorrect behavior; Expression Builder only honors one Boolean operator, but the expression will work if typed directly and "Run on Client" is checked. This caused confusion due to the system not flagging the expression as unsupported in Expression Builder, and this has been fixed. In addition, the code has been updated to properly handle multiple logical operators so that runtime behavior is correct and no error is reported at save time. However, please note the following important information: For auto-generated sections, complex 'when' expressions will be allowed and honored when typed directly , but Expression Builders will still allow only one operator. Also, for non-auto generated sections and JSP directives, the old limitation of 1 operator will still apply.
INC-165992 · Issue 657691
Table Filter save uses correct harness
Resolved in Pega Version 8.7
After creating a new view for table and then relaunching the portal or switching between tabs, the created views were not visible. Investigation showed that the views were saved under the incorrect pycaseworker harness on initial load, causing them to not be visible when returning from the switch and using the correct pyCWPortalContent harness. This has been resolved with the addition of the new parameter innerHarnessName to get the harness name when creating a personalization instance.