SR-C41067 · Issue 382608
Number type conversion from DSMClipboardPage matches platform page
Resolved in Pega Version 8.1
The DSMClipboardPage implementation behaved differently than the platform page regarding converting numbers to decimal and when rounding took place. To correct this, the behavior of number type conversion from DSMClipboardPage has been aligned with the behavior from the platform page by calling an API provided by the platform.
SR-C41076 · Issue 379073
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-C41426 · Issue 378692
Resolved survey userscript JS error on mobile logoff
Resolved in Pega Version 8.1
A JS error was being generated from survey_ui_userscript_offline.js when logging out of the mobile application. This was caused by a missed null check for the QPREFPage before referencing property on it, and has been fixed.
SR-C41461 · Issue 386651
DateTime control fixed for year selection with unlimited Date Range
Resolved in Pega Version 8.1
After upgrade, there was a difference in behavior in the datetime control -> year range selection. With default configuration, it was possible to select a maximum of 10 years backwards and forwards, but if the Date Range option was not checked it was not possible to select any year. This has been corrected by implementing spinner functionality for an infinite number of years if the Date Range restriction is not used.
SR-C41540 · Issue 378722
Filter indicator color repaired for frozen grid headers
Resolved in Pega Version 8.1
The filter indicator color was not changing for columns when the header of grid was frozen. This has been corrected by updating GenerateGridHTML to generate the correct RDColumnName for freeze header grid columns.
SR-C41566 · Issue 382974
Date Picker On Change properly triggered in Standard mode
Resolved in Pega Version 8.1
A date selected from the date/calendar picker was not being reflected on the clipboard if there was an action - Post value (on change event) configured. When Legacy Mode was used, the clipboard was updated immediately, but when the standard mode was used the clipboard was not updated. This was traced to a non-auto-generated "Date" control not executing change events, and the function calls have been updated to correct this.
SR-C41775 · Issue 380461
Autopopulate mapping corrected for property references created under previous system versions
Resolved in Pega Version 8.1
After upgrade, the pzAutoPopulate information was missing when opening a work object which contained a property which referred to a data page. This caused the data page load to fail because the parameter (which was actually present on the page) did not get passed. Investigation found a backward compatibility issue that caused the autopopulation to fail in the new version: reference links were not built with the right parameter values during blob serialization because parameter information was stored in pzAutoPopulateMap (new) instead of pzAutopopulatedKeys (old). This has been corrected so the properties will be mapped appropriately.
SR-C42096 · Issue 386832
Parent tree grid edit mode passed to generated children
Resolved in Pega Version 8.1
Tree Grid was becoming editable when the child items were expanded. This was caused by the ReadOnly parameter not being passed when calling pzgetChildNodes, resulting in the edit mode of the parent section not being known when generating the child nodes. This has now been fixed so the edit mode will be passed.
SR-C42129 · Issue 382150
Created-in version populated in class ruleform dropdown
Resolved in Pega Version 8.1
In class rule form, the versions from the version dropdown were not visible after upgrade. This was due to the property pySPRuleSetName not being set on the client, and has been corrected by setting the section @baseclass.RuleFormMain and including the control pyRuleSetName_RF to populate the pySPRuleSetName.
SR-C42241 · Issue 385882
Standard format min-height added to hold target positions
Resolved in Pega Version 8.1
The Radio button was not being selected when clicked. Investigation showed that when the button was opened in a modal dialog the default focus was set to 'true', but clicking on it did not switch it to 'false' as expected unless it was clicked twice. This was due to a modal resize after the error message was set: since an error message pushes radio options up, the click was being fired outside of the radio option. It was possible to put in a text input with visibility as hidden to solve this height issue, but the code has now been updated to create a min-height as a standard format. This will ensure that the click is fired on the radio button even when an error message is shown.