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-C66633 · Issue 408773

Corrected DADT mapping for PegaDATA tables during upgrade

Resolved in Pega Version 8.2

After upgrading, old data tables being upgraded to new data tables (local storage) had the DADT table mapping changed from PegaDATA to CustomerDATA schema even though the tables themselves remained in PegaDATA format. This was traced to a missed use case in an enhancement that allowed creating a data type only in a CustomerData data base. To resolve this issue, the validation for restriction of PegaDATA has been removed and the param.nonPegatable will be set to false in cases where the database type is PegaDATA in pzCreateLocalDataStorage.

SR-C70639 · Issue 409664

Node ID correctly transmitted for PEGA0066 Alerts

Resolved in Pega Version 8.2

The PEGA0066 alert containing information about synchronization errors or connection lost did not contain the correct value in the Node ID field, causing PDC to not be able to handle the alerts on mobile. This has been corrected.

SR-C68443 · Issue 410236

Changed French locale to use getshortmonths to descriminate between June and July in datepicker

Resolved in Pega Version 8.2

When using the French locale, there was a problem selecting the month of July from the date picker because the three-letter abbreviations of June and July are the same in French. To resolve this, the system will now use the Java API getShortMonths in the French locale which gives 4 characters for the months.

SR-C62635 · Issue 405290

Changed French locale to use getshortmonths to descriminate between June and July in datepicker

Resolved in Pega Version 8.2

When using the French locale, there was a problem selecting the month of July from the date picker because the three-letter abbreviations of June and July are the same in French. To resolve this, the system will now use the Java API getShortMonths in the French locale which gives 4 characters for the months.

SR-C41102 · Issue 410423

Resolved error in editing flow rule assignment shapes

Resolved in Pega Version 8.2

The submit of an assignment properties modal window was not closing the modal, and instead opened a new window with an error page indicating a NullPointerException. This happened whether or not there were changes made to the assignment properties, and occurred for the assignment shapes on any flow. This was traced to a UI limitation in the backward compatibility of the "parent.parent.pyWorkClass" property which caused the property reference to not be resolved for hidden controls in client side template. To correct this, updates have been made to "pzAssignmentTab" (in Data-MO-Activity-Assignment class ) and "pzPropertyPanel" (in Data-MO-Activity-Assignment-WorkAction class).

SR-C72568 · Issue 410837

Corrected underscores removed from attached filenames

Resolved in Pega Version 8.2

As an inadvertent side effect of work done to handle thumbnail image generation for file attachments with special characters, underscores were being removed from the names of all files attached to work objects. To correct this, the code has been refined to remove special characters from the parameter passed to generate thumbnail activity. Special characters will not be removed from the filename.

SR-C35967 · Issue 404321

Updated parameter handling for SECU0001 alert for accuracy

Resolved in Pega Version 8.2

In the SECU0001 alert, some fields contained incorrect values pertaining to a previous HTTP request, not the one that caused the alert, causing misleading information to be logged and sent to PDC. This was found to be an issue where when unexpected properties were found, the alert was being thrown from an early stage of processing, i.e, during inputProcessing where the current activity had not yet been set to the requestor state and therefore the current activity was not there in the stack frame. This has been addressed by getting the activity name from the HTTP request parameters and updating the diagnostic information with it so the alerts will be accurate.

SR-C71043 · Issue 411254

pzSendEmail returned to revious behavior of sending separate emails to work parties

Resolved in Pega Version 8.2

After upgrade, a change in behavior was seen when using the pzSendEmail activity. When pzSendEmail was called to send emails to work parties, a single email is sent to all recipients instead of separate emails to each recipient as it did in earlier versions. The SendSimpleEmail activity accepts a SendDiscreteMails parameter, the pzSendEmail activity has 'Pass current parameter page' checked so the default value for the SendDiscreteMails parameter was not used. This was a backwards compatibility error, and has been corrected by setting the SendDiscreteMails parameter to true by default in the pzSendEmail activity.

SR-C68500 · Issue 411293

Node ID correctly transmitted for PEGA0066 Alerts

Resolved in Pega Version 8.2

The PEGA0066 alert containing information about synchronization errors or connection lost did not contain the correct value in the Node ID field, causing PDC to not be able to handle the alerts on mobile. This has been corrected.

SR-C66283 · Issue 411633

Report Usage updated to always fully populate statistics regardless of page source

Resolved in Pega Version 8.2

After creating a report under the Log-ReportStatistics class, it was seen that reports under report usage were not reflecting the exact data. The inconsistency observed with embedded reports was due to grids being sourced by virtual RD, for which the report page had already been loaded elsewhere. In this case it was assumed that the statistics were already populated because the report page was already loaded. To ensure that reports are consistently accurate, pxRetrieveReportData has been updated to always call pzPopulateStatisticsInfo.

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