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.

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-126942 · Issue 583397

Report Shortcuts resolve datapage parameter references

Resolved in Pega Version 8.4.3

After upgrade, no results were displayed in case manager portal report browser. This was traced to a data page value that was not resolved at runtime when a data page was used in the report definition shortcut to pass a parameter value. Investigation showed this was due to a change made for v8.4 to correct an issue with data page variables that were not persisting if a report was made with pre-exisiting filters. To resolve this, the logic related to pzResolveCopyFilters has been updated.

INC-128880 · Issue 592814

Handling added for angle brackets in legacy Chart control

Resolved in Pega Version 8.4.3

When using Investigative Case Management, some report charts were not rendering correctly. This has been resolved by updating appendFormattedString in AbstractJsonDataGenerator.java to escape angled brackets (< and >) before appending the input.

INC-131942 · Issue 574324

Orphaned CSS reference removed from DisplayReport harness

Resolved in Pega Version 8.4.3

An intermittent invalid CSS error was appearing in the DisplayReport harness when an operation resulted in the regeneration of the harness content. This was traced to a reference to the workform_pyReportingSkin CSS, which was used in old reporting features and is not in use anymore. The reference has been removed to resolve this issue.

INC-135719 · Issue 581380

Corrected reference exception for filter on a grid sourced from a parameterized report definition

Resolved in Pega Version 8.4.3

An Invalid Reference Exception was thrown after attempting to apply a filter on a grid sourced from a parameterized report definition. This was traced to work done to allow cross-scripting filters to allow filters to contain special characters, and has been resolved.

INC-136643 · Issue 583365

Orphaned CSS reference removed from DisplayReport harness

Resolved in Pega Version 8.4.3

An intermittent invalid CSS error was appearing in the DisplayReport harness when an operation resulted in the regeneration of the harness content. This was traced to a reference to the workform_pyReportingSkin CSS, which was used in old reporting features and is not in use anymore. The reference has been removed to resolve this issue.

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