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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-119858 · Issue 175151

Adjusted code to prevent double-localization when using Google Chrome

Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7

When utilizing a locale that uses commas instead of points to demarcate decimals in numbers, editing any numbers in a skin caused extra zeros to be added to the numbers. When using Google Chrome, if an input type is a number, Google Chrome by default will localize. The control is also localizing the value after reload, so localization is happening twice. In order to resolve this, If the input type is text, only control localization will happen.

SR-A76677 · Issue 253493

IDP SAML 2.0 schema validation error resolved

Resolved in Pega Version 7.2.2

When generating the Pega SP metadata after importing the Shibboleth IDP metadata, the error "The metadata does not pass the SAML 2.0 schema validation" appeared. This has been resolved by modifying the pzDownloadSPMetadata activity to generate a unique secure random ID prefixed with an underscore.

INC-132191 · Issue 582550

Option added to return to same authenticationService after SAML logoff

Resolved in Pega Version 8.5.2

An enhancement has been added which provides a check box on the Authentication Service ruleform to select the option of redirecting users back to their original authentication service screen after logoff.

INC-168837 · Issue 646972

CSRF token updated for use with OKTA login

Resolved in Pega Version 8.7

An issue seen while connecting via OKTA has been resolved by updating the CSRF token validation for use with IDP initiated SSO login.

SR-A77173 · Issue 254080

IsWindowStealFocusInIEAllowed allows 'when' value

Resolved in Pega Version 7.2.2

In order to run legacy and Pega applications in parallel, a site configured the system to create a case in the Pega application as soon as a case was created in the legacy application. The intent was to have the case created in Pega to be in the background, but performing any DC actions shifted focus to the Pega app window when using Microsoft Internet Explorer . In order to have the configuration work as desired, the pyIsWindowStealFocusInMicrosoft Internet Explorer Allowed when rule must be set to false (default is true). Support for a conditional window focus configuration is now available, based on pyIsWindowStealFocusInMicrosoft Internet Explorer Allowed 'when' rule value.

INC-138243 · Issue 584897

Performance improvement in When parsing

Resolved in Pega Version 8.5.2

After upgrade, performance issues were seen in the execution of rules with When conditions. This has been resolved by modifying the code to address some inefficiencies in the parsing method.

SR-116761 · Issue 169833

FormatNumber use clarified

Resolved in Pega Version 7.1.7

Attempting to use the "pxFormatNumber" function in an activity step generated the error message "com.pega.pegarules.session.internal.mgmt.Executable cannot be cast to com.pega.pegarules.pub.runtime.StreamBuilderToolKit". Formatter RUF were not intended to be called directly from activities, but RUF has been enhanced to work with reduced functionality in case it is called from activity. The documentation has also been updated to reflect preferred usage.

SR-B84336 · Issue 332037

onOnlineDetected use matches documentation

Resolved in Pega Version 7.4

iOS11 was failing the first login attempt. Documentation for the addListener method in pzPega_offline_datasync rule lists 'onOnlineDetected' as optional, but when the listener was added without onOnlineDetected the console.error occurred. This was originally a documentation error where the rule was incorrectly given as optional even though the event handlers always assumed onOnlineDetected was defined, but as there are reasons to support this use the system has been updated this so onOnlineDetected is truly optional now.

INC-192464 · Issue 681751

PackageComponent updated for use with repositories

Resolved in Pega Version 8.7

Exporting a zip file created by the Component wizard to a repository resulted in an error, however the same process worked as expected when the zip file was created by the Product wizard. Investigation showed that pxPackageComponent was not kept up to date with new metadata requirements for Artifactory export. This has been resolved by modifying pxPackageComponent step 7 to set Param.ArtifactType to "component" and Param.ArtifactName to [component name]_[component version]. A privilege check has also been added to zipMoveExport.

SR-C1026 · Issue 344634

Able to add When condition for DisplayYesNo

Resolved in Pega Version 7.4

An exception was generated when attempting to add 'when' conditions for DisplayYesNo control in Section. The pzActionConditionSource activity was fetching the pyUIElement value from the Primary Page and setting it to UIELement as intended, but when the pyUIElement value is empty, a null-pointer exception occurs. Handling has now been added to avoid this scenario.

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