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-A100292 · Issue 270065

Select Values from join properly displayed on chart

Resolved in Pega Version 7.3

In charts of report definitions using a join, properties with prompt select values were displaying the actual data rather than the prompt values. This was due to a handling difference for properties from joins: before rendering the chart, report data was copied to a page that did not have the correct pxObjClass, creating the assumption that the property applied to @baseclass. To resolve this, the class will be set on the page that contains the target property.

SR-A103079 · Issue 273545

Check added for RD date time values

Resolved in Pega Version 7.3

An exception was generated when running RD by choosing the relationship for a datetime property as "Is not null" in filter conditions before displaying the data. This has been fixed with the addition of a check for the date time value.

SR-A103203 · Issue 276928

SQL alias function getLastDayofYear repaired

Resolved in Pega Version 7.3

After upgrade, the SQL alias function getLastDayofYear generated an error. This was due to missing format conversion for the date value parameter, and has been corrected.

SR-A86522 · Issue 272062

Event Late triggers expanded

Resolved in Pega Version 7.3

If "Limit passed deadline events" was not set to any value and the enqueue item was still in defer-save and not committed to DB, 'Event Late' was not triggered. Code has been added to properly check and trigger the late notice based on this scenario.

SR-A86522 · Issue 272065

Event Late triggers expanded

Resolved in Pega Version 7.3

If "Limit passed deadline events" was not set to any value and the enqueue item was still in defer-save and not committed to DB, 'Event Late' was not triggered. Code has been added to properly check and trigger the late notice based on this scenario.

SR-A91979 · Issue 261380

referencePropertyLink will be directly copied if autopopulate disabled

Resolved in Pega Version 7.3

A run-time failure occurred due to a reference to an AP property failing to copy properly during objOpenByHandle. This was because autopopulation is disabled in objOpenByHandle, causing the source property to be returned as null when page-copy lost the reference information. To resolve this, when autopopulation is disabled the referencePropertyLink will be directly copied from the source page to the target page without trying to resolve the reference property's source.

SR-B10051 · Issue 279714

Agent management detail corrected to show all nodes

Resolved in Pega Version 7.3

Drilling down to the agent detail from the Agent management page was showing only the current node when agents from the other nodes should have been displayed as well. This was caused by an error in the DataAgentIndex function, and has been corrected.

SR-B10051 · Issue 279523

Agent Management updated for long NodeNames

Resolved in Pega Version 7.3

Drill down to the agent detail from the Agent management page was only showing the current node. This was traced to a failed join when a very long "pyNodeName" DB line was encountered in pr_index_data_agents, and has been fixed.

SR-B10051 · Issue 279523

Agent Management updated for long NodeNames

Resolved in Pega Version 7.3

Drill down to the agent detail from the Agent management page was only showing the current node. This was traced to a failed join when a very long "pyNodeName" DB line was encountered in pr_index_data_agents, and has been fixed.

SR-B10103 · Issue 279865

Improvements in Export to Excel of very large files

Resolved in Pega Version 7.3

When exporting a very large (6000+ row) decision table into Excel, the process was very slow and the lack of a progress or busy indicator created the impression that the system was not responding. To resolve the processing issue, the code has been optimized to create lesser style objects. A busy indicator will also be displayed until the file starts download to indicate the operation is in progress.

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