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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-C70602 · Issue 415503

Changed async loading when attaching Files with PegaCloudFileStorage to address 3rd party PEGA0046 error

Resolved in Pega Version 8.1.3

When using PegaCloudFileStorage, a PEGA046 alert was observed when attaching a file to a work object. This was a cosmetic issue that did not affect functionality, and was traced to the use of an external logging system that is not part of the standard system development for Pega. In order to remove this alert, Step-5 (Load-DataPage) of Data-WorkAttach-File.pzSaveToRepository activity has been removed as asynchronous loading of D_pxNewFile data page is not required.

SR-C74047 · Issue 416353

Automatic Cloud Terminations updated with retry logic and exception handling for nodes being disconnected while in use

Resolved in Pega Version 8.1.3

Agents were being disabled when a node was about to be shut down and the lock operation timed out. This was traced to an issue where the Hazelcast operation timed out trying to communicate with a node that had not yet dropped out of the cluster but did shortly after, and was due to the refactored code around delegating to a cluster component missing a lock method. In order to ensure the cluster component handles such exceptions gracefully, the lock operation now contains retry logic along with exception handling that will return 'false' instead of raising an exception.

SR-C82244 · Issue 421173

Enhancement made to allow passing of URL in actionset via the DX API

Resolved in Pega Version 8.2.1

When using the action "Open URL in Window" and the option "Use Alternate Domain" to pass a URL that is in saved in a property, the name of the property was passed when using the DX API instead of the URL. To allow this use, an enhancement has been added to support storing a last submitted value and a reference so that an action set with a property reference can return a reference object with lastSavedValue and the reference name attached.

SR-C82244 · Issue 421174

Enhancement made to allow passing of URL in actionset via the DX API

Resolved in Pega Version 8.1.3

When using the action "Open URL in Window" and the option "Use Alternate Domain" to pass a URL that is in saved in a property, the name of the property was passed when using the DX API instead of the URL. To allow this use, an enhancement has been added to support storing a last submitted value and a reference so that an action set with a property reference can return a reference object with lastSavedValue and the reference name attached.

SR-C71221 · Issue 427921

Radio buttons maintain arttributes after dynamic layout table reordering

Resolved in Pega Version 8.2.1

When using a table configured in a popup where each row of the table was rendered using a dynamic layout that included radio buttons within it, the radio button fields were being cleared when the rows of the table were reordered. This was caused by the radio buttons not having unique name values, and has been resolved by using the updatehandles function in the pega_ui_repeatlayout js file to set the checked attribute based on the selected value after the reorder.

SR-C77072 · Issue 415542

Title of Repeating Layout is passed correctly with ViewAPI

Resolved in Pega Version 8.1.3

When using a section with a repeating dynamic layout and a header (title) set with a property that had value, using the view API displayed a title which showed the property name instead of the value. To correct this, RDL has been updated to use a title and include support for text/property/fv and localization.

SR-C74054 · Issue 422025

Handling added for summary columns in Export to Excel

Resolved in Pega Version 8.2.1

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-C71043 · Issue 416762

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

Resolved in Pega Version 8.1.3

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-C77459 · Issue 416898

Report tab names are correctly maintained after refresh

Resolved in Pega Version 8.1.3

When multiple reports are opened and the browser is refreshed, the tab names/labels failed to show up on reload. This was caused by an error in the method used to set the tab label, and has been corrected.

SR-C71053 · Issue 413209

Added handling for defer-loaded dynamic layout inside a flowaction grid

Resolved in Pega Version 8.1.3

When using a grid configured to show the details in expandable rows and the inner grid was a work bound grid, trying to expand the rows only showed the "Loading ..." message and never completed. This was traced to a missing use case for having a defer-loaded Dynamic layout which wraps the grid inside a flowaction embeddedpane grid, and has been corrected.

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