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-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-131151 · Issue 572831

Resolved empty body for Reject email

Resolved in Pega Version 8.2.8

When using the pzEmailActions Section in Correspondence for Approve/ Reject functionality via email, there was no reply body in the email for Reject Option. This was due to the flow action for the Reject email being different than that of the Approve email, and has been resolved.

INC-131385 · Issue 573453

Swagger APIs updated

Resolved in Pega Version 8.2.8

The Swagger File APIs have been updated to ensure swagger document files generated meet specifications for editor.swagger.io .

INC-134370 · Issue 577633

Expanded Grid locking updated

Resolved in Pega Version 8.2.8

When using pyDashboadMyWorkList to show the cases of an operator with Master Detail in Read Only mode, the system was acquiring a lock on the expanded work object. To resolve this, the following changes have been made: - In activity Assign-pyAcquireObject, If the parameter bRODetails is true, do not call acquireWorkObject and do obj-open-by-Handle to get assignment and work page in pyAcquireObject activity. - In activity acquireWorkObject, the parameter skipWorkLock has been removed as acquireWorkObject should always acquire the lock.

INC-134557 · Issue 585646

Dropdown populated with parametrized data page source

Resolved in Pega Version 8.2.8

When configuring dropdowns or autocomplete controls with parametrized data page as a source in a section, the parameter configuration values and parameter names were not sent in the JSON created by the DX API view. This has been resolved by adding parameter support for DataPages in Dropdown, Autocomplete, and Radio buttons.

INC-134709 · Issue 579436

Updated endpoint Cross-site scripting protection

Resolved in Pega Version 8.2.8

Cross-site scripting security has been updated for Endpoints in Display activities.

INC-135161 · Issue 580934

Upload with "Select File" works in Microsoft Internet Explorer

Resolved in Pega Version 8.2.8

When using Microsoft Internet Explorer, uploading a document was failing on the first try when using the "Select File" button. The second attempt worked as expected. This was an intended consequence of work done to enable attaching the same file after deleting it, and was related to Microsoft Internet Explorer calling an "onChange" which caused the "pzAttachFileDDFileList" section which is used to display the attachments uploaded to not be properly refreshed. This has been resolved by updating the pzMultiFilePath control handling of the success and failure of the upload function call.

INC-136383 · Issue 584518

Delegated SLA rule allows "Notify party"

Resolved in Pega Version 8.2.8

When modifying an SLA that had been delegated to an access group, setting the perform action to "Notify Party" did not present an option to select a user to notify. Attempting to submit the change resulted in the error "pzGoalCorrName—Value cannot be blank" and the rule was not saved. This was a missed use case with the delegation of SLA when notify party was used. and has been resolved.

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