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-D77268 · Issue 542339

Updated URL opening for iOS 12 & 13

Resolved in Pega Version 8.4.1

Attempting to open a URL did not work on iPad/iPhone with iOS 12 and 13 and PIMC version 8.3.500. This has been resolved by updating previewPIMCAttachmentOnline function to handle URL opening by using the application.openurl function.

SR-B89567 · Issue 340261

Logic reworked for case advancement

Resolved in Pega Version 7.4

The logic in function pega.process.engine.canAdvance was incorrectly calling pega.process.caseType.getNextTask before running the execPostProcessHook or the subFlowPostProcessHook functions, leading to missing properties needed by the decision shapes in the flow. This has been fixed.

SR-123130 · Issue 184202

Added apostrophe handling for navigation rule item names

Resolved in Pega Version 7.1.8

If an apostrophe (') was present in the label of Navigation rule item name, the onclick functionality of menu option was not working and threw a JavaScript error. In this JS file, the eval(strAction) function call failed because strAction text contains all the parameters enclosed in single quotes: if the label contains an apostrophe, that became an extra quote in this text. To avoid this, the functions pzMenuBarTranslator and pzActionShowHarness have been modified to handle extra apostrophes passed by the label.

SR-C6156 · Issue 351338

Changed RDE 'when' process to avoid syntax errors

Resolved in Pega Version 7.4

The syntax of the Rule-Declare-Expression was incorrect, enclosing the expression in apostrophe('). There was no change in the functionality, but it was not possible to use 'save as' on the rule and an error was generated. In addition, the function calls syntax was missing the @ symbol before the function. These errors were traced to conditions previously fetched from the HTML form data: instead of parsing the html and retrieving the condition, the system will now check if a pyWhen value is available. If it is present, the system will directly use that to create the UI.

SR-C6156 · Issue 350820

Changed RDE 'when' process to avoid syntax errors

Resolved in Pega Version 7.4

The syntax of the Rule-Declare-Expression was incorrect, enclosing the expression in apostrophe('). There was no change in the functionality, but it was not possible to use 'save as' on the rule and an error was generated. In addition, the function calls syntax was missing the @ symbol before the function. These errors were traced to conditions previously fetched from the HTML form data: instead of parsing the html and retrieving the condition, the system will now check if a pyWhen value is available. If it is present, the system will directly use that to create the UI.

SR-C10430 · Issue 353177

Null check added for offline rendering of declarativeTarget

Resolved in Pega Version 8.1

When rendering a section offline that has declaratives, the platform tried to evaluate a pyWorkPage which had no parent, resulting in a JS error and breaking the subsequent JS functions. This has been handled by putting a null check in the failing JS function.

SR-D34359 · Issue 510602

StretchTabsWidth performance improvements

Resolved in Pega Version 8.1.8

Slowness was seen when a new intent task was created through an interaction. To improve performance, some of the unnecessary calls to the Layout Group _updateStretchTabsWidth() function have been eliminated, and the function code has been updated to use native javascript performant helper functions so it starts rendering sooner. A flag has also been added to disable addnewtab and resizeactions: these need to be enabled through pega.u.d.DISABLE_LG_RESIZE and pega.u.d.DISABLE_ADDNEWTAB.

SR-D34359 · Issue 510600

StretchTabsWidth performance improvements

Resolved in Pega Version 8.2.6

Slowness was seen when a new intent task was created through an interaction. To improve performance, some of the unnecessary calls to the Layout Group _updateStretchTabsWidth() function have been eliminated, and the function code has been updated to use native javascript performant helper functions so it starts rendering sooner. A flag has also been added to disable addnewtab and resizeactions: these need to be enabled through pega.u.d.DISABLE_LG_RESIZE and pega.u.d.DISABLE_ADDNEWTAB.

SR-D39356 · Issue 515148

StretchTabsWidth performance improvements

Resolved in Pega Version 8.2.6

Slowness was seen when a new intent task was created through an interaction. To improve performance, some of the unnecessary calls to the Layout Group _updateStretchTabsWidth() function have been eliminated, and the function code has been updated to use native javascript performant helper functions so it starts rendering sooner. A flag has also been added to disable addnewtab and resizeactions: these need to be enabled through pega.u.d.DISABLE_LG_RESIZE and pega.u.d.DISABLE_ADDNEWTAB.

SR-D56953 · Issue 523475

StretchTabsWidth performance improvements

Resolved in Pega Version 8.2.6

Slowness was seen when a new intent task was created through an interaction. To improve performance, some of the unnecessary calls to the Layout Group _updateStretchTabsWidth() function have been eliminated, and the function code has been updated to use native javascript performant helper functions so it starts rendering sooner. A flag has also been added to disable addnewtab and resizeactions: these need to be enabled through pega.u.d.DISABLE_LG_RESIZE and pega.u.d.DISABLE_ADDNEWTAB.

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