Skip to main content
circle-square
Outline Circle
square-square
Little Circle
square-square
Little Circle

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 SR ID number 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-130917 · Issue 573429

Extension point added for customizing MFA

Resolved in Pega Version 8.4.2

An enhancement has been added to allow MFA to overwrite OTPInputs by offering an extension point for OTP generation and validation.

INC-131496 · Issue 573370

Correspondence preview works with non-English character in pzinskey

Resolved in Pega Version 8.4.2

Attempting to preview a Correspondence with non-English character on the pzinskey displayed the non-ascii characters as a parameter converted to squares. As a result, the correspondence template could not be found in the template list and could not be previewed. Investigation showed that once the URL was decrypted, it was not being decoded. This has been corrected.

INC-131521 · Issue 574774

Updated method for fetching Open ID Connect Token End Point URL with GRS

Resolved in Pega Version 8.4.2

In Open ID connect Authentication service, the Token End point URL was not working with GRS. To resolve this, the code has been updated to fetch the access token endpoint using the getStringIndirect method instead of getStringIfpresent.

INC-132209 · Issue 577003

CDK key loading modified for better database compatibility

Resolved in Pega Version 8.4.2

CDK key loading modified for better database compatibilityUsers were unable to log on to the system and received the error "There has been an issue; please consult your system administrator." Investigation showed the log errors stating "(dataencryption.DataKeyProvider) ERROR localhost - Could not get CDK from systemKeyManagementCache - System CDK is null". This was an issue specific to the MS SQL Server database when there were 6 or more CDKs in the database: CDK keys are loaded from database into Cache using an SQL statement which had the ORDER clause. By default, the ORDER clause treats NULL values differently on different databases, and this caused MS SQL databases to not load a necessary CDK key. To resolve this, the SQL query has been modified so the result will be the same for all supported daatbases (Oracle, Postgres & MS SQL Server).

INC-132634 · Issue 573041

Removed non-functional 'forgot password' link in mobile

Resolved in Pega Version 8.4.2

On mobile app login, if a user selected 'Forgot Password' then navigated back to the login screen and logged in, the portal loaded in a browser tab instead of the app itself. This was due to 'Forgot password' not yet being supported in mobile even though the link was displayed, and has been resolved by removing the link as it does not initiate any flow.

INC-132859 · Issue 573491

ProductInfoReader updated to fetch only most recent version information

Resolved in Pega Version 8.4.2

Hfix scanner has been modified so that ProductInfoReader.runQuery will fetch only latest version of DAPF instances during a scan.

INC-123156 · Issue 560669

Check added for equivalent table during data upgrade

Resolved in Pega Version 8.4.2

The Data Upgrade between Pega versions failed with the error "DatabaseException caused by prior exception: java.sql.SQLException: ORA-01408: such column list already indexed". This was caused by the system not considering duplicate indexes before modified indexes. Once it's identified an index has been modified, the system would try to alter it without considering that what it was altering it to might already be present. To resolve this, an update has been made so the system will not alter an index if the resulting index would be equivalent to a different one on the table.

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 Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us