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-C94549 · Issue 438432

Secure RESTful implementation for Websphere Liberty added

Resolved in Pega Version 8.3

Mbean server connection errors were seen when trying to configure remote SMA in Websphere Liberty 18.0. The local mode worked as expected. Investigation showed that some needed IBM classes and jars were not present because Websphere Liberty does not ship with the same Java Libraries as traditional Websphere, causing a ClassNotFoundException when attempting to use the admin client Java APIs needed to connect to remote nodes. To resolve this, a secure RESTful implementation for Websphere Liberty has been added. Additional configuration is required on the target nodes, prweb in order to use this RESTful API: see the following IBM documenation: https://www.ibm.com/support/knowledgecenter/en/SS7K4U_liberty/com.ibm.websphere.wlp.zseries.doc/ae/twlp_admin_restconnector.html The above configuration will only work with the new prsystmgmt WAR provided as part of this fix.

SR-D5183 · Issue 438440

Prconfig enhancements for Cassandra diver connection pool

Resolved in Pega Version 8.3

An enhancement has been added to to support the following prconfig setting options for the Cassandra driver's connection pool:dnode/cassandra_max_requests_per_connection/local dnode/cassandra_max_requests_per_connection/remote dnode/cassandra_max_connections_per_host/local dnode/cassandra_max_connections_per_host/remote In addition, error handling in the CassandraBrowseByKeysOperation has been improved. To avoid NPEs caused by a record in Cassandra (DDS data set) that has data_ column set to null, CassandraDataEmitter will skip records with a null data_ column.

SR-D2240 · Issue 438452

Check added for custom section use in Summary report exported to Excel

Resolved in Pega Version 8.3

Criteria were missing when Export to PDF was used for Summary reports filtered by a custom section. This was caused by the needed pyQueryTokenList not being repopulated for the export in the case of custom section use, and has been resolved by adding a summary report check in the pzIncludeCustomFilterSection section before invoking pzClearRDTempFilters function.

SR-D3655 · Issue 438566

Resolved UI issues with TextArea control

Resolved in Pega Version 8.3

Two issues were seen with TextArea after upgrade: 1) The UI flickered when using a section where a checkbox click caused a TextArea to appear; and 2) When 'size to content' was specified for height in the TextArea, the area became unresponsive when the content was reduced. These issues have been corrected by setting height to auto instead of 0px while updating the text area height.

SR-C96394 · Issue 438670

Report data query updated to better handle exceptionally large queues

Resolved in Pega Version 8.3

If the database queue was exceptionally large (more than 3.5 million items), the report data query aggregating the results was timing out and showing 0 items queued on the management landing page. To resolve this, the summary view has been changed to rely on the data pages of the detailed view instead of aggregating the results by firing another query with RD.

SR-D2400 · Issue 438739

Security for ExporttoPDF tool process improved

Resolved in Pega Version 8.3

In order to increase system security, the tool process around iframe HTML tags used in generating a PDF with chart image data has been improved.

SR-C89040 · Issue 438827

Calling flow correctly resumed after sub-process completes

Resolved in Pega Version 8.3

If a case was processed via Operator1 and passed as an assignment to a workbasket where Operator2 picked it up and performed a Reject case on it, the process in Flow1 correctly called Flow2, but once Flow2 was processed Flow1 was not resumed. If Operator2 only performed the Reject processing, Flow1 was resumed. To to ensure the correct flow resumption, the location of the pyFirstRun setting in flowMethodBody FUA has been updated.

SR-C95667 · Issue 438853

Corrected UI distortion for the errors container format

Resolved in Pega Version 8.3

After upgrade, using pydisplay to case stages in a harness resulted in misalignment issues in the UI. Investigation showed that this issue was due to an incorrect margin value for the errors container format following recent redesign work in the UI Kit, and has been resolved by correcting the value.

SR-D392 · Issue 438871

Behavior reset for using getLocalizedValue with an input string containing parentheses

Resolved in Pega Version 8.3

After upgrade, the getLocalizedValue function was not returning any value if the input string contained parentheses. This was a difference in behavior caused by a missed use case when correcting another issue, and has been resolved by resetting the system to the previous behavior of getLocalizedValue returning a localized string in cases where a Field value/Rule message is present, or otherwise returning the exact input string.

SR-D1441 · Issue 438905

CMIS Timestamp function updated to support more timezones

Resolved in Pega Version 8.3

When trying to edit any attachment , a null pointer exception was generated from the out of the box activity pygetobjectfromAPPCMISConnector by the pzFormatCMISTimestamp function in the class PRDateFormat.java. This was traced to CMIS using a library that did not support all the possible timezones for a timestamp. To resolve this, the RUF pzFormatCMISTimestamp has been updated to use java.text.SimpleDateFormat as it currently supports the highest number of timezones and permutations in the CMIS timestamp format. A check has also been added so that if a timezone cannot be found, the date is simply not converted and a warning is logged.

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