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-144358 · Issue 601012

Localization added for "Automatically" and "Manually" field values

Resolved in Pega Version 8.5.2

The Dutch translation of "Child case [Case_type] [Case_id] has been [Instantiation_mode] instantiated" used the hard-coded English expression "manually". This has been resolved by adding the "Automatically" and "Manually" field values to localization.

INC-136634 · Issue 591678

Thread contention resolved for InteractionHistoryQuery

Resolved in Pega Version 8.5.2

High thread contention was observed while running Inbound load tests. This was traced to pzLoadInteractionHistory invoking a generated strategy to retrieve ihFields from InteractionHistoryQuery using the getUsedInteractionHistoryFields() method: because this method is synchronized, it caused a bottleneck. To resolve this, the synchronized methods have been replaced with the appropriate data structures.

SR-C53759 · Issue 404974

Corrected revalidate and save of Service REST rule after upgrade

Resolved in Pega Version 8.1.2

After upgrade, opening an existing Service REST rule and trying to save it in a higher ruleset using the revalidate and save tool resulted in the error "pyResourcePathParams.pyParameterName : This field should not be blank". This was caused by the Service REST xml not getting updated and has been corrected by adding UpgradeOnOpen to the process.

INC-139645 · Issue 597500

Flowaction button responds for grid modal window

Resolved in Pega Version 8.5.2

The submit and cancel buttons were not working on first click for a modal window opened from a grid. Investigation found that this happened when the grid was shown on launching a harness but not if the grid was set to show otherwise in tabs, and was not seen when launching modal windows normally either from tabs or from harness (the pzModalTemplate or pyModalTemplate). This was traced to the system passing the target as a window to getTrackerChanges from triggerEvaluateClientConditions, which caused getTrackerChanges to be called on every window action. To resolve this, the event has been changed to 'focus' so that the method gets called only on focus.

SR-113624 · Issue 167070

Enabling out-of-the-box Security Policies now redirects immediately

Resolved in Pega Version 7.1.7

When enabling out-of-the-box Security Policies, it was not immediately redirecting to the change password screen but instead requiring the timeout interval to expire before redirect happened. This has been corrected.

SR-114353 · Issue 166997

System scanner performance enhanced

Resolved in Pega Version 7.1.7

When working with a large number of hotfixes, the system scanner can become very slow. Performance enhancements have been incorporated to increase speed by changing how ID and key comparisons are performed.

SR-117158 · Issue 169361

Corrected inclusion of "Other Specifications" in Document Wizard

Resolved in Pega Version 7.1.7

The 'Other Specifications' section of the application doc was being included regardless of whether the checkbox was selected in step 4 of the Document Wizard. This has been corrected to ensure 'Other Specifications' are documented only when they are selected.

SR-111889 · Issue 157259

Some SOAP calls with WSTRUST generated exceptions in customized environments

Resolved in Pega Version 7.1.7

In some heavily customized environments, a SOAP connect call using the WSTRUST element generated an exception. This was due to uneven handling of the local custom elements in the SOAP STS request, and has been resolved by adding a method to pick up all custom code based on the tag in policy document.

INC-145263 · Issue 600036

Query logic modified for Anypicker

Resolved in Pega Version 8.5.2

A search for results in the Anypicker control for the first time showed the results, but if the results were deleted and the search run again without focusing out from that field, no results were found for the second search. This has been resolved by using slice than splice in the query to avoid mutating the original array source.

SR-117840 · Issue 170516

Autopopulate correctly set/disabled in the CSR portal

Resolved in Pega Version 7.1.7

Switching to some clipboard pages caused a null pointer error in the CSR portal for the operator. This was caused by an autopopulate call being made even when autopopulate was disabled. This has been corrected.

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