SR-C39203 · Issue 379154
Interaction ID retains decimal integrity for external SOAP XML
Resolved in Pega Version 8.1
Parse XML was incorrectly mapping numeric value to decimal property when the SOAP request was called from outside Pega. The SOAP XML contains a Pega DSM interaction ID, which is a long numeric value. During the handling the interaction ID is mapped to a decimal property, but the number lost precision and became incorrect. To correct this, the mapping has been made more precise so the integrity of the ID number is maintained.
SR-C39344 · Issue 385447
updated archive name parameter method to ensure zip files correctly download
Resolved in Pega Version 8.1
Multiple products could not be imported using the Product Migration command line utility, and the error "internal.archive.PRJarFile) ERROR - Unable to create PRJarFile ... (A file or directory in the path name does not exist.)" appeared. Instead of reading the archive name from PegaAccel_Management-Migrate-Target, the system was reading it from the PegaAccel-Management-Import where pxFileName was null in the DownloadZipFile activity. On analysis, it was found that first product zip file is downloaded and imported fine, but the error was received when downloading the second zip file to the target system. To correct this, the system will read the pxFileName from the myStepPage instead of pyWorkPage.
SR-C39372 · Issue 385403
Corrected duplicate index records created on mobile
Resolved in Pega Version 8.1
When creating cases on mobile, multiple duplicates were being created with the same time stamp due to a handling issue with the pzInskey of the case. This has been fixed.
SR-C39409 · Issue 377586
Resolved commit error for import of blobless class data by removing unexposed properties
Resolved in Pega Version 8.1
Import of blobless class data in to the system was failing because the system was incorrectly expecting properties related to px types, resulting in an error being thrown during commit for unexposed properties present in an external table. To resolve this, pzAddUpdatePageRecord and pzSavePageRecord have been modified to remove all unexposed properties before doing an Obj-Save.
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.