SR-D23340 · Issue 497607
Calendar begins with Saturday in the Arabic locale
Resolved in Pega Version 8.1.6
When using the Arabic locale, the week was not starting on Saturday as expected, but was showing Thursday as the first day. This has been corrected.
SR-D2615 · Issue 439227
Added function to auto-validate Chinese date
Resolved in Pega Version 8.1.6
If a datetime property with custom format was created in the zh_CNadtimezoe (Asia/Shangai) locale, the property was not updating if a date was selected with any time unless an onchange refresh action was included. This has been resolved by adding a function that will automatically validate the date for the Chinese locale.
SR-D9132 · Issue 457357
Performance improvements for EventStoreWriter class
Resolved in Pega Version 8.1.6
The cache protocol has been modified In order to improve performance for the EventStoreWriter class.
SR-D16934 · Issue 493704
External Cassandra nodes listed in DDS cluster
Resolved in Pega Version 8.1.6
Nodes of an external Cassandra cluster were not listed in the DDS cluster except for the first one in the host list, and when the “only” listed Cassandra node was restarted, the status on the DDS cluster LP did not become “NORMAL” afterwards. In addition, even though other C* nodes were up and running, the external Cassandra cluster was reported as unreachable. This was an unintended side effect of work done on the landing page to reflect the real state of the nodes after some were killed and restarted, and has been corrected by refining the equals() and hashCode() methods for DDS member info in order to better differentiate the external Cassandra nodes.
SR-D28905 · Issue 500674
Compensation added for Cassandra v2.2 not honoring count limits
Resolved in Pega Version 8.1.6
Running CassandraEstimateNumberOfRecordsOperation on a large data set was causing a ReadTimeoutException. Investigation showed that contrary to its documentation, Cassandra v2.2 ignores limits intended to stop all records from being counted. In order to compensate for this, the system has been modified to skip the first of two attempts to estimate the number of records (first cql count() query with limit 1000) and the estimated number of records will only be retrieved through JMX.
SR-D15844 · Issue 496777
Flag set for using defer load context switching with Microsoft Internet Explorer
Resolved in Pega Version 8.1.6
Defer load section was not working as expected due to Microsoft Internet Explorer 11 not maintaining the context of the section during busyIndicator hide. To avoid this, a flag 'pega.ctxmgr.skipContextSwitching' will be set during the hide of busy indicator if Microsoft Internet Explorer is used, and the harness switching context will then be decided based on this flag.
SR-D27041 · Issue 499047
Manual value group addition support available
Resolved in Pega Version 8.1.6
In a test case created for a data transform containing a value group property, that value group property could be added by clicking the + sign in the left pane of the test case, but a value group property could not be added manually by clicking the add row button. This has been resolved by adding support for manually adding value list/value groups. The activity steps which were using @java function have also now been replaced with a getproperty function.
SR-D10178 · Issue 423054
Tika library upgraded to v1.20
Resolved in Pega Version 8.1.6
The tika-parsers and tika-core version have been upgraded to version 1.20 .
SR-D20292 · Issue 495147
Race condition handling added to resolve stuck class loader threads
Resolved in Pega Version 8.1.6
A JVM became unresponsive after new JVM traffic was brought in. In reviewing the threaddump, there were hundreds of threads that originated from PRClassLoaderDB.getDefinitionForName or PRClassLoaderDB.getorCreateDefinitionForName found in a "stuck" state waiting on a condition. Investigation showed there was a thread deadlock caused by the system loading class definitions while an external resource was asking for a snapshot of the resources being loaded. This has been resolved by adding handling for the race condition.
SR-D14521 · Issue 486530
Added support for sorting by field value instead of localized value
Resolved in Pega Version 8.1.6
In a datapage-sourced dropdown with 'group by functionality' enabled in ascending order, the values were being sorted according to their localized value and not their field value. This was a difference between templatized and non-templatized handling, and has been resolved by adding the ability to sort the group label by field value in the templatized UI.