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-116157 · Issue 165994

Improved crash recovery in a complex system

Resolved in Pega Version 7.1.7

During crash recovery in a clustered, load balanced system, attempting to recover a user's progress displayed a message that the session was recovered but the page did not then properly load the recovered data. To ensure proper crash recovery failover on complex systems, the user is now authenticated on the STANDARD thread instead of a work thread when restoring work in progress.

SR-116556 · Issue 170813

AllLinksForParticularRule changed from Final to Available

Resolved in Pega Version 7.1.7

The list view reporting limit AllLinksForParticularRule has been changed from a Final rule to an Available rule in order to allow an increase in the number of links shown in the Application Profile. The default is 500.

SR-116585 · Issue 167063

Screen flow previous button repaired in obfuscated IAC

Resolved in Pega Version 7.1.7

When using IAC with obfuscation is enabled, the screen flow 'previous' button was not responding. This was caused by the '\' at the end of the URL parameter being accidentally obfuscated as well, and has been fixed.

SR-116681 · Issue 169378

BIX Column length increased

Resolved in Pega Version 7.1.7

At runtime BIX checks the target DB metadata for column length. If it could not find the metadata with schema associated with the BIX DB user, it was setting the length at 32 characters even if a larger column length was specified in PRPC and SQL. This was due to a mismatch in the stored value location, and has been corrected so BIX will reflect the length specified on the Extract rule form.

SR-116716 · Issue 167507

Execute RDB runs in batch mode for very large data sets

Resolved in Pega Version 7.1.7

The executeRDB query was not able to handle very large large data sets, resulting in an OOM error after clicking on "Create Prior Authorization". ExecuteRDB (which is a select query) has been modified to run in batched mode, i.e. run the same query with limit on max rows, so as to avoid OOM when copying the whole result set into the memory object (similar to Report Definition paging).

SR-117039 · Issue 169671

Standardized class display options for App Explorer

Resolved in Pega Version 7.1.7

Inconsistencies had appeared in how Application Explorer handled switching the display between name and label (short description) in the class hierarchy display. The App Explorer menu now shows the option to toggle between Class labels and Rule names, with a default setting of displaying Rule names. In addition, the short description display will not include the rule purpose.

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-117391 · Issue 170006

Export to Excel replaces embedded control characters in APW

Resolved in Pega Version 7.1.7

In Application Profile Wizard, attempting to Export to Excel would fail if any specifications text contained an embedded control character (such as might appear after cutting and pasting from a Word or text file). To prevent the exporting failure, any control characters introduced into the generated data are now replaced with spaces during the export process.

SR-117461 · Issue 169210

Delete All Links' button disabled if rule is read-only

Resolved in Pega Version 7.1.7

When an Application Requirement rule is read-only due to being in a locked ruleset etc., the Delete All Links button was offered as an option. In order to avoid confusion, the Delete All Links button is now readonly when the rule is not editable.

SR-117604 · Issue 169493

Increased limit for Application Document flows

Resolved in Pega Version 7.1.7

Application Document previously limited the number of flows to 50 and would not list those exceeding the limit. This limit has been removed.

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