SR-C38997 · Issue 379285
Mobile buttons revised to workaround iOS browser click bug
Resolved in Pega Version 8.1
When using the iOS browser, buttons were getting stuck or frozen and requiring multiple clicks to execute. This was traced to an error in the iOS browser version 11.4 where click events are triggered with event.timeStamp as a negative number. To avoid this, the system will not rely on event.timestamp, but will instead get the current datetime and maintain it in prevEvent object.
SR-C3904 · Issue 353053
JAWS able to read validation errors on child of modified element
Resolved in Pega Version 8.1
After overriding some JS functions in UserWorkForm to prepend the field name to the validation message, JAWS was not reading out the validation errors. This occurred because JAWS was not able to read an alert from the child of a modified element, and a role alert has been added on the parent div to enable this use.
SR-C39148 · Issue 379402
Custom field duplicates removed from rule autocomplete dropdown
Resolved in Pega Version 8.1
After creating a key/value pair in the custom fields feature that is available in the "History" tab of the rule, the autocomplete displayed duplicate values if the same name was used in other section rule(SecD). In order to present a cleaner custom fields dropdown list, Embed-CustomFieldsList.pzGetCustomFieldValuesList will now remove the duplicate values.
SR-C39158 · Issue 379163
Sorting works for calculated field grid column
Resolved in Pega Version 8.1
Sorting was not working on a column when a date calculation function was given as a grid column sourced with a report definition. This has been fixed by adding the proper sort field in the DOM and correcting the check of pyFieldName in the gridSortpaginate activity.
SR-C39192 · Issue 377615
pyshowFAButtons property populated on primary page
Resolved in Pega Version 8.1
Buttons needed to finish an assignment or close a case were not visible in mobile offline. This was traced to the pyshowFAButtons property not being populated on pyWorkPage when the condition couldn't be triggered on client side, and has been fixed by modifying 'FlowActionHTML_Simple so it populates 'pyShowFAButtons' on the primary page.
SR-C3920 · Issue 350474
HKT short code added to en_US locale for time conversions
Resolved in Pega Version 8.1
When using the en_US locale, the time zone for "Asia/Hong_Kong " was displayed as "08:03 PM GMT+08:00" whereas for " America/New_York" it displayed as "07:07 AM EST". This was caused by there not being a time zone short code for Hong Kong in the en_US locale xml file, and this has been added so the time will be displayed as "07:07 PM HKT".
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.