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.
SR-C42254 · Issue 380800
Correct step pages set for openUrlInWindow configured inside an RDL row section
Resolved in Pega Version 8.1
The step page when a Repeating Dynamic Layout is rendered was always the first element in the Page List. This meant that given a Page List with 3 entries: .ExamplePageList(1), .ExamplePageList(2), and .ExamplePageList(3), when the first Repeating Dynamic Layout was rendered it was expected that the step page would be .ExamplePageList(1), when the second Repeating Dynamic Layout was rendered the step page would be .ExamplePageList(2), and when the third Repeating Dynamic Layout was rendered the step page would be .ExamplePageList(3). In actuality, when the first Repeating Dynamic Layout was rendered the step page was .ExamplePageList(1), but when the second and third RDLs were rendered, the step page was also .ExamplePageList(1). This was traced to a missed use case: when openUrlInWindow was configured on a control inside the RDL row section with the "use page" setting, the pzPrimaryPage was incorrectly stamped, i.e., the step page of the first row is stamped on controls of all the rows. This has been fixed by making use of pzAuto.getUIComponentRuntime().generateActionTokenForStepPage() instead of tools.getStepPage().getReference().
SR-C42283 · Issue 380088
Client library version will be cached for Apache use in building client-response headers
Resolved in Pega Version 8.1
As an unintended consequence of refactoring the REST connect client code, an SQL query was being passed on every REST connect call to retrieve the version of the 3rd party client library being used for REST connectors (Apache HTTPClient 4.5.2) for insertion into the client user-agent string. The extensive use of REST connectors was driving up DB elapsed/CPU time, sometimes involving between 60-110K queries in a 60 min period. To correct this, the version info will be retrieved on the first use of ComponentsRESTClient and then be re-used for each subsequent call. This will make Apache avoid the code path that does the queries.
SR-C42418 · Issue 385133
Enhancement added to allow multiselect input by clicking outside the area
Resolved in Pega Version 8.1
Previously, the multi-select control would process, add, and set the value on 'enter key'. An enhancement has been added to allow setting the value in multi-select input even when the users click outside after entering a value, allowing multi-select to also work like a normal input text box. To do this, a flag has been added to not clear the multiselect value on blur.