INC-161645 · Issue 634638
Java Bean import updated to handling differences in Java 7 and Java 8
Resolved in Pega Version 8.6.2
The behavior of the java bean Introspector class is inconsistent across different versions of the JDK when detecting indexed properties built off of java.util.List objects, causing Java Bean import to generate differently in Java 7 and Java 8. This has been resolved by updating PRIndexedPropertyDescriptor to better handle this JDK difference by resolving indexed read and write methods manually using simple reflection.
SR-D51555 · Issue 516495
Resolved system hang after changing input field value post note
Resolved in Pega Version 8.2.5
After upgrade, a session was hanging in a Non-Member Search Phone interaction after navigating back from "Add or edit attachments" window. The same code worked as expected in the Member Search Phone interaction. Investigation showed that changed values (transaction ID, pzFromFrame) were being sent to the client twice, once in the popup window after attaching the note and again to the parent window. When the changed values were consumed and used in next actions, a mismatch resulted in pzFromFrame. To resolve this, the system has been updated so the Client will not consume the pxThread.pxClientExchange value if pxThread.pxClientFrame is different from what the current tracker is using.
SR-D41882 · Issue 510092
Resolved Ajax container blank tab
Resolved in Pega Version 8.2.5
When using an Ajax container in tabbed mode, opening a work item from the dashboard and clicking on the Begin button resulted in the Workitem closing automatically and the main tab becoming blank. This was rtaced to the system attempting to set the last tab header before it was created, and has been resolved by removing an instantiateTabs call in the success callback of the close MDC tab functionality in the pzpega_ui_redux_impl file.
INC-173452 · Issue 666440
Quorum capability check added for external Elastic Search
Resolved in Pega Version 8.6.2
The error "java.lang.UnsupportedOperationException: Not supported for client/server mode at search.indexmanager.internal.ESIndexAdminHTTP.isQuorumAvailable" was appearing when attempting to use external Elastic Search to index a dedicated index, and the queue processor was running but showed multiple broken items. This has been resolved by adding a capability check with ES_INITIALIZE_EMBEDDED_CLUSTER to prevent a quorum check with external elastic search.
SR-D39369 · Issue 513096
Handling added for images in true/false checkboxes causing security policy issues
Resolved in Pega Version 8.2.5
The out-of-the-box Pega security policy AllowPegaCollaborationServices, which is included functions such as Pega Customer Services for Healthcare and required by Pega Cloud Collaboration Services, was blocking Pega images from webwb. As an example, using a checkbox "*truefalse" configured with two images for true and false values when this Security Policy was set (which has Image-Source self set), a console error was generated. This was caused by the images URL being a base-64 string instead of a page URL. This meant that when the checkbox was configured with an image, the image was being converted to bytes as if for offline. To resolve this, separate handling has been added for online cases.
SR-D52695 · Issue 515972
Pagination context switch handling updated for mouse scroll
Resolved in Pega Version 8.2.5
When using various tables in the client application that have the Pagination mode set to 'Progressive' and that contain hyperlinked elements on which an 'Open Work by Handle' action has been defined, clicking an element that was loaded progressively intermittently generated an alert with the message 'Empty work item handle'. Investigation showed that dragging the scroll bar to access the latest cases worked, but using the mouse to scroll and select replicated the issue immediately. This was caused by context not being properly switched to the current harness while scrolling due to missing context switch handlers. To resolve this, code changes have been made to set the correct context before sending the request.
INC-176952 · Issue 660482
DateTime format check added for REST response
Resolved in Pega Version 8.6.2
While retrieving case details using the standard GetCases API, a datetime field defined on a work object was returned in JSON date format i.e. "QuoteExpiryDate": "2021-06-09T14:00:00.000Z". However when the same field was mapped to a flow action's section, the value was retrieved by the GetAssignmentAction API which returned the value in Pega's date format, "value": "20210609T140000.000 GMT". This was traced to a missed datetime format check in the REST response, and has been resolved by using the Rule-Utility-Function pzAPICreateJsonForField to handle the conversion of the time stamp to JSON format.
INC-180275 · Issue 666455
Collaboration control hidden if data type is delegated
Resolved in Pega Version 8.6.2
When collaborating using a customized CaseManager portal with some delegated data types, the admin user refreshing the Data Type view changed the collaborator's view from the portal to show the Data Type tabs, allowing the second person to open rules (properties, Data Pages, etc) and see the configuration even though they could not make any changes. This has been resolved by updating pzDataTypeDelegated to display the collaboration control only if pzDelegation is false.
SR-D43788 · Issue 512543
Corrected Last Added By values for reports created in report browser
Resolved in Pega Version 8.2.5
After creating a report using report browsers in the case manager portal, opening that report definition rule in Designer Studio showed the person's name who created the pydeafult report instead of the expected values for Last added by(Operator ID & Name) and Last Moved by (Operator ID & Name,Date). This has been resolved by adding steps to pzRRSaveAs which will fix the history details when making a new report in the report browser.
INC-186466 · Issue 670291
Style selector workaround added for Internet Explorer 11
Resolved in Pega Version 8.6.2
When using UI-Kit 15.0.1 with Microsoft Internet Explorer 11, the responsive behavior of the left navigator was not working as expected, it was not possible to Customize/Style the File Path control completely, and the AutoComplete control and Date Time Controls had a blue border on hover/focus. This was traced to the styles not being correctly selected because they contained the selector "focus-within" which is not supported in this browser. This has been resolved by adding focus-within separately so Internet Explorer will ignore the selector.