SR-D18234 · Issue 491749
Updated backwards compatibility for custom date/time wuith extra text
Resolved in Pega Version 8.1.6
After upgrade, migrated extra text in the custom date format was causing confusion. The previous support of additional text on earlier versions was not intentional, but was allowed by the previous default of non-template mode. In template mode, when custom datetime format includes plain text in single quotes, pega.ui.Formatter.formatDateTime processes the entire format string instead of only the datetime formats. To avoid confusion, updates have been made so if a custom format has plain text in quotes, the system will separate the formats and resolve them.
SR-D22734 · Issue 492778
Added check to pxDateTime for incomplete date
Resolved in Pega Version 8.1.6
An out-of-the-box pxDateTime control configured with "Display mode" = "Dropdown list" was generating the error "Error in the launched portal TypeError: mom.date is not a function at line 714 Column 31" if an incomplete date was selected (such as year only) before saving the case. This occurred because the mom object tried to call date() which was undefined because the date was incomplete, and has been resolved by adding a check to see if the mom holds a valid date before calling the function.
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 .