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-B11675 · Issue 284417

Cursor correctly changes to hand in Report Wizard popup

Resolved in Pega Version 7.3

The hand icon was not displaying as expected when the cursor was placed on the Search icon in the "Report Wizard" pop up window. This has been fixed.

SR-B11741 · Issue 285895

Tenant ID check added to Ruleset Wizard for MT

Resolved in Pega Version 7.3

Attempting to deleting a ruleset in a multi-tenant environment using the Ruleset Wizard resulted in the error message 'Getting records from the database' and the application would hang. This was due to a missing tenant ID in the SQL statement, and a check has been added to the query generation to ensure the prepared values for "pzTenantID" are included.

SR-B11776 · Issue 289458

Report results populating as expected for tree grid

Resolved in Pega Version 7.3

Report definition results were not populated in the tree grid structure but were populated in the spread sheet structure. This was caused by a difference in handling for formatting a column with empty values, and has been changed.

SR-B11796 · Issue 281383

Column filters updated to escape values with angle brackets

Resolved in Pega Version 7.3

When attempting to apply a filter on a Repeat Grid or Report Definition column, the filter popup showed blank values for column values starting with the "" character. This was due to the browser treating "" as an HTML tag, and the pzGetGridColUniqueValues function has been updated to escape these values.

SR-B11800 · Issue 283413

Stage wide User Actions are consistent on section expand

Resolved in Pega Version 7.3

Stage wide User Actions were different on nested grid sections when the work bound grid was expanded. This has been resolved with an added check to see if the target element is inside a modal dialog.

SR-B11802 · Issue 285155

Fixed work object submitting with incorrect hidden datetime

Resolved in Pega Version 7.3

When a date field was configured with a validation to check if the date is in the future, the work object was getting submitted even if the validation failed and error messages existed on the clipboard. This was a missed use case in the resetDateTimeHidden function which clears the value from a hidden field if there is an error in the field, and has been fixed.

SR-B11927 · Issue 280995

pyContentType column populated in recents table

Resolved in Pega Version 7.3

After upgrade, the new column "pyContentType" was visible in the pr_data_recents table, but data was not getting populated into this column when work objects or rules were opened. This was due to the recents tab missing the pyContentType column query from the custom population queries, and this has now been added.

SR-B11988 · Issue 284340

Fixed pagination exception for grid with pagegroup property

Resolved in Pega Version 7.3

An invalid reference exception was generated while navigating to the second page of a grid sourced with a pagegroup property. This was an error with the preActivityParams being encoded twice, causing characters to be corrupted. The string query has been updated to resolve this problem.

SR-B12026 · Issue 283561

Overridden data flow with RD partitioned key fixed

Resolved in Pega Version 7.3

A validation error was thrown and data flow activation failed for an overridden data flow with a RD partitioned key. This was traced to the circumstanced pzValidateRuleExistance (triggered when the dataflow shape was overridden) trying to open the property rule with pyPurpose set to rule name whereas the actual property should have been pyPropertyName. This has been fixed.

SR-B12207 · Issue 285722

Corrected Org text field handling for templated mobile sections

Resolved in Pega Version 7.3

Given a section pyWorkSummary_Mobile with a text input field called Organization, the organization name was shown correctly in the Declare_crmOrg page but on the UI it was displaying 'Org Not Found'. This was caused by recent section template changes that caused the object to be rendered on the wrong thread, and 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