INC-213918 · Issue 714454
Discard button works consistently
Resolved in Pega Version 8.6.5
After check out, the discard button was not working consistently for decision tables or MapValue. Investigation showed this occurred when an exported file was being downloaded in the same window, as the thread would be busy with the file and not able to perform the discard action on the window. To resolve this, the configuration for the download on the same window has been removed, exportToDecisionTable has been modified to handle an iframe, and a runScript action has been added to register the exportToExcel activity and download in iframe.
INC-215785 · Issue 722553
Corrected logic for parsing imported Excel formula cells
Resolved in Pega Version 8.6.5
Integers specified as cells with formulas in Excel were getting an additional ".0" in them due to them being parsed internally as doubles during the floating point arithmetic of the Apache POI library. This has been resolved by modifying the logic in ExcelUtils.java to apply DataFormatter to get the string value instead of an integer by default for a formula cell.
INC-216935 · Issue 714049
Corrected decision table scroll bar display in resized section
Resolved in Pega Version 8.6.5
Resizing a decision table window was causing the horizontal scroll bar to move out of the section while scrolling. This has been resolved by updating the HTML and adding the needed CSS.
INC-220385 · Issue 720010
Corrected Branch Code Score / Unit Test Rule count issue
Resolved in Pega Version 8.6.5
When reviewing branch quality, the "Rules with Test Cases" indicated 5 out of 7 rules were covered, but no rules were listed in the "rules without unit tests" tab and all rules within the branch had unit tests where applicable. Investigation showed the filter for withdrawn rules was not working correctly and they were shown as not having test cases. In addition, when a test case was in a branch but its tested rule was not in the branch, the test pass percentage calculation was being skipped and displayed as 0%. These issues have been corrected.
INC-220770 · Issue 718027
Null check added to getBaseRef
Resolved in Pega Version 8.6.5
When using a customized Cosmos portal that included tabs, some of the Pega APIs were not available in the child frame and javascript errors were generated when calculating the clipboard path for live UI elements. This was traced to invalid references to "pega.api.ui.util.getBaseRef", and has been resolved by adding null checks to the getBaseRef API call to make sure javascript errors are not thrown.
INC-191412 · Issue 692674
Large Data page join condition available for Mobile
Resolved in Pega Version 8.6.5
Support for a join condition has been added to the Large Data page for use in Mobile to match the use available on desktop.
INC-198193 · Issue 723624
Error correctly shows for each attempt to upload an oversize file
Resolved in Pega Version 8.6.5
The error message indicating an uploaded file exceeded the permitted file size was only shown on the first try on Android. Subsequent attempts to upload the same oversize file did not generate any error. This was due to a persisting value, and has been resolved by explicitly clearing the input value for the mobile browser upload.
INC-205683 · Issue 702561
Data transform actions supported in offline app
Resolved in Pega Version 8.6.5
Support has been added for pre- and post-processing data transform functionality and validation in the local actions of the offline app.
INC-222126 · Issue 721903
Improvement for mobile display error related to harness timing
Resolved in Pega Version 8.6.5
After updating from 8.1 to 8.6, working very quickly on mobile to create a case and refresh it resulted in a "Display error" screen that included the message "Failed to find instance @baseclase.pyCreate of type Rule-HTML-Harness". This was caused by the system not being initialized with the needed content and some target parameters therefore being evaluated as null. A preliminary fix for closeDocCallback when WebView is not loaded has been added which has significantly reduced the frequency of this issue. Additional work will be done towards a complete resolution in a future release.
INC-214974 · Issue 721181
Documentation updated for accessing D_pyUserInfoClaims
Resolved in Pega Version 8.6.5
When logging in using Org Credentials, trying to get the user details from D_pyUserInfoClaims did not return any information. This was due to the D_pyUserInfoClaims datapage being available only after authentication, so the claims information was not available during operator provisioning. The documentation located at https://docs.pega.com/security/86/mapping-operator-information-openid-connect-sso-authentication-service has been updated to include the following note: "This page becomes available and can only be accessed post authentication."