SR-D10178 · Issue 423054
Tika library upgraded to v1.20
Resolved in Pega Version 8.1.6
The tika-parsers and tika-core version have been upgraded to version 1.20 .
SR-D20292 · Issue 495147
Race condition handling added to resolve stuck class loader threads
Resolved in Pega Version 8.1.6
A JVM became unresponsive after new JVM traffic was brought in. In reviewing the threaddump, there were hundreds of threads that originated from PRClassLoaderDB.getDefinitionForName or PRClassLoaderDB.getorCreateDefinitionForName found in a "stuck" state waiting on a condition. Investigation showed there was a thread deadlock caused by the system loading class definitions while an external resource was asking for a snapshot of the resources being loaded. This has been resolved by adding handling for the race condition.
SR-D14521 · Issue 486530
Added support for sorting by field value instead of localized value
Resolved in Pega Version 8.1.6
In a datapage-sourced dropdown with 'group by functionality' enabled in ascending order, the values were being sorted according to their localized value and not their field value. This was a difference between templatized and non-templatized handling, and has been resolved by adding the ability to sort the group label by field value in the templatized UI.
SR-D28657 · Issue 500585
Corrected Reference value's description in Table
Resolved in Pega Version 8.1.6
When a user was given 'property for value' as an ID and 'property for display text' like a name, launching the portal showed the display text correctly until 'refresh' was clicked, at which time the current section showed the property value instead of the property text. Investigation showed that the parameter string split inside the parameterised data page used as a dropdown source failed in the readonly case. This has been corrected.
SR-D5388 · Issue 461278
Corrected dropdown focus issue with dynamic layouts
Resolved in Pega Version 8.1.6
The focus was not retained on the dropdown field whose property was used in the dynamic layout for the refresh condition. Investigation showed that in pzpega_ui_doc_focus.js, the function "focusNextElement" was setting pega.u.d.gFocusElement set to null after the first load. This has been corrected.
SR-D14630 · Issue 491166
Thread label clipboard issue resolved for work objects using skipDCDataModelUpdation
Resolved in Pega Version 8.1.6
In some cases, when a case ID was opened in Designer studio, its corresponding thread name in clipboard was pxThreadName instead of caseID or workID. Tab labels are handled through the Declare_pyDisplay data page. Investigation showed the child page pyDisplay(Developer) of the parent page Declare_pyDisplay, which was expected to contain pyUIElements for each tab, was missing an element for the tab whose label was shown as threadName. As this error was only reproducible for work objects with the 'skipDCDataModelUpdation' property set as true in the 'pyWorkPage', this issue has been corrected by updating the show-harness activity step-2 so the 'skipDCDataModelUpdation' property value is explicitly copied from primarypage ('pyWorkPage' in this use case) to 'parameterPage'. In addition, an issue with filtering records based on Operator Preferences has been resolved by updating ActivityStatusContentHandler to use a simple Show-HTML of the same "ActivityStatusSuccess" content instead of going through an unnecessary harness execution during activity when there is no session established.
SR-D15428 · Issue 491567
Null check added to resolve non-impacting InvalidParameter exception
Resolved in Pega Version 8.1.6
Creating a child case from the SLA goal activity using the 'AddCovered' activity generated the message "Exception in queue item: cannot be null or blank". The error "com.pega.pegarules.pub.clipboard.InvalidParameterException: cannot be null or blank" was also seen. However, no functionality impact was observed. This has been resolved by adding a null check to the getPortalName method, and modifying the HarnessUIBuilder.java file to add safe checks for whether 'portalName' is empty or not.
SR-D15875 · Issue 486381
Spinner wheel dom correctly cleared after incomplete case closure
Resolved in Pega Version 8.1.6
Incorrect behavior of the spinner wheel during a case search following the browser being closed while a case was open has been resolved by updating pzpega_ui_doc_actionRouter to ensure the wheel dom is correctly cleared.
SR-D28469 · Issue 499089
Corrected exceptions report appearing on user screen
Resolved in Pega Version 8.1.6
When "Break on all exceptions" was enabled, the exceptions report was visible on the end user screen when using IE11. This has been resolved with updates to the 'pzpega_ui_dynamiccontainer' and 'pzpega_ui_doc_tabsupport.js' files.
SR-D28480 · Issue 499085
Corrected exceptions report appearing on user screen
Resolved in Pega Version 8.1.6
When "Break on all exceptions" was enabled, the exceptions report was visible on the end user screen when using IE11. This has been resolved with updates to the 'pzpega_ui_dynamiccontainer' and 'pzpega_ui_doc_tabsupport.js' files.