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-123977 · Issue 185468

Optimized regex decision tree for property and when values

Resolved in Pega Version 7.1.8

A regex expression run against long property names was resulting in system slowdown and stuck requestor threads. A similar issue was encountered with When rules. To resolve this, the decision tree has been optimized.

SR-126181 · Issue 188742

Corrected tab display for failed visible when conditions

Resolved in Pega Version 7.1.8

When a repeating tab layout on a page group property includes "Body Visible When", tabs were displayed properly, but sections within were not being rendered for some tabs. To correct this, a visible when rule has been added to the outside content Div to handle situations where the when condition is not satisfied.

SR-D68235 · Issue 534781

Stale WorkSearchPreference data cleared when switching apps

Resolved in Pega Version 8.3.3

The D_pyWorkSearchPreferences data page data was not refreshing while switching between apps, causing stale data to be populated under the case search dropdown for all the applications after switching the application from one to another. This has been resolved by removing the D_pyWorkSearchPreferences data page as part of pzProcessApplicationSwitch.

INC-185847 · Issue 669526

Handling added for disabling weekends when no weekends are available

Resolved in Pega Version 8.7

A browser exception was generated while selecting the option “Disable weekends”. This was traced to a malformed array of weekends in a scenario where the Data-Admin-Calendar instance had all business days checked (i.e., no weekends). To resolve this, DatePickerAssembly and pzGenerateDatePicker have been updated to handle the case when there are no weekends available in the Data-Admin-Calendar instance.

SR-122409 · Issue 182081

Refresh when active' tabs no longer affecting other tabs

Resolved in Pega Version 7.1.8

A tab using the 'Refresh when active' setting, could cause the content of other non auto refreshing tabs to re-execute. E.g. Report Definitions that are sourcing repeat grids in other tabs. This occurred when using the 'Refresh when active' setting on a tab whose content is a Dynamic Layout (the out-of-the-box default when adding a tab) with an embedded section. There was a local workaround of updating tabs to use the required section as the top level content rather than using a dynamic layout with an embedded section, and this has now been incorporated into the software. The refresh when active setting is still available in this configuration.

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.

SR-127491 · Issue 193606

Resolved runtime error when editing complex grid cells

Resolved in Pega Version 7.1.8

When using grid edit mode inline on a grid with a section inside a cell that includes a checkbox and a 'when' condition, a runtime error appeared when the cell was clicked. This was an issue with the wrong reloadElement being passed in the editRow() API, and this has been corrected.

SR-D60284 · Issue 550558

Delete Requestor method updated for use with CMT

Resolved in Pega Version 8.3.3

JMS MDB Listeners with Container Managed Transaction (CMT) enabled in Websphere 8.5 had global transactions fail. To initialize a JMS-MDB listener, a requestor of type APP is used. Upon the service being fully initialized, the requestor is removed by executing a delete operation followed by a COMMIT. However, in this scenario, the initialization operation is running within a CMT context and a SQLException was raised indicating that the commit was not allowed. To resolve this, the delete requestor method has been refactored to take into account the CMT context so the commit is not executed if the transaction is managed by the container.

SR-D65239 · Issue 547821

Handling added for encrypted messages using IMAP

Resolved in Pega Version 8.3.3

Log errors were seen related to Email Listeners while processing encrypted emails from specific mail IDs, including "Unable to determine DSN, EmailClientRuntimeException: Unable to load BODYSTRUCTURE" and "isMimeType(JavaMailMIMEMessage - Unable to determine partIsEncryptedMessage". This issue is related to how certain servers work with the IMAP protocol to parse messages, and has been handled by creating a new instance of MimeMessage from the original MimeMessage and working on it.

SR-D81659 · Issue 548899

Handling added for encrypted messages using IMAP

Resolved in Pega Version 8.3.3

Log errors were seen related to Email Listeners while processing encrypted emails from specific mail IDs, including "Unable to determine DSN, EmailClientRuntimeException: Unable to load BODYSTRUCTURE" and "isMimeType(JavaMailMIMEMessage - Unable to determine partIsEncryptedMessage". This issue is related to how certain servers work with the IMAP protocol to parse messages, and has been handled by creating a new instance of MimeMessage from the original MimeMessage and working on it.

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