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.

SR-C82619 · Issue 421023

JavaILCompiler updated to skip a type convert when generating code for a ternary operation

Resolved in Pega Version 8.3

A compilation error was generated when attempting to save a Data Transform with a java expression giving the ternary as boolean. In this case, the pyWorkPage.Channel was set to  @java("tools.findPage(\"TempInputAccelPage\").getProperty(\"Channel\").getMessageCount()>0") ? "" : pyWorkPage.Channel.


The system previously used EL code generation, which had a gap which allowed such expression to work. Since the system now uses IL code generation, this expression failed. In order to ensure backwards compatibility, logic has been added to  JavaILCompiler to skip a type convert when generating code for a ternary operation where the source is ILProgramText (java expression).

SR-C79523 · Issue 421039

Updated the documentation for enabling debug logging during upgrades

Resolved in Pega Version 8.3

The documentation regarding enabling debug logging during upgrades has been updated to reflect the following information: To enable debug logging during installs, upgrades or prpcUtils invocations: The template logging configuration for installs, upgrades and prpcUtils is located within the scripts/config directory of the Pega Platform distribution. To change what gets logged, modify the prlog4j2.xml file (refer to https://logging.apache.org/log4j/2.x/manual/configuration.html#XML). Some of the utilities involved in the install and upgrade processes use java logging. To impact what is logged by these tools, modify the deploylogging.properties file in the same directory.

SR-D8794 · Issue 483814

Import ordering shifted to prioritize Functions and Libraries

Resolved in Pega Version 8.3

A runtime error was seen when running DataTransform getbranchandcbsadetails. Investigation showed that when getbranchandcbsadetails was imported, the RUF it referenced was not imported beforehand. To resolve this, the import ordering has been reworked to prioritize Function and Libraries by shifting Rule-Utility-Library and Rule-Utility-Function to be after Rule-Obj-Property* in the import order.

INC-139861 · Issue 594006

Cross-site scripting protections added to Case Email

Resolved in Pega Version 8.5.4

Cross-site scripting updates have been added to rules handling linked email correspondence.

INC-138348 · Issue 599772

Added parameter skipPropertyEvaluation to handle CSS in email HTML

Resolved in Pega Version 8.4.4

While sending an email with custom HTML appended to the email body, a "+" sign in the body was causing the correspondence generation to fail. Investigation showed that if there were CSS classes with braces in the message body, the braces were being removed and replaced via "+" symbol in step 21 of CorrCreate activity. To resolve this, a new Boolean parameter skipPropertyEvaluation has been added in the CorrCreate activity to handle the decision to either evaluate the logic or not, and the pre-requisite will be to resolve all the property references before calling this activity so custom CSS braces { } will be honored when the message body is sent.

INC-140266 · Issue 602076

Search made consistent across environments

Resolved in Pega Version 8.4.4

Search was behaving differently based on whether the user was launching the search by clicking the search icon or hitting enter directly. The search icon passed the classes list and fetched cases based on that, whereas hitting enter performed the search without the classes list unless it was a multi-tenant environment. This has been resolved by updating the pyWorkIDSearch activity to pass application classes list in any environment.

INC-143025 · Issue 600611

API performance improvements

Resolved in Pega Version 8.4.4

Performance improvements have been made for running the get assignment action details API.

INC-144265 · Issue 609287

Updated timestamp handling for duplicate key issue with PyCompleteAutomation

Resolved in Pega Version 8.4.4

Occasionally a robot failed to complete a case due to a duplicate key exception. This was an issue with the History record creation due to duplicate key erlated to the timestamp, and has been resolved by updating the timestamp handling so that the REST API will use 'getCurrentTimeStampUnique' and for other cases 'pxGetCurrentTimeStampThreadUnique' will be used.

INC-144358 · Issue 601014

Localization added for "Automatically" and "Manually" field values

Resolved in Pega Version 8.4.4

The Dutch translation of "Child case [Case_type] [Case_id] has been [Instantiation_mode] instantiated" used the hard-coded English expression "manually". This has been resolved by adding the "Automatically" and "Manually" field values to localization.

INC-146174 · Issue 602868

Chevron vs Back button in screen flow made consistent

Resolved in Pega Version 8.4.4

When using the TabbedScreenFLow7 harness with the "Enable navigation Link" and "Only allow navigating back to step" settings for the flow along with client-side validations, the validations were ignored when using the back button but using the chevron displayed a validation error. Investigation showed that the case action area buttons and bread crumb navigation were out of sync during the back button operation. This has been resolved by updating the ProcessStep function in BreadCrumbTrial library to pass skipValidations while calling gotoprevioustask.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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