SR-C11041 · Issue 352810
UI retains layout when RTE maximized for editing
Resolved in Pega Version 8.1
After using the 'Maximize' button in a Rich text editor in a section, the screen layout was incorrect after visiting another window and toggling back to the one with the RTE. This was a timing conflict: when the RTE is maximized CSS styles are captured and removed from the Harness, and whenever refresh section fires onChange, RTE is destroyed and recreated. To make sure the UI does not get distorted, pzpega_ui_richtexteditor.js has been modified to resize the RTE before destroy and to set the CSS styles back to the harness.
SR-C11138 · Issue 357104
Removed stray attribute causing Accessibility error
Resolved in Pega Version 8.1
While validating the Case Manager portal, a critical error thrown by the Accessibility validator was traced to the attribute 'aria-selected' being set to false for Tabs. This was misplaced code applied to an element that did not need it, and has been removed.
SR-C11146 · Issue 355013
Corrected thread contention performance issues for requestor create/retrieve
Resolved in Pega Version 8.1
A thread contention on Requestor retrieval was traced to a global level lock in PRNodeImpl.class, and the global lock has been replaced with a ReentrantReadWriteLock.
SR-C11148 · Issue 354987
Performance improvement for AccessInfoConclusion evaluation
Resolved in Pega Version 8.1
In order to improve performance during an AccessInfoConclusion evaluation, data will be stored in a ConcurrentHashMap instead of a Hashtable.
SR-C11149 · Issue 355078
Added prconfig setting to adjust sync policy for LAC
Resolved in Pega Version 8.1
Some contention on the monitor lock for the LocalizedApplicationContext was seen on sites with with thousands of concurrent users logging in and out. To improve performance, a prconfig setting has been added to LAC - registerUse() & deregisteruse(). to allow use of a looser synchronization policy.
SR-C11241 · Issue 355607
Support added for secured Connectors to use "Keystore location"
Resolved in Pega Version 8.1
Support was recently added for "External keystores" on the Keystore ruleform, seen in the new "Keystore location" drop-down at the top of the form, but Connectors were not able to use the new Keystore types (File reference and data page) for HTTPS connections. This ability has now been added by modifying SSLUtils.java and KeyStoreUtilsImpl.java to support the file reference keystore.
SR-C11241 · Issue 360907
Support added for secured Connectors to use "Keystore location"
Resolved in Pega Version 8.1
Support was recently added for "External keystores" on the Keystore ruleform, seen in the new "Keystore location" drop-down at the top of the form, but Connectors were not able to use the new Keystore types (File reference and data page) for HTTPS connections. This ability has now been added by modifying SSLUtils.java and KeyStoreUtilsImpl.java to support the file reference keystore.
SR-C11319 · Issue 352584
Mobile dropdowns accept data binding from all sources
Resolved in Pega Version 8.1
When entering reports on Mobile, dropdowns were being reset after filling in autocompletes and other dropdowns. This was traced to data binding not being supported for sources other than Associated, and changes have been made to the generateDropdown RUF to support data binding for all sources of dropdown to correct this.
SR-C11323 · Issue 352191
Tab header value works for SSO
Resolved in Pega Version 8.1
The Tab header value was not updated with the rule name or Work Object ID when SSO authentication was used with sub-domain URLs. This has been fixed.
SR-C11351 · Issue 356669
RDL FlowAction Section correctly rendered readonly offline
Resolved in Pega Version 8.1
When given a Repeating Dynamic layout in a Section which had the Primary Section and Detail Flow Action configured and the section in Detail Flow Action was configured to display in read-only mode, the layout worked as expected on Desktop and Mobile online, but enabling any case for Offline caused it to not be rendered in read-only mode. This was an issue with how the offline readonly information was being stored, and has been corrected.