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-D15895 · Issue 486592

Strict checking inserted to better handle DB keywords in string constant

Resolved in Pega Version 8.2.3

After upgrade, a report was failing with the message "Rule Alias Function cannot reference a SQL function that performs a subquery." This was traced to the report having a function alias used in the columns which compared two strings and returned another string (constant - static value) if the condition was met. However, in two of the returned string constants there was the word "select", which is a keyword in all database languages. Even though the word "select" was a referred part of a string constant, the system treated it as a keyword and tried to perform a subquery within the Function Alias because ABAC was enabled. The report only exhibited this behavior post-upgrade because while ABAC defaulted to disabled in previous versions, it was changed to default to being enabled beginning with v8.1. To resolve this and create more robust backwards compatibility, a more strict check for subquery validation will be performed when ABAC is enabled which will parse and check whether the RAF has the standard 'select from' clause syntax of SQL.

SR-D15910 · Issue 491006

AM/PM time setting corrected for Riyadh timezone

Resolved in Pega Version 8.2.3

When logged into the Pega mobile application with operator locale as ar_AR and timezone as Asia/Riyadh, selecting time as PM resulted in it being set to AM with Native control. If the native control was unchecked, a blank screen resulted. This has been corrected.

SR-D16074 · Issue 485880

Additional language options added to Language Wizard dropdown

Resolved in Pega Version 8.2.3

An enhancement has been added to the “select a language” dropdown in the Language Wizard that extends the available options to include Latin American Spanish (es_XL), Brazilian Portuguese (pt_BR), and Korean (ko_KR).

SR-D16221 · Issue 485531

Email replies fixed for cases addressed to CC or BCC address

Resolved in Pega Version 8.2.3

Using Customer Service, if a Customer included 3 email accounts in single email (one email in To, one in CC, and one in BCC) and all three accounts had the listener configured and running, the system created 3 cases accordingly (I-1, I-2 and I-3). However, when the CSR picked up the case and replied back on each Interaction case, the customer could receive emails only from the first case (the I-1 case which was created based on To address) and replies from the other cases created from the CC and BCC email addresses were not received. Investigation showed that the function populating the “From” email address for replies was only considering email addresses in the “To” recipient list of the original email and not the email addresses which were in the “CC” or “BCC” list. This has been corrected.

SR-D16433 · Issue 499295

Exception handling added for upgraded custom decision tables

Resolved in Pega Version 8.2.3

After upgrade, the status fail message "There has been an issue; please consult your system administrator" appeared with a blue screen in the Run window when attempting to run a Decision table from Actions-> Run option. This impacted the ability to create unit test cases. Analysis showed the issue occurred for any decision table where "Evaluate All rows" was enabled and list properties were used in Actions if there was no value for the list property after the execution of decision table. This was traced to a NullPointerException in a RunRuleFromPage activity in a customized in PUnit ruleset, and was caused by having list properties in the actions of a decision table that had not been populated during rule execution. Exception handling has been added to resolve this.

SR-D16934 · Issue 493703

External Cassandra nodes listed in DDS cluster

Resolved in Pega Version 8.2.3

Nodes of an external Cassandra cluster were not listed in the DDS cluster except for the first one in the host list, and when the “only” listed Cassandra node was restarted, the status on the DDS cluster LP did not become “NORMAL” afterwards. In addition, even though other C* nodes were up and running, the external Cassandra cluster was reported as unreachable. This was an unintended side effect of work done on the landing page to reflect the real state of the nodes after some were killed and restarted, and has been corrected by refining the equals() and hashCode() methods for DDS member info in order to better differentiate the external Cassandra nodes.

SR-D17306 · Issue 490917

RD pagination expanded to 1500 rows

Resolved in Pega Version 8.2.3

The default pagination enabled on the Report Definition was limiting the results to 50. This has been enhanced to a row limit of 1500 in report definitions pzGetAllPropertiesOfGivenClass.

SR-D17418 · Issue 498721

Attached note header displays properly in Hebrew locale

Resolved in Pega Version 8.2.3

With the locale set to Hebrew, the whole portal is presented correctly from right to left, but when opening a case note (attached email) the header was not displayed as right to left. This has been resolved by updating the 'DisplayNote' HTML of class 'Data-WorkAttach-Note' and 'Show' HTML of class 'Data-Corr-Email' to use locale information from the operator.

SR-D17660 · Issue 486700

Resolved OOM error for system scan

Resolved in Pega Version 8.2.3

In some installations, performing a system scan would cause an Out Of Memory Error. This was traced to the process used to de-serialize the catalog metadata, which caused the unzipped version of the catalog (containing data going back to v6 releases) to grow to 125 MB. To resolve this issue the system will make use of streams, but as that still requires the entire catalog object to be available, the system will also cull redundant objects from the hotfix catalog. Going forward, platform-specific catalog files will be created to minimize their size and improve efficiency.

SR-D17919 · Issue 491580

Corrected thread switching when moving between interactions tabs

Resolved in Pega Version 8.2.3

When using Create New for a Phone Call-Consumer in one tab and Create New for an Outbound Phone Call on another tab, the thread was not changing when switching between the tabs of the interactions. Closing the Outbound call interaction resulted in null pages on the clipboard. This has been resolved by updating the pzpega_ui_doc_tabsupport file so it switches to root document context if called from onActivate function using a flag.

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