SR-C43501 · Issue 382522
Handling added to clear dashboard Data pages and thread when switching activity
Resolved in Pega Version 8.1
After publishing a dashboard to an application, everything worked as expected when directly logging into that application. However, if the user had multiple access groups and switched to another access group, the wrong dashboard was displayed and D_pxUserDashboardLoadList was not reloaded. This has been resolved by moving the D_pxUserDashboardLoadList Data page to Thread level and adding the new Data transform PZCLEARDASHBOARDDATAPAGES called from pzClearDataPagesBeforeSwitch. This will clear the dashboard Datapages and the thread when switching the activity.
SR-C43567 · Issue 381665
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-C43718 · Issue 388308
Repaired wrap text in first column of tree grid
Resolved in Pega Version 8.1
The Wrap Text for the first column in a Tree Grid was not working. This was an error introduced during grid CSS optimization that caused white-space: normal to be overwritten by oflowDiv styles. The code for the sector has now been updated to ensure that white-space: normal style is applied for the first column of the tree-grid.
SR-C43831 · Issue 383613
Updated data retained when form error is encountered during offline application validation
Resolved in Pega Version 8.1
If a hard edit error message appeared during validation in the offline mobile app, changing the property value and syncing resulted in only the old data being retained and not the new. This was due to missing handling: when a form error was encountered on the page, diffSnapShot was updated with the recent changes but they were not added to the action queue. When the form error was corrected and resubmitted, only the new diff changes were sent to the action queue and the earlier changes were discarded. To correct this, the algorithm has been modified to perform the diffing for the workpage snapshot during record action, instead of during the mergeWorkAndForm.
SR-C43905 · Issue 387467
Locale will be considered while validating imported decimals for the clipboard
Resolved in Pega Version 8.1
When using a specific locale and importing decimal value in a format specific to that locale, the import wizard was throwing a bad decimal value error If 'skip validation' was unchecked during import. To resolve this, the locale will be considered in parsing the decimal value while populating the clipboard page prior to dictionary validation.
SR-C44194 · Issue 383066
Cursor pointer corrected for non-interactive grid cells
Resolved in Pega Version 8.1
When the mouse cursor was placed over any cell in a grid, the mouse changed to a pointer indicating an activity even when there was no activity to perform. This was an error introduced when the grid CSS was refactored and optimized: the hand cursor should only be used for interactive elements and causes confusion when displayed on a static table. The behavior has now been reset and will correctly detect whether actions are configured and display the proper cursor.
SR-C44375 · Issue 387180
Check added for multiselect object type when using Microsoft Internet Explorer 11
Resolved in Pega Version 8.1
Using the multi select control worked fine in Google Chrome but was throwing JS errors when used in Microsoft Internet Explorer 11 and causing the whole flow action to hang. Object.keys on a non-object throws error as per ES5, but on ES6 a non-object argument will be coerced to an object. This error was seen because the older version of Microsoft Internet Explorer still uses ES5. To better handle this, the system will check for the object type before using object.keys in pzpega_control_multiselect.js.
SR-C44548 · Issue 384154
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-C44701 · Issue 389484
The flag internNsUris set to 1 to handle 3rd party XML parser cache access
Resolved in Pega Version 8.1
Heavy thread contention was seen over an internal cache when using a third party stax XML parser. Because the parser interns namespace strings, which is a synchronized cache, quite a few threads were spending a significant amount of their time blocked. The flag internNsUris comes from a “config” object, and the config flag will be set to 1 to resolve the issue.
SR-C44707 · Issue 384115
Leading/Trailing 0s retained in Export to Excel
Resolved in Pega Version 8.1
Leading/trailing 0s were lost from text after export to Excel. This was traced to ReportUIField.getReturnObject treating the text type as number type if and only if the text property holds numeric content. To correct this, ReportUIField.getReturnObject has been modified to set the datatype to String if its a text type.