SR-D28905 · Issue 421583
Compensation added for Cassandra v2.2 not honoring count limits
Resolved in Pega Version 8.3
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-C67397 · Issue 421637
Added check for missing rule data when using abstract class in CSS
Resolved in Pega Version 8.3
Including CSS optimization with abstract class in the Advanced tab of the 'Add Optimization' Screen resulted in a Null pointer exception error. This has been resolved by adding a check for missing data from a rule to make the system more resilient in its handling of a corrupt flow-action clipboard page.
SR-C80948 · Issue 421764
ProfileLink control updated to resolve opening issue
Resolved in Pega Version 8.3
The profile was not opening when the Operator Profile link was clicked. This was traced to certain functions having been moved to javascript files that were not included by default in the ProfileLink control. To correct this, the control has been modified to include the needed javascript files and the appropriate references have been updated to match.
SR-C75723 · Issue 421825
Rollback filter query updated to handle very large classes mapped to the same history table
Resolved in Pega Version 8.3
When rolling back the imported product file using deployment manager, the error "DatabaseException caused by prior exception: org.postgresql.util.PSQLException: ERROR: column "pzinskey" does not exist" was seen. This was traced to the rollback process picking the already processed items from the history table due to an incomplete filter query that occurred when there were more than 1000 classes mapped to same history table. This has been resolved.
SR-C80215 · Issue 421848
Migrated Data Flows open correctly from the data flow landing page
Resolved in Pega Version 8.3
After upgrade, Data Flows made in an earlier version could not be opened from the data flow landing page. Instead, a generic error screen was displayed and an NPE on activity pxMigrate was logged. This was caused by a missing null pointer check, and has been corrected.
SR-D22734 · Issue 421883
Added check to pxDateTime for incomplete date
Resolved in Pega Version 8.3
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-D35291 · Issue 421883
Corrected minute spinner for datetime with time interval
Resolved in Pega Version 8.3
If a datetime control was configured with a time interval set to use "Allow time to be displayed in the interval of minutes", the minutes spinner was undefined at runtime. This has been resolved with modifications to pzpega_ui_calendar.js to update the minuteSpinner value based on if time interval is set or not.
SR-C85035 · Issue 421946
Added getIfPresent check for Field Value parameters with pzAPICreateJsonForView
Resolved in Pega Version 8.3
Calling pzAPICreateJsonForView was altering case values if localized field value parameters were added. This has been corrected by performing a getIfPresent and getIfString on the property pyFieldValueParams so field value parameters will not be added to the main page if they're not present.
SR-C74054 · Issue 422024
Handling added for summary columns in Export to Excel
Resolved in Pega Version 8.3
When a field has an aggregate function in Report Definition, the column alias changes and is not the same as the property name. The consequence is a mismatch between the result set column name and the property name from the property list created beforehand. This results in blank fields when using the "pxDownloadDataRecordsAsCSV" activity for Export to Excel. In order to support the export of summarized columns in Report Definition, an enhancement has been added that uses the column label as an alias for aggregate fields in the native SQL builder of the exportData API to form a map between the property name and the alias name and use it while iterating over the result set.
SR-C81410 · Issue 422136
Radiobutton aria-label enhanced to retrieve localized field value
Resolved in Pega Version 8.3
Localization code has been added to the pzpega_ui_template_radiogroup file to support using RadioButton aria-labels for Field value.