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-B11141 · Issue 282453

PageList property popup fixed in Report Editor

Resolved in Pega Version 7.3

When adding a PageList property to a report in the Report Editor, the resulting popup was empty. This was caused by a missing layout in the section used to display the index of the pagelist, and has been fixed.

SR-B11201 · Issue 281026

Downcasing added to ensure skin-defined templates are applied as expected

Resolved in Pega Version 7.3

When using a customized modal template and modal format defined in the application skin, the UI reflected the section modal template but not the skin template. This was traced to the CSS not being applied due to skin rule custom format names being case sensitive. To resolve this, code has been added to downcase the name when generating style for the modal.

SR-B11271 · Issue 281717

Assignment Gadget hang resolved

Resolved in Pega Version 7.3

The Open Assignment Gadget was hanging when loading assignments in perform harness, preventing completion of the assignment. This was due to a missing null check for dataRow in the setHeadersWidth API for grid generation, and has been fixed.

SR-B1132 · Issue 274302

SOAP simulations restored

Resolved in Pega Version 7.3

SOAP simulations were not executed as expected due to the hard coded value SOAP being removed and made generic. This has been fixed by updating the service type to SOAP in the parameters passed to the simulations section.

SR-B11441 · Issue 280633

Connect-SOAP jar recompiled with JDK 1.7 for greater compatibility

Resolved in Pega Version 7.3

After upgrade, an error was generated by Connect-SOAP calls on systems using JDK 1.7. This was caused by the Pega jar having been compiled with JDK 1.8, which lacks backwards compatibility. To resolve this, the jar has been recompiled using JDK 1.7 as it has forward compatibility and will work with the higher version.

SR-B11600 · Issue 282715

Handling added for dot in visible-when rule

Resolved in Pega Version 7.3

On click of the icon next to the visible-when rule in order to open the rule, the error "Unable to open the rule as Base Class Value is empty" was generated if the 'when' rule of the conditions included a dot. To correct this, the pega_openRuleSP logic has been modified to fall back to the section class from the PRXML when the value of baseClassValue is empty.

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-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.

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