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-C16525 · Issue 356495

CheckDependency improvements

Resolved in Pega Version 7.4

String and character checking have been reworked in order to improve the CheckDependency process for DL files from PegaSupport.

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-C6899 · Issue 351811

Decision tree correctly evaluates condition

Resolved in Pega Version 7.4

A decision tree was going to the 'otherwise' condition even though satisfying 'if' blocks existed. This was an unintended consequence of another fix related to the handling of brackets, and has been corrected.

SR-C6899 · Issue 351602

Decision tree correctly evaluates condition

Resolved in Pega Version 7.4

A decision tree was going to the 'otherwise' condition even though satisfying 'if' blocks existed. This was an unintended consequence of another fix related to the handling of brackets, and has been corrected.

SR-B81856 · Issue 335124

Cursor behavior fixed in search text field

Resolved in Pega Version 7.4

The cursor was moving ahead when typing search text in a filter grid, causing typos. This was an unintended side effect of a fix to the method used when focusDomElement is called in settimeout, and has been fixed.

SR-B85963 · Issue 339603

Resolved duplicate Guardrail warnings

Resolved in Pega Version 7.4

Duplicate guardrail warnings were appearing in the DT and Section rules due to multiple warnings being generated with the same time stamp. To fix this, the system will use the synchronized timestamp function to ensure the created time is different for each warning.

SR-B85963 · Issue 338180

Resolved duplicate Guardrail warnings

Resolved in Pega Version 7.4

Duplicate guardrail warnings were appearing in the DT and Section rules due to multiple warnings being generated with the same time stamp. To fix this, the system will use the synchronized timestamp function to ensure the created time is different for each warning.

SR-B86181 · Issue 334246

Cursor behavior fixed in search text field

Resolved in Pega Version 7.4

The cursor was moving ahead when typing search text in a filter grid, causing typos. This was an unintended side effect of a fix to the method used when focusDomElement is called in settimeout, and has been fixed.

SR-B86753 · Issue 339777

Mouse resize of modal dialog fixed

Resolved in Pega Version 7.4

After opening a flow in a modal dialog and resizing the first window by using the mouse (drag bottom-right corner), the resize option disappeared after proceeding to the next assignment. In this case, when back-to-back assignments were executed in the modal dialog, the resizehandler was not registered when navigating to the second assignment as the modal dialog was not initialized again but instead used a section refresh. A script has now been added to call pega.u.d.modalDialogExtras in pzModalActionAreaContainer if the resize handler is not available for back-to-back assignments.

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