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-B67903 · Issue 330414

Offline DataTransform generation process improved

Resolved in Pega Version 7.4

in WHEN and OTHERWISE there was code which failed with the error "expressionCode = "pega.process.expression.evaluate(\"" + whenExpression + ""\""

SR-B67903 · Issue 329835

Offline DataTransform generation process improved

Resolved in Pega Version 7.4

in WHEN and OTHERWISE there was code which failed with the error "expressionCode = "pega.process.expression.evaluate(\"" + whenExpression + ""\""

SR-B67903 · Issue 328792

Fix for Data Transform when Clipboard Page not found.

Resolved in Pega Version 7.4

Logic has been added to correct the scope references of the generated offline-Datatransform-JS when using AppendAndMapTo.

SR-B76736 · Issue 328823

Offline localization fixed for field values with trailing spaces

Resolved in Pega Version 7.4

Field values were not localized offline if they contained trailing spaces. These spaces caused the field value lookup to fail, resulting in a JS exception. To handle this, a call has been added to trim the spaces if the field value is a string.

SR-B76736 · Issue 327585

Offline localization fixed for field values with trailing spaces

Resolved in Pega Version 7.4

Field values were not localized offline if they contained trailing spaces. These spaces caused the field value lookup to fail, resulting in a JS exception. To handle this, a call has been added to trim the spaces if the field value is a string.

SR-B81862 · Issue 330666

Offline localization support added for survey header

Resolved in Pega Version 7.4

Localization was not being applied as expected to a header section that served as the top part of an offline survey app. This header section used a pyCurrentSurveyQuestion property that held the value of the Question that was displayed on the screen, then the property value to be localized corresponded with field values contained in an offline allow list. The lack of localization was traced to the header section not pushing the context (via pega.pushStackFrame) when there was no using page defined. This lack of push is fine for the template renderer, but caused the offline localization logic to not have the correct context. In order to support the intended use, the code has been modified so that if the pzPrimaryPage is empty in the section metadata, the system will push the currentContext reference via pega.pushStackFrame.

SR-B84636 · Issue 335909

Needed functions/function libraries ported into JS text rules for mobile validation

Resolved in Pega Version 7.4

A validate rule with a simple string expressions attached to a flow action of an offline-enabled case failed to execute when the flow action was submitted in an Android app. This was traced to new handling for Validate rules usage in offline which relied on select Function rules ported to JavaScript functions, and the desired functions has not been ported. These functions/function libraries will now be ported into JS text rules.

SR-B84636 · Issue 335930

Needed functions/function libraries ported into JS text rules for mobile validation

Resolved in Pega Version 7.4

A validate rule with a simple string expressions attached to a flow action of an offline-enabled case failed to execute when the flow action was submitted in an Android app. This was traced to new handling for Validate rules usage in offline which relied on select Function rules ported to JavaScript functions, and the desired functions has not been ported. These functions/function libraries will now be ported into JS text rules.

SR-B84636 · Issue 334503

Needed functions/function libraries ported into JS text rules for mobile validation

Resolved in Pega Version 7.4

A validate rule with a simple string expressions attached to a flow action of an offline-enabled case failed to execute when the flow action was submitted in an Android app. This was traced to new handling for Validate rules usage in offline which relied on select Function rules ported to JavaScript functions, and the desired functions has not been ported. These functions/function libraries will now be ported into JS text rules.

SR-B86387 · Issue 339475

Offline mobile Work ID sync issue fixed

Resolved in Pega Version 7.4

When creating a new Case on the mobile offline application, temporary IDs are created. Once synced with the server, the Server IDs are correctly updated on the device. However, if 3-4 new cases were created, one case was failing due to the Server ID not correctly being updated on the device. This meant the device still carried the temp ID and failed to sync. This was traced to EventListener_executeFunction returning false when there was any exception in the subscribed function during its execution, making the subscriber function null in the Listeners array. To fix this, a safe check has been added in syncAttachmentDP and a try catch has been added in dataPageUpdateAction to handle the exceptions.

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