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.

INC-147873 · Issue 610865

Custom header character encoding for Subject added

Resolved in Pega Version 8.5.5

Case correspondence that contained a Subject with accent characters such as "Invitation à être" was being rejected by MailJet on the basis of encoding issues on the "Thread-Topic" when using custom headers. The error "BAD HEADER SECTION, Non-encoded non-ASCII data (and not UTF-8)" was generated. This was traced to the Send Email Smart Shape handling when using custom headers, and has been resolved by encoding the Subject before appending it to the Thread-topic header while adding custom headers.

SR-C93292 · Issue 432662

Inline error messages linked to input for accessibility

Resolved in Pega Version 8.2.3

In order to support accessibility for server side inline messages, the controls have been mapped to the error message div and an aria-describedby attribute has been added for the same. This allows JAWS to read the error message specific to the control where the error occurs.

SR-D20763 · Issue 500406

DASS added to allow toggle of indexpurpose filter in declare index join

Resolved in Pega Version 8.2.3

A performance issue was seen when using a declare index join to add a pxIndexPurpose filter to a very large index_workparty table, either taking a long time to process a search request or intermittently timing out. This was traced to recent modifications in the DeclareIndex Join filter conditions to better handle multiple declare index rules pointing to the same index table, As a result, doing a declare index join on one of the declare indexes returned results that included those that corresponded to other declare index rules. To resolve this, a DASS has been provided to toggle the inclusion of the indexpurpose filter in a declare index join to allow for better customization.

INC-161645 · Issue 634639

Java Bean import updated to handling differences in Java 7 and Java 8

Resolved in Pega Version 8.5.5

The behavior of the java bean Introspector class is inconsistent across different versions of the JDK when detecting indexed properties built off of java.util.List objects, causing Java Bean import to generate differently in Java 7 and Java 8. This has been resolved by updating PRIndexedPropertyDescriptor to better handle this JDK difference by resolving indexed read and write methods manually using simple reflection.

INC-163292 · Issue 635839

Portlet service deprecated

Resolved in Pega Version 8.5.5

Portlet authentication services have been removed from the standard installation package. The IAC service has been restored.

SR-D17825 · Issue 494701

PreSaveAs updated to set the correct ruleset value when saved into a different ruleset

Resolved in Pega Version 8.2.3

When using a BIX Extract rule already configured with properties and filter criteria, attempting to update the filter criteria system resulted in an "invalid property error" and inability to save the updated rule. This was traced to the extract rule being created from another extract rule with 'save as', resulting in the new extract existing in a different ruleset. Because the pxBixReportPage.pyRuleset had the value of the original ruleset instead of rule set in which it had been saved, the system was attempting to find the filter properties in the original ruleset. To resolve this, the Presaveas activity in rule-admin-extract has been modified to check and set the correct value when both the rulesets are not equal.

SR-D18038 · Issue 489532

Corrected grid column header misalignment

Resolved in Pega Version 8.2.3

After upgrade, a grid's first column heading was misaligned when using the IE browser. This was traced to Quirks mode related CSS not being removed after support for Quirks mode ended, and has been corrected.

SR-C94644 · Issue 485244

Date Filter corrected for Optimized table layout

Resolved in Pega Version 8.2.3

The Date Filter was showing incorrect results when 'next month/current month' range filter was applied on the 31st of the month and the Allow Optimize code check box was enabled in the table layout properties. This was traced to the pySymbolicStartDate and pySymbolicEndDate properties values not being properly populated with time, and has been corrected.

SR-D11312 · Issue 484683

CKEditor table-related plugins updated

Resolved in Pega Version 8.2.3

In order to successfully put a copy of previous correspondence below the auto email template, gaps had to be explicitly left below the auto email template before pasting the previous email correspondence. Otherwise the auto template disappeared and left only the previous email correspondence on the auto template. This was traced to issues with the CKEditor plugins, and has been resolved by updating to the latest table plugins from CKEditor (table,tabletools,showborders,tableresize,tableselection).

SR-D16624 · Issue 490927

Table layout filter popover position corrected for Pega mashup

Resolved in Pega Version 8.2.3

When using an exposed harness with table layout using Pega web mash up, the mash up worked but the apply and cancel buttons were not visible when any column was clicked to filter the result. This was traced to the filter popup having a hardcoded position offset set in its div element, and has been resolved by delegating the responsibility of the filter popover height calculation to the popover.

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