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-B39484 · Issue 296141

Calculation Builder made more robust for use in segments

Resolved in Pega Version 7.3

An error was generated when using the Calculation Builder in a segment, though the Calculation Builder for Report Definition worked. This was traced to code in the Calculation Builder which assumed the report page class would always be "Rule-Obj-Report-Definition", which failed for segments. To correct this, the logic has been modified to be more robust.

SR-B39489 · Issue 295922

KeyStoreType of PKCS12 passes validation

Resolved in Pega Version 7.3

Keystore has an allowed file type of PKCS12, but an invalid type error was generated when trying to create a keystore file of this type. This has been corrected.

SR-B39489 · Issue 290738

KeyStoreType of PKCS12 passes validation

Resolved in Pega Version 7.3

Keystore has an allowed file type of PKCS12, but an invalid type error was generated when trying to create a keystore file of this type. This has been corrected.

SR-B39528 · Issue 303927

Node startup modified to support very large clusters

Resolved in Pega Version 7.3

Node startup was failing if the cluster had more than 50 nodes. This issue was caused by the query to the "pr_sys_statusnodes" table only returning 50 records; this limitation has been removed.

SR-B39528 · Issue 303228

Node startup modified to support very large clusters

Resolved in Pega Version 7.3

Node startup was failing if the cluster had more than 50 nodes. This issue was caused by the query to the "pr_sys_statusnodes" table only returning 50 records; this limitation has been removed.

SR-B39558 · Issue 297151

Logic added to convert UTC Date for REST clipboard mapping

Resolved in Pega Version 7.3

An error was generated while mapping UTC format Date fields to the clipboard in REST. This was traced to the DateTime properties in the JSON response not being converted to Pega-supported datetime format, and the necessary parsing logic has been added.

SR-B39673 · Issue 297670

Fixed grid row editing for Remote List

Resolved in Pega Version 7.3

When trying to create a property with table type as Remote List, it was not possible to edit or add the rows. This was due to the grid using the row editing option 'None' when the grid row-editing property has been changed to 'inline', and the table editing has been changed to inline.

SR-B39730 · Issue 301187

tempItem parameter added to createworkprocess API

Resolved in Pega Version 7.3

The parameter tempItem has been added to the createWorkProcess API to hold a temporary work object which is passed to AddWork activity. The same naming convention is used.

SR-B39792 · Issue 298418

Validation removed for survey name property

Resolved in Pega Version 7.3

If the survey driver parameter "survey" was configured with a property reference to provide the survey name in the subprocess SurveyDriver, adding validations to it caused the property panel to generate an error. This was due to Validations on the pySurvey property checking if the survey existed with the configuration. To avoid this, validations on the pySurvey property have been removed and an added required condition has been put on the pySurvey

SR-B3980 · Issue 273916

Scrollbar added for Microsoft Internet Explorer 11 window sizing overflow

Resolved in Pega Version 7.3

In Microsoft Internet Explorer 11, reducing the screen width caused grid data to overflow onto the tree navigation menu. This has been resolved with the addition of scrollbars to the Action area to handle overflowing content.

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