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- · Issue 404593

Thread name implementation fixed for FCM use with micro DC

Resolved in Pega Version 8.1.1

When attempting to invoke a remote case in the Interaction Manager portal via FCM with the Customer Service for Insurance application which uses micro DC, the case was not invoked and an empty screen was displayed. Invoking the case from the interaction portal resulted in a JavaScript error. Invoking the case from a WSS or directly from the Create button in Designer Studio worked correctly. This was traced to a recent change to the implementation for generating the thread name. Because of this, CRM apps could not load the Federated cases via micro DC. This has been fixed through changes in "pzFCMMashupGadget" to replace the slash with underscore for the FCM thread.

SR- · Issue 406436

OIDC and authorization_code flow corrected

Resolved in Pega Version 8.1.1

The OIDC and authorization_code flow was not working work on the first attempt. This was traced to the server that was performing the OAuth 2.0 authorization_code redirecting straight to the Pega application after successful user authentication instead of returning an authorization code via redirect_uri. As a result, the Pega application was rendered in a external Safari window which is supposed to be used for user authentication only. Second and subsequent attempts to perform the OAuth 2.0 authorization_code flow were successful and the Mobile Client was logged in. This was caused by the unnecessary retainment of state parameters in the OIDC flow, and has been fixed by removing the code that appended the querystring parameters used for the Hybrid Client.

SR- · Issue 402877

Merge Wizard errors fixed, and created rules will use the highest ruleset version available

Resolved in Pega Version 8.1.1

Code errors in the Merge Wizard that were causing Null Pointer Exception errors have been fixed, In addition, branch rule sets created through this wizard did not have the 'Application validation' option and rule set pre-requisite filled automatically; the system has been updated so the version prerequisite will be the highest existing ruleset version in the ruleset.

SR-111928 · Issue 183474

Assignment locking smoothed for slow network async requests

Resolved in Pega Version 7.1.8

In situations with slow network async Ajax requests, locking was not being properly released between requests. This caused an issue with sub-flows that had a Spinoff Flow configured to route the assignments in the sub-process and the main process to separate operators. In order to resolve this, the close tab process has been updated to remove the corresponding thread and release the lock.

SR-114819 · Issue 175544

Localization added for currency values using commas vs decimal points

Resolved in Pega Version 7.1.8

Excel within PRPC was not properly localizing for the use of decimal and comma as thousand and decimal separators for decimal/double currency property values, a use that is common in non-English installations. The records editor has been changed to support localization for properties of type double and decimal.

SR-114875 · Issue 171313

Enhanced error handling for WebSphere class conflicts

Resolved in Pega Version 7.1.8

An error caused by a class conflict issue in WebSphere was being generated when exporting Process Flow as XPDL. In order to clarify the limitations in this use, changes have been made to the XSLTRANSLATE Activity to add an extra catch that handles any style sheet errors explicitly and provides an informative error message.

SR-115208 · Issue 178808

Assignment locking smoothed for slow network async requests

Resolved in Pega Version 7.1.8

In situations with slow network async Ajax requests, locking was not being properly released between requests. This caused an issue with sub-flows that had a Spinoff Flow configured to route the assignments in the sub-process and the main process to separate operators. In order to resolve this, the close tab process has been updated to remove the corresponding thread and release the lock.

SR-115208 · Issue 183474

Assignment locking smoothed for slow network async requests

Resolved in Pega Version 7.1.8

In situations with slow network async Ajax requests, locking was not being properly released between requests. This caused an issue with sub-flows that had a Spinoff Flow configured to route the assignments in the sub-process and the main process to separate operators. In order to resolve this, the close tab process has been updated to remove the corresponding thread and release the lock.

SR-115365 · Issue 173851

New 'Break Long Word' sub-setting added to 'Wrap Text'

Resolved in Pega Version 7.1.8

When lengthy text was present inside the cell of a grid configured as a fixed size / fixed header grid, misalignment between column header and row cells was seen. This was an issue with the text display. The word-wrap property earlier was set to break-word to enable wrapping of long words to multiple lines, but this was not working as expected for values that do not have a whitespace/break. To resolve this, when the 'Wrap text option' is clicked, the new configuration option 'Break long word' will be available to allow line breaks between letters.

SR-115408 · Issue 153195

Corrected rendering of complex embedded dynamic layouts

Resolved in Pega Version 7.1.8

Embedded Dynamic Layouts with defer load configuration enabled were not rendering sections correctly. If one dynamic layout contained two dynamic layouts embedded in it and both dynamic layouts contained separate sections referred in them (collapsed), the section in the first dynamic layout was rendered in both dynamic layouts.

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