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.
SR-C11373 · Issue 353185
Logging enhanced for names of activities
Resolved in Pega Version 8.1
The new logger 'LogActivityExecution' has been introduced to log the names of activities running on the system as Info loggers. To get these info forced log messages, enable 'INFO' on 'LogActivityExecution' logger. This can be done either changing in prlogging.xml or by changing logger settings in Designed studio landing page. The info message will look like: "Activity is being executed - Activity name: 'pyUpdateActiveUserCount', Class name: 'System-Status-Nodes'"
SR-C11499 · Issue 352774
Performance improvement for Mobile use of CaNull Pointer Exceptionrform
Resolved in Pega Version 8.1
Performance issues were seen in the Mobile application while processing work referencing the when rule CaNull Pointer Exceptionrform. This was due to the "CompareTwoValues" expression underperforming for the Boolean comparison case, and performance has been improved by replacing it with an "ExpressionEvaluatesToTrue" expression.
SR-C11712 · Issue 354391
Incremental Indexer Agent skips instances being indexed by updateIndex API
Resolved in Pega Version 8.1
If NRT Indexing and immediate search queries were processing while the FTSIncrementalIndexer was doing an update, they sometimes conflicted and the FTSIncrementalIndexer would temporarily alter the content in the index. This resulted in incorrect search results during the run, though in the end the content would be correct and match the database to give correct results. To address this confusing behavior, an enhancement has been added to prevent instances being indexed by updateIndex API from being overridden by Incremental Indexer Agent.