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-120450 · Issue 561743

Configure view finds existing calculations for properties

Resolved in Pega Version 8.4.2

Modifying a property to ‘calculated: Readonly’ by creating declare expression inside a fieldgroup list (which was created in the data model and refers to a datatype) while adding the fieldgroup list property by selecting from the field in the configure view of a step was not reflected when adding the same list type property inside another step of configure view. Declare expressions were created with page context for embedded fields by default in configure view, but Declare expressions have recently been enhanced and no longer expected to use page contexts. Because Configure view continued to use page contexts, this resulted in calculations that existed not being picked up. This has been resolved by configuring view handling for page list fields specifically to not create new calculations with a page context. Detection of calculations has also been updated to not check for page context to match the recent Declare expression enhancements.

INC-120472 · Issue 571437

Corrected date display on export to Excel

Resolved in Pega Version 8.4.2

Reports which have visible date and Date time properties or values displayed correctly when viewed in PEGA, but when the data was exported to Excel the values were converted to GMT time. Due to this the date fields (with no time stamp) were showing the date less by one day in Excel. This has been corrected.

INC-123033 · Issue 561388

Updated logic for delegating when the RARO exists

Resolved in Pega Version 8.4.2

When trying to delegate a Data Type, the validation error "Update Record Failed: This record is non-versioned and already exists and can not be moved to a different ruleset" appeared. Because data type delegation is dependent upon the existence of a RARO for the delegated data type, when delegating the ruleset of the RARO to accessgroups with the same roles the code was attempting to update the RARO. Updating the RARO determines if the Ruleset of the RARO is unlocked. If the ruleset is locked, then the logic attempts to select a new ruleset, but the RARO cannot be moved to a new ruleset. To resolve this, the logic has been updated so that if the RARO exists, the system will not try to create a new instance.

INC-125822 · Issue 566312

Agile Studio correctly embedding attachments

Resolved in Pega Version 8.4.2

Attachments were not being included in Agile Studio documents for backlogs and sprints as expected. This was traced to the third-party jar "jsoup", which was converting the parameter PegaDocumentObject to pegadocumentobject, causing a mismatch. This has been resolved by adding a check that will replace the converted name with the correct one.

INC-78420 · Issue 566792

Documentation clarified for pxGenerateExcelFile with template values

Resolved in Pega Version 8.4.2

Using Export to Excel created the document, but pxGenerateExcelFile was not replacing template values in the generated output file. To improve the clarity of the necessary configuration, the documentation for pxGenerateExcelFile has been updated to include an example of the usage:This can be used anywhere in platform to export excel file. E.g. - export stories, specifications, requirements etc. Example Usage of properties in template: {.pagelist().property input}\n{.property input}

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