SR-C39541 · Issue 379148
Operator image upload persistence fixed
Resolved in Pega Version 8.1
Sporadically, operator avatars uploaded were not successfully saved. The avatar would change on the ruleform, but after saving the avatar reverted to the default silhouette. Investigation showed this was linked to the InsKey generation, and the Data-Admin-Operator-ID.Validate activity has been updated to set the correct InsKey of the generated dci image to correct this.
SR-C39546 · Issue 383651
Listeners added to explicitly unload windows to resolve OpenURLInWindow memory leak
Resolved in Pega Version 8.1
Opening another domain URL's using the "openURLInWindow" API was causing a memory leak. This was traced to the beforeunload listener not being triggered by the browser, as it is a cross-site security issue. To resolve the leak, the system will handle cross domain windows by holding the window name instead of an object and ensuring it is closed during the window unload. For same domain windows, listeners have been put in place to add it to opened windows during onload and then remove it during window unload events.
SR-C39546 · Issue 387806
Fixed Google Chrome report browser memory leak
Resolved in Pega Version 8.1
A memory leak was seen when toggling from the report browser to a different screen in Google Chrome. This was due to an event listener holding onto a window in pzpega_browser7, and has been fixed.
SR-C39588 · Issue 377514
Exception details and stack trace added to Bix -l
Resolved in Pega Version 8.1
When running BIX with the -I option, it failed with the message "( internal.access.ExtractImpl) INFO - Could not open file for reading " and nothing further. In order to improve diagnostics, the system will print the exception details and stack trace.
SR-C39676 · Issue 379470
Grid filtering "list only" option repaired
Resolved in Pega Version 8.1
The Grid filtering "List Only" option was not working on a grid that displays a list of claims on two different screens, the range for date properties did not show up in the filter box, and the "Apply" button on the filter appeared to be disabled. If there was another column set to Filtering: "Auto", then the filter could be applied. Once a separate filter was applied, the original "List Only" filter could then be applied. This has been resolved with the addition of a typeOf check while calling Displayerrors function in csvalid.js.
SR-C39690 · Issue 381877
New RUF added for deleting data type from CSV during import
Resolved in Pega Version 8.1
After upgrade, attempting to use the import CSV functionality to delete caused the wizard to hang and log the error 'PRRuntimeException: Can't continue with file upload. Can't read File'. This was caused by the system using the pxHasSingleKey RUF in pzDeleteRecords to check whether or not the class has a single key, which does not work for this use case. In order to support this method, a new RUF(pxHasSingleKeyAndExposed) has been created which will check the class for single key and also will check whether it is exposed or not. This will result in executeSQLForBatchDelete API being skipped and pzCreatePagesAndImportInBatch will get called instead.
SR-C39747 · Issue 383893
Added call to pyconvertedvalue to preserve number format in BIX extract filtering
Resolved in Pega Version 8.1
When creating a BIX extract rule with a filter of integer property on LHS and a constant integer value of RHS which is of 8-9 digits such as "filter : salary = 100000000" , saving the extract rule converted this RHS value to 100,000,000 and the filter showed as : "salary = 100,000,000" .In this scenario, running the extract rule generated an error in the log. This was traced to the system converting the filter value ( <pyfiltervalue> whose value is "100,000,000" ) to a number and causing a numberformat exception. This was a coding error that missed a call to supply <pyconvertedvalue>, and has been fixed.
SR-C39791 · Issue 379314
Group processing and StartDate issues resolved for Timeline controls
Resolved in Pega Version 8.1
Two issues were seen in the Timeline control:Issue 1: When a technician was selected who had no events, the Technician was not shown in Y-Axis (Groups were not being displayed). A blank screen was shown instead. This was caused by the a condition where an empty datasource caused createDataset to return without processing groups. This has been corrected by adding handling so the system will initialize dsArray with an empty value if needed to ensure the group related processing takes place. Issue 2: The start range for Timeline was not respecting the StartDate given for the Events display. In this case, if either the start or end time was not available then neither was set. To resolve this, If an end date is not specified then it will be marked as the current date.
SR-C39796 · Issue 383047
Enhancement added to switch tab name localization when locale switches
Resolved in Pega Version 8.1
When launching a Harness in a tab onclick of a link/button from a section, passing tab name as a localized field value was not working properly when switching between different locales. This was caused by the Tab name not getting updated on click on Launch harness, and has been corrected with the addition of a new parameter "bLocalize" for pzActionAppendValue to invoke getLocalizedTextForString if the parameter is true. This value will be passed as true when called from pzActionShowHarness newDocument case.
SR-C39815 · Issue 381813
Font files updated to support Turkish characters in VBD
Resolved in Pega Version 8.1
It was possible to use Turkish special characters in the labels of Business Issue and Groups, but VBD did not show these Turkish characters as in the screenshot. To enable this, a new set of font files with larger character sets has been added which includes the Latin-1 Supplement and Latin Extended A blocks to which the Turkish characters belong.