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-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.

SR-118036 · Issue 171165

Corrected column width auto expand issues in decision table

Resolved in Pega Version 7.1.7

Decision tables which have many columns (8+) will expand the width very wide automatically by just clicking on the resize cursor (no dragging is necessary). However, trying to resize it back to a more reasonable width caused it to keep getting wider and wider due to an error with the dynamic display logic. This has been fixed.

SR-118125 · Issue 171188

Circumstance property value carried into dropdown options

Resolved in Pega Version 7.1.7

If a property of mode single value and type text was created with a defined local list of property values for the property, the value field was not automatically included in the dropdown options when attempting to use this property for circumstance/specialized flows. This was caused by an incorrect refresh section strategy used to determine when to reload the section for the circumstance by property, and has been corrected.

SR-118259 · Issue 173287

LookupList opened to unauthenticated requests

Resolved in Pega Version 7.1.7

When a list lookup was called from an unauthenticated service, it failed due to the lack of required authentication. The activity RULE-CIRCUMSTANCE-DEFINITION LOOKUPLIST has been modified to allow its execution by an unauthenticated requestor.

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