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-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-117228 · Issue 168249

Resolved issues with Flow shapes distributed across Swim Lanes

Resolved in Pega Version 7.1.7

Pool size is maintained as both pixels and inches, but auto conversion was failing if the pool dimension was very large. This created an error where saving a flow rule could cause the pool to drastically shrink (for example, 20 inches becoming 20 pixels). In order to maintain the proper dimensions, a check has been added for pool and swimlane to ensure the proper inch/pixel conversions.

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.

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.

SR-117921 · Issue 174204

Warning message displays for ruleset save in lower version

Resolved in Pega Version 7.1.7

If a developer tried to save a rule in lower ruleset version while the same rule is already in a higher ruleset version, this was allowed with no warning. This behavior has been corrected.

SR-117961 · Issue 174233

Datetime conversion smoothed for SQL queries

Resolved in Pega Version 7.1.7

If the date time format on an SQL Server 2008 instance is set to ydm, a datetime conversion error was created due to the PRPC query using ymd format. In order to support all date formats for SQLServer, Timestamp is now formatted as "yyyyMMdd HH:mm:ss:SSS".

SR-118029 · Issue 173069

BIX filtering corrected

Resolved in Pega Version 7.1.7

Bix filters were not working consistently due to a missing call in the logic handling the ruleset references, and are now working correctly.

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