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.

INC-177263 · Issue 655830

isFutureDate edit validation fires correctly

Resolved in Pega Version 8.6.1

The date value entered was not getting converted to the user-specific time zone and resulted in an incorrect value for validation when using isFutureDate. This has been resolved by adding an update which will convert the date value to the specific time zone before comparing it with the current date.

INC-177852 · Issue 658654

Added UI handling for error message on Delegated data table

Resolved in Pega Version 8.6.1

It was not possible to navigate in the UI if there were error messages shown on properties in a delegated data table until that column was filled with a value. To resolve this, an update has been made to prevent reload or save on scroll.

INC-178639 · Issue 658056

Improved accessibility for Autocomplete Role

Resolved in Pega Version 8.6.1

Accessibility issues with Autocomplete Role have been resolved by adding role = "combobox" for autocomplete in template mode.

INC-179378 · Issue 661174

Repeating Layout renders correctly after update

Resolved in Pega Version 8.6.1

Repeating dynamic layout was not working properly after update. This was caused by a missing active class, and was traced to changes made in the pzpega_ui_layoutgroup function where reload happens on close of a modal dialog. To resolve this, a safe check has been added to setInActiveLayout in layoutgroup.js.

INC-179622 · Issue 659155

Flow action list available in navigation menu

Resolved in Pega Version 8.6.1

After update, only one flow action which had highest likelihood was visible when an assignment in a flow had multiple flow actions. Alternatives were not visible in the Action menu. This was an unintended side effect of work done to simplify the Actions menu which did not consider the usecase of an alternate flow action being configured, and has been resolved by restoring the flow action list to the navigation menu in pyWorkCommonActions.

INC-179883 · Issue 661615

Pega reference tags persist

Resolved in Pega Version 8.6.1

Cross-site scripting protections have been updated to allow Pega reference tags.

SR-D45101 · Issue 512530

Added support for Helper Text Question Mark with visibility condition

Resolved in Pega Version 8.1.7

The Helper Text Question Mark was not displaying if the control was configured with "Help icon with overlay on hover" combined with a visibility condition. This was a missed use case, and the expression visibility support for controls.changes have now been added in the pzpega_ui_DLCellTemplate.js file.

SR-C81829 · Issue 419227

pxCoveredCountOpen value decrease corrected

Resolved in Pega Version 8.2.1

When a flow reached the resolved stage (Resolved-Withdrawn), pxCoveredCountOpen was reducing the count by 2 instead of 1, eventually causing the value to go negative and prevent any further work objects from being marked as Withdrawn. Investigation showed the "Update status" activity was being called twice due to the Temporary WorkPage used to delete assignments persisting and appearing as a duplicate pyWorkPage. This caused an issue when using findPage by pzInsKey. To correct this, the "pxDeleteAssignmentsForWork" activity for Step-15 has been modified to explicitly remove the temporary WorkPage after the assignment is deleted.

SR-C85035 · Issue 421947

Added getIfPresent check for Field Value parameters with pzAPICreateJsonForView

Resolved in Pega Version 8.2.1

Calling pzAPICreateJsonForView was altering case values if localized field value parameters were added. This has been corrected by performing a getIfPresent and getIfString on the property pyFieldValueParams so field value parameters will not be added to the main page if they're not present.

SR-C82244 · Issue 421173

Enhancement made to allow passing of URL in actionset via the DX API

Resolved in Pega Version 8.2.1

When using the action "Open URL in Window" and the option "Use Alternate Domain" to pass a URL that is in saved in a property, the name of the property was passed when using the DX API instead of the URL. To allow this use, an enhancement has been added to support storing a last submitted value and a reference so that an action set with a property reference can return a reference object with lastSavedValue and the reference name attached.

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