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-125210 · Issue 189127

Customization corrected for RRHeader section of RD

Resolved in Pega Version 7.1.8

If the RRHeader section item was customized and renamed, opening Report Definition and clicking "Edit Report Title" did not produce the expected results even with the "Edit Report Title" command enabled. This was due to the RRHeader section being hard-coded; this is now loaded dynamically to allow for customization.

SR-125245 · Issue 187386

Search ability corrected for rule names containing spaces

Resolved in Pega Version 7.1.8

While a space was allowed in the rule name of a report category rule, searching for a rule name with a space generated the error "Unable to open instance Error: Can't find record". This was due to a missing JavaIdentifier validator for the "pyCategoryName" property in "Rule-Category" class, and this has been added.

SR-125520 · Issue 194874

Open Authoring OCX and other certificates renewed

Resolved in Pega Version 7.1.8

In order to ensure ActiveX and other helper programs continue to work properly, the components have been re-signed with a digital certificate expiring 12-Mar-2018.

SR-125610 · Issue 189352

Added handling for property-defined declare value list indexing

Resolved in Pega Version 7.1.8

When adding or updating entries in a value list, the corresponding index entries were not getting created in the database. This was caused by handling that was missing from the minimum feature string clipboard properties that were recently introduced for better performance. These strings get created when it's not a reference property and has no declaratives defined etc. In this case, a declare index that is defined on the value list property should not have those elements be minimum feature properties. To correct this, the code has been changed to pass the featureID of the parent property.

SR-125751 · Issue 194311

Updated scroll bar generation for rule forms

Resolved in Pega Version 7.1.8

Calling WBOpen in a list view on click event allows a pop up to show. For rule or data instances which have forms bigger than the pop up size, no scrollbar was shown. This was caused by the previous ruleset regulating the scrollbar, RuleFormFrameset, being marked as deprecated but not removed from the function. To replace this rule, Window.open Attributes resizable and scrollbars have been set to true.

SR-125910 · Issue 194305

Corrected data population in report for exposed column

Resolved in Pega Version 7.1.8

Data was not being populated in a report for an exposed column when it was dragged and dropped from the data explorer of Report Editor. This was caused by the CreateColumnPage fieldName being hard-coded to Param.FieldName for embedded page properties, and has been changed to set FieldName conditionally.

SR-126011 · Issue 195418

RUF 'hasMessages' working with Declarative Pages

Resolved in Pega Version 7.1.8

Attempting to execute a Declarative Page with the RUF 'hasMessages' as a precondition caused a NPE. The error was caused by a null page call, and has been corrected by adding a null check for pageVarName and adding a find page call.

SR-126011 · Issue 195591

RUF 'hasMessages' working with Declarative Pages

Resolved in Pega Version 7.1.8

Attempting to execute a Declarative Page with the RUF 'hasMessages' as a precondition caused a NPE. The error was caused by a null page call, and has been corrected by adding a null check for pageVarName and adding a find page call.

SR-126092 · Issue 189635

Enhanced logging for SQL exceptions with BIX

Resolved in Pega Version 7.1.8

In order to enhance diagnostics while using BIX, logging has been added to print the stack trace for an SQL Exception while fetching the last updatedatetime.

SR-126335 · Issue 192177

Added support for custom mixed property types for listview filter

Resolved in Pega Version 7.1.8

When the out-of-the-box listview pySearchResultsWork was modified to add two columns with one property having Datetime control and the other having Date Control, the data was retrieved but the filter criteria was not working. This issue was specific to Date/Datetime control, and was traced to missing configurations for this scenario. Those have been added.

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