Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

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.

SR-C82408 · Issue 422326

Repaired instance insertion for REST connection invoked via Queue

Resolved in Pega Version 8.3

After upgrade, the REST connection invoked in an activity which in turn called out-of-the-box ProcessQueue was not getting the response into the SYSTEM-QUEUE-EXECUTIONREQUEST-CONNECT-CREATEBOOKING instance. The right response was observed coming from other source systems in the logs, and the work object status also changing as expected. This has been resolved by exposing a DSS to revert to the old behavior of Response being present in the queueItem when a connector is queued for execution.

SR-C84294 · Issue 422375

Pagination repaired for RD using alternate database

Resolved in Pega Version 8.3

On selecting "Use alternate DB" option available in Report defenition and fetching the results of the RD to a grid, the results were not being fetched from the alternate DB but were fetched from the Pega DB only. This was traced to the property pyUseAlternateDB being overridden in step30 of pxRetrieveReportData activity. This step is skipped if it's report viewer, so if the same report is invoked from report viewer iit worked properly. To resolve this issue, the system has been modified to skip the step30 not only for report viewer but also if Param.pyUseAlternateDB is empty.

SR-C61656 · Issue 422434

CPU time will be fetched from MBeanServer instead of the JRE application to provide consistency

Resolved in Pega Version 8.3

The value of CPU time in the Enterprise health metrics was being given in nanoseconds instead of seconds after the IBM JRE version was upgraded by applying Websphere Application Server patches. The CPUTimer is a platform class which has logic specific to different JRE vendors; in order to provide consistent results regardless of which JRE is used, the system has been updated to always fetch the values from the MBeanServer.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us