SR-D1270 · Issue 488262
DB table mapping will check for existing properties before creating them
Resolved in Pega Version 8.1.6
Using the Database table class mapping tool to map an external database table to a class and create properties according to columns in the table was resulting in the property being created as 'not available' and not case sensitive if the property to be created while mapping was already present in the inheritance hierarchy. This led to an error caused by the property validation failing in the validateReportDesignTab activity. Previously the database table mapping tool did not check to see whether the properties to be created existed already in the parent class hierarchy. With this update, the system will check before allowing the mapping, and if the properties exist in the hierarchy already they will not be populated.
SR-D9198 · Issue 485218
Connections leak fixed for data-admin-db-table Oracle DB connections
Resolved in Pega Version 8.1.6
When exporting a product that contains a lot of Data-Admin-DB-Table instances to extract (>180), JBoss was crashing due to losing the connection to the DB as it reached the maximum number (100 connections) of DB sessions created during the export. Each time the export was launched, new connections were generated in the pool of ORACLE DB sessions that were never closed except by rebooting the environment. This was traced to a connection leak scenario within SQLGenerator.getCaseSensitiveColumnNamesForTable where a connection was being taken out inside a different try/finally block than where the connection was being closed, so the connection could potentially never be returned. This has been corrected.
SR-D10889 · Issue 482667
Intervals for DateTime control inside table grid corrected
Resolved in Pega Version 8.1.6
The "allow time to be displayed in the interval of minutes" feature did not work as expected for a DateTime control configured inside a table grid. If a value for minutes was chosen, say 30 minutes, it displayed all the minutes from 00 to 59 instead of displaying 00 and 30. The same control used inside a simply dynamic layout worked correctly, displaying 00 and 30. This has been resolved by adding logic to support having only time with drop downs.
SR-D15910 · Issue 491008
AM/PM time setting corrected for Riyadh timezone
Resolved in Pega Version 8.1.6
When logged into the Pega mobile application with operator locale as ar_AR and timezone as Asia/Riyadh, selecting time as PM resulted in it being set to AM with Native control. If the native control was unchecked, a blank screen resulted. This has been corrected.
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.