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-A21043 · Issue 241137

Refresh list action retains focus on work area

Resolved in Pega Version 7.2.1

When used as used as part of enabling successive rows, the refresh list action was returning focus back to first item rather than holding focus at the working point. This was found to be caused by a ?Select first row on initial load? option when ?Refresh List? is performed, and this code will no longer be called in this scenario.

SR-A18716 · Issue 234856

Corrected Hotfix Manager mismatch between 7.2 versions

Resolved in Pega Version 7.2.1

The version of 7.2 used in the Hotfix Catalog was different from the version used in Hotfix Manager when installing DLs. An update to the HM code was made to correct this mismatch.

SR-A16535 · Issue 231740

Null Boolean and datetime properties passed in command line extraction

Resolved in Pega Version 7.2.1

If a Boolean or a datetime Embedded valuelist /valuegroup /pagelist/page group property was in the WO blob but has no value when extracted from the command line using the -B and -J options, the value in the extract was not valid. This was traced to the handling for empty Boolean and datetime properties, and these properties will now be passed without modification when using the command line options -B and -J in XML output format or when running the extract from the UI.

SR-A16904 · Issue 234334

Wrapper added to expression builder for the jump transition on a step

Resolved in Pega Version 7.2.1

While using expression builder, selecting the option for "Enable conditions after this action" in an activity and submitting the expression did not show the expected result in the When input box. Attempting to use the expression builder again and submitting it then resulted in the screen freezing and requiring a refresh. To resolve this, a "pyStepsTransSection" wrapper section was been added for the "pyStepsTransParamsWhen" when condition.

SR-A21931 · Issue 242711

XY chart Dashboard reports updated to handle empty data

Resolved in Pega Version 7.2.1

Dashboard reports were not loading when using RD as the source for XY charts if the data returned was completely empty. RUF: pzControl ? pzRuntimeFusionXYDataJSON has been updated to handle this missing use case.

SR-A21931 · Issue 233188

XY chart Dashboard reports updated to handle empty data

Resolved in Pega Version 7.2.1

Dashboard reports were not loading when using RD as the source for XY charts if the data returned was completely empty. RUF: pzControl ? pzRuntimeFusionXYDataJSON has been updated to handle this missing use case.

SR-A14168 · Issue 230039

Unique page names generated for nested child work items

Resolved in Pega Version 7.2.1

When multiple child work items were created using pxAddChildWork in one transaction, the same page name was getting used and causing errors. This has been fixed by making pagename unique by appending currentdatetime.

SR-C95253 · Issue 435788

Custom datetime controls correctly appended to Excel export

Resolved in Pega Version 8.1.5

The timezone was not being appended to datetime when exporting to Excel if a custom control was used. This has been corrected.

SR-A16566 · Issue 232088

TrackAction and TrackAchievement no longer require authentication to run

Resolved in Pega Version 7.2.1

When an unauthenticated client called an external service (Service-HTTP, SOAP, etc.) that upon completion uses an activity that uses Requestor-Stop instead of allowing the requestor to time out, an error was generated. This was due to the new rule PXTRACKACTION defaulting to 'Require authentication to run', a conflict when an unauthenticated service invokes this activity. The 'Require authentication to run' setting has been unchecked for the pxTrackAction and pxTrackAchievement activities.

SR-A17852 · Issue 234570

Edit Validate passes parameters to message rule

Resolved in Pega Version 7.2.1

When using an Edit Validate rule in the condition, functions could not be passed as a parameter into a message rule. This has been fixed.

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