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-C69729 · Issue 414969

Improved security for XXE

Resolved in Pega Version 8.1.3

Several updates have been made to improve security against External Entity Injection.

SR-C70602 · Issue 415503

Changed async loading when attaching Files with PegaCloudFileStorage to address 3rd party PEGA0046 error

Resolved in Pega Version 8.1.3

When using PegaCloudFileStorage, a PEGA046 alert was observed when attaching a file to a work object. This was a cosmetic issue that did not affect functionality, and was traced to the use of an external logging system that is not part of the standard system development for Pega. In order to remove this alert, Step-5 (Load-DataPage) of Data-WorkAttach-File.pzSaveToRepository activity has been removed as asynchronous loading of D_pxNewFile data page is not required.

SR-C70867 · Issue 414703

Resolved focus for new Microsoft Internet Explorer windows in Citrix environment

Resolved in Pega Version 8.1.3

When opening a new Microsoft Internet Explorer window in the Citrix envirnoment, the window would open in the foreground and then immediately shift to the background. Investigation showed that when a menubar item was clicked, there was a call to show submenus in a settimeout of ZERO which implicitly did a focus on the menu item. Though the focus on the menu item happens after the window.open (action) is called, for in-house cases the focus occurs before the window is completely opened. However in this case, this focus was delayed and the new window was sent to the background. To correct this, the system has been updated so it will not perform focus on the menu item if the document itself is not in focus.

SR-C71043 · Issue 416762

pzSendEmail returned to revious behavior of sending separate emails to work parties

Resolved in Pega Version 8.1.3

After upgrade, a change in behavior was seen when using the pzSendEmail activity. When pzSendEmail was called to send emails to work parties, a single email is sent to all recipients instead of separate emails to each recipient as it did in earlier versions. The SendSimpleEmail activity accepts a SendDiscreteMails parameter, the pzSendEmail activity has 'Pass current parameter page' checked so the default value for the SendDiscreteMails parameter was not used. This was a backwards compatibility error, and has been corrected by setting the SendDiscreteMails parameter to true by default in the pzSendEmail activity.

SR-C71053 · Issue 413209

Added handling for defer-loaded dynamic layout inside a flowaction grid

Resolved in Pega Version 8.1.3

When using a grid configured to show the details in expandable rows and the inner grid was a work bound grid, trying to expand the rows only showed the "Loading ..." message and never completed. This was traced to a missing use case for having a defer-loaded Dynamic layout which wraps the grid inside a flowaction embeddedpane grid, and has been corrected.

SR-C71070 · Issue 417207

UI-Toolkit updated to resolve issue with fields overlap in dynamic layout collapse header

Resolved in Pega Version 8.1.3

The UI-Toolkit has been updated to resolve an issue with Dynamic layout where using a Collapsible Header that has multiple fields to be displayed resulted in the fields overlapping or being mis-aligned.

SR-C71520 · Issue 415399

Robot Manager portal re-launch correctly renders the last active screen

Resolved in Pega Version 8.1.3

Two problems were seen with Robot Manager:1) Opening Robot Manager and then navigating to Workgroup drill-in screen worked as expected, but when the portal was closed and re-launched from Designer Studio, the last active screen (workgroup drill-in) was rendered but with no valid data in it. 2) Opening Robot Manager from email notification worked the first time, but when the same button from the same mail was clicked, the last active screen was rendered with blank or no valid data. This was caused by preActivity and preActivityParams not being sent in the doUIAction call during re-launch of the portal, and has been fixed.

SR-C72252 · Issue 415224

isAncestorOf function now checks whether a child class is defined in the tenant layer

Resolved in Pega Version 8.1.3

After upgrade, the isAncestorOf function was not returning the correct result. Checking the inheritance path for the tenant work class showed the shared layer work class, but after upgrade of the tenant layer, the IsAncestorOf function returned false and the functionality that uses isAncestorOf function failed if the parent class was in the shared layer and the child was in the tenant layer. To correct this, the logic has been updated so that rather than always checking in the shared layer, the system will check whether the Descendant class is defined in the tenant first.

SR-C72385 · Issue 414868

Resolved ClassCast email exception caused by duplicate javamail class loading

Resolved in Pega Version 8.1.3

A ClassCastException was occurring when attempting to configure an email account in conjunction with JBOSS , WebLogic, or WebSphere Liberty. Analysis traced the issue to Class Loading: the WAS application server was providing a default com.ibm.ws.prereq.javamail.jar which conflicted with Pega's out of the box mail-1.5.5.jar, and at run time the JAR provided by WAS was getting picked due to JBoss, Weblogic, and WAS loading architectures from Tomcat. To resolve this, the delegation in PRAppLoader has been expanded to include the "javax.mail." package. This will ensure that Pega delegates to the web-app classloader unconditionally for the email classes. This prevents the ClassCastException caused by the interface javax.mail.Transport and com.sun.smtp.(Implementation Class) being loaded by two different class loaders.

SR-C73425 · Issue 413723

Fixed error when trying to discard a circumstanced Report Definition rule

Resolved in Pega Version 8.1.3

Attempting to discard and delete a circumstanced Report Definition rule resulted in an error on screen, in the tracer, and in the log file. This was caused by the system being unable to identify a reserved property when circumstanced on an embedded page or primary page. To correct this, the saveCircumstanceIndex rule of Rule- activity's first step has been modified to get the circumstanced property for this use.

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