INC-178417 · Issue 670114
Flag reset added for grid with 'Expand When'
Resolved in Pega Version 8.7
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.
SR-C23138 · Issue 367878
PRPushServlet response corrected to 400 when disabled
Resolved in Pega Version 8.1
PRPushServlet is used to establish a WebSocket connection with the Pega server. When server-push is disabled, the Push engine won't get initialized and will return an empty response by logging a warning message ("Request arrived for requestor:[%s]. But PushEngine has not started." ). Unexpectedly, this process was returning HTTP status 200 instead of 400. This has been corrected.
SR-C24201 · Issue 373198
Updated logging to stabilize ServiceAPI use
Resolved in Pega Version 8.1
When using “ServiceAPI” for other integrations within the application, setting ServiceAPI to “Fatal” caused the loss of visibility on issues with other components of the application which use ServiceAPI. This was traced to excessive logging for authentication failures from ServiceAPI, and has been resolved by changing error logging to Warn or Debug at various instances.
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.
SR-D39302 · Issue 507981
Report name in tab uses localization
Resolved in Pega Version 8.2.4
After creating a field value with field name as pyCaption to localize the report definition name, the title in the report definition tab was not translated. This was traced to Step 1 of the activity displayReport using an old localization function, and has been resolved by changing the localization of document title to use pyCaption.
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-D26785 · Issue 495892
Corrected error when persisting temporary work object
Resolved in Pega Version 8.2.4
When persisting a temporary work object using the Persist case shape, the internal assignment handle was not updated to include the work object's ID. Subsequent attempts to access the internal assignment (such as the "Edit" button on the Review Harness) resulted in errors. Investigation showed that when a temporary case was persisted, pyInternalAssignmentHandle was not getting recalculated after pzInsKey was updated. To resolve this, the configuration on the edit button has been modified to use .pxFlow(pzInternalCaseFlow).pxAssignmentKey which is what pyInternalAssignmentHandle declare expression was also returning.
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.