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-B3943 · Issue 279666

NewCorrSummary rule resolution modified for CommunicationType

Resolved in Pega Version 7.3

The Received Via section of the out-of-the-box NewCorrSummary rule was being mapped to the property rule CommunicationType despite that property rule being configured locally. This has been fixed by setting the function to take the class name using dictionary instead of section xml.

SR-B39458 · Issue 299698

Email Listener checks for engine startup before queue processing

Resolved in Pega Version 7.3

Items in an Email Listener queue were not processed upon server restart and an null-pointer exception was generated. This was due to the Email Listener beginning work too quickly, and has been fixed by modifying the Email Listener code to check whether the engine has started or not before beginning processing.

SR-B39476 · Issue 297525

addCalendar() RUF logic updated

Resolved in Pega Version 7.3

The addCalendar() RUF logic has been modified to correctly set the operator time zone and correctly add the given years, months, days etc. This fix will be active based on a DASS setting as addCalendar() cannot be directly changed due to backward compatibility with DateTime issues.

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.

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