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.
SR-C42662 · Issue 384508
Required flag set by passed value is maintained while toggling
Resolved in Pega Version 8.1
When using a section where a radio button field was required based on the value of another field, it correctly showed the * indicator for required the first time but would hide it subsequent times. This was traced to client side required expressions not toggling properly for radio buttons due to class and data-class attributes missing null checks that resulted in setting null as the attribute value. This has been fixed by adding a check for the attribute value existence before toggling.
SR-C42732 · Issue 386315
Addressed memory leak on non-optimized DSM clipboard
Resolved in Pega Version 8.1
A memory leak was seen after setting DSM/clipboard/optimize to false and executing a DataFlow load test using regular clipboard pages. This has been addressed by disabling the inference engine on the input thread of the DataFlow.
SR-C4280 · Issue 349923
Template fixed so JAWS reads menu name when an image is used
Resolved in Pega Version 8.1
When using template mode, JAWS was reading the image src text for navigation menus configured with an image on them. This was caused by the role="link" aria-haspopup="true" being wrongly generated on the <img> tag, and has been fixed by updating the template file to generate the role only for an anchor tag and not on img.
SR-C42819 · Issue 382453
Enhancement added to configure location for data import error CSV file
Resolved in Pega Version 8.1
An enhancement has been added to allow the Data Import Error CSV file location configurable through the addition of the property pyErrorFileStorage. This property needs to be set before the input process is started and supports only filespec syntax. It should contain the fileStorage location like file://defaultstore:/ , file://amazons3:/, etc. The value can be set to any of the available repositories and the error file will be placed accordingly in the respective repository. This process is more flexible than DSS, and allows the site to configure different locations for different imports in the same application. If no value is passed to the import process, Defaultstore will be used.
SR-C4290 · Issue 347477
Reduced redundant reads of work objects during CheckLockingMode
Resolved in Pega Version 8.1
In analyzing captured Trace data, it was noted that there were several redundant reads of the work object, including within the pzCheckLockingMode activity. In order to avoid unnecessary opens of Work objects in pzCheckLockingMode, it has been modified to conditionally open the Work object/Cover object.