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-117847 · Issue 172996

Handling enhanced for custom system names

Resolved in Pega Version 7.1.7

If the system.name property in setupDatabase.properties was updated to reflect a custom System Name during ruleset migration, the value was not being used by the software update process and the resulting error caused a batch failure. There was a workaround of explicitly setting the system name in the field env name="Identification/SystemName" value=, but this has been updated to fetch the name from the db. In addition, the query that fetches the system name has been modified with a check to make sure that there is at least one requestor for the name it fetches.

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-117923 · Issue 171578

Remedied spurious size alert from the attachments viewer

Resolved in Pega Version 7.1.7

When listing attachments from History & Attachment display, the work object was re-read for each attachment. If the work object had many attachments, the alert "PEGA0004 alert (50MB DB threshold)" would appear regardless of the actual attachments' size. This has been adjusted so the RUF attachment access makes use of the existing WorkPage instead of re-reading it from the database.

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-117999 · Issue 177374

Tabbed display validation error resolved for DB2 z/OS

Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7

When running in 'tabbed' mode using DB2 on z/OS, it was not possible to select 'ACTIONS' nor 'WRAP UP' the call. This was due to the Rule html fragment UserWorkForm being taken from Pega-UInternet Explorer ngine instead of from the local application after validation failed following improper execution of an complex query. Further analysis found that the query was looking for records in list (0,2). As the DB setting of in this error situation was Decimal=comma, it was not taken as list but as single value 0,2 (a decimal value). This has been mitigated by adding a space before the '2' so that it will taken back as a list.

SR-118016 · Issue 174520

Spellcheck on text area fixed for IE8

Resolved in Pega Version 7.1.7

Using IE8, a text area with SpellCheck enabled generates the error "Script Error: Message: 'null' is null or not an object" if there is more than one line present. This was caused by the handling of the check for list length, and has been modified to work with all browsers.

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-118053 · Issue 172515

Added edit format for Designer Studio integer control in read-only when

Resolved in Pega Version 7.1.7

In the Integer Control for Designer Studio, it is not possible to set properties on the Edit Format when the presentation is ReadOnly based on a when rule. Both the Formats appear when the Edit Options is selected as Auto. Options have now been added to set the properties.

SR-118061 · Issue 175102

CorrNew activity can send email in sync or batch

Resolved in Pega Version 7.1.7

When attempting to send email correspondence in synchronous mode i.e. not via the agent processing, the activity always queued it to the agent even when the Activity CorrNew SendNow param was set to true. To correct this, the system will pass the value of a BatchSend param based on the value of the SendNow param: email will be sent immediately If SendNow is set to 'yes', or will be queued for batch processing if SendNow is set to 'no'.

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