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.

INC-219627 · Issue 715995

InvokeHTTPConnector security updated

Resolved in Pega Version 8.8

"Allow invocation from browser" has been disabled for InvokeHTTPConnector, and "Require authentication to run" has been enabled. In addition, an unsafe reflection used to load JCIFS libraries for NTLM operations has been removed, which removes support for custom JCIFS libraries in Connect HTTP.

INC-211349 · Issue 709607

Service API called directly in CDH simulation

Resolved in Pega Version 8.8

Running a simulation from the Customer Decision Hub with strategy and dataflow that used customer data resulted in with either a failed run or blank explain detail reports. Investigation showed synchronization was not triggered due to the pxVBDAvailable call returning false, and this has been resolved by directly calling the service API without additional checks.

INC-211480 · Issue 712420

Handling added updates involving Oracle descending column

Resolved in Pega Version 8.8

The build was failing when attempting to update to Pega 8.6, and an error indicating an issue with Oracle columns was generated. Investigation showed that when a column changed that belonged to an index which had a 'desc' column (even if the changed column was not specified as desc), an Oracle restriction was triggered. This occurred with any column size increase if the column participated in an index containing a descending column or a function index. This has been resolved by adding a step to drop the index before altering the column if a Descending index is involved, and to catch the case where the resized index is part of an index that has a descending column but is not necessarily a descending column itself.

INC-231721 · Issue 741742

Dataview API correctly returns value for embedded fields

Resolved in Pega Version 8.8

n QueryableDataViewTransformer, pxObjClass is populated when the payload has no embedded fields and special processing is not required. Because of pxObjClass being present, the values are parsed as per the property type and correctly populated on the clipboard and a boolean is generated correctly in the response. However, when the payload has embedded fields and special processing is required, the response body was not populated with pxObjClass and hence all fields on the clipboard were treated as strings and the data view API responded with the values in as a string irrespective of type. To resolve this, page properties have been enabled in the aggregation validator and the transformer in QueryableDataViewTransformer.java has been refactored to link the property definition.

INC-213189 · Issue 707343

Addressed performance issues for classless DSMClipboardPage

Resolved in Pega Version 8.8

The DSMClipboardPage implementation handles Page Group access as a classless page (i.e. pxObjClass = ""), creating potential performance issues in implementations where the page group is used with a very large number of distinct AccountIDs in a short period. This has been resolved by updating the system to not cache keys for page group classless page.

SR-D80798 · Issue 545241

Updated attachment popover handling for IE

Resolved in Pega Version 8.1.8

After configuring a button consisting of two events, 1. On click --> View Attachment and 2. Hover --> Show Smart info, an attachment popup opened whenever the button was clicked, and moving the cursor out minimized the attachment. To resolve this, dismiss callback logic has been added in popover close for use with IE.

INC-220293 · Issue 726323

Operator ID ruleform "Reporting To" supports large number of users

Resolved in Pega Version 8.8

In a site with more than 10,000 operators, the "Reporting To" field in the operator ID rule form did not display operators beyond 10,000. This has been resolved by updating the Reports To component to an autocomplete in the Data-Admin-OperatorID!pzRoutingSettings, which is using the new data page D_pzGetOperatorsAndFilterByID and report pzGetOperatorsAndFilterByID.

INC-202793 · Issue 698055

Corrected malformed URL

Resolved in Pega Version 8.8

The function used in the session timer to log off the user was not working consistently, and attempting to discard a checked-out delegated Rule did discard the rule. Both issues reported the error "HTTP Status 400 - Bad request". This was traced to a badly formed URL, and has been resolved by wrapping the URL with SafeURL_createFromURL.

INC-207785 · Issue 721085

Updated check for isPreGeneratedMashup

Resolved in Pega Version 8.8

After embedding Pega mashup from one application into another Pega application, attempting to use the 'Getgadgetdata' method to retrieve property values in the mashup resulted in an infinite loop in the javascript function. This was traced to the handling of encryption of isPreGeneratedMashup in this scenario, and has been resolved by passing the parameter separately to check whether it is pre-generated or not.

INC-210760 · Issue 708532

Corrected malformed URL

Resolved in Pega Version 8.8

The function used in the session timer to log off the user was not working consistently, and attempting to discard a checked-out delegated Rule did discard the rule. Both issues reported the error "HTTP Status 400 - Bad request". This was traced to a badly formed URL, and has been resolved by wrapping the URL with SafeURL_createFromURL.

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