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-223557 · Issue 732143

Integer property allows blank value

Resolved in Pega Version 8.8

When a field with a default value was changed to blank, the value was not updated on the clipboard. This has been resolved by updating the control_textinput file.

INC-223880 · Issue 733556

Handling added for IME input for date and value

Resolved in Pega Version 8.8

Attempting to input numbers in date and price areas generated from an input method editor (IME) Japanese keyboard was not working correctly due to the field not supporting double-byte characters. This has been resolved by adding an if condition for not formatting the date or value until IME input is done.

INC-224059 · Issue 743432

Corrected locking issue in repeating grid for local action

Resolved in Pega Version 8.8

When a grid was configured as readonly and the button in the grid had an open local action which opened up a section via flow action which was editable, on cancel, the grid context was treated as readOnly and was not releasing the lock. To resolve this, the pega.ctx.activeGrid.isOpenLocalAction flag has been added to releaseWOLock when a modal is launched from the grid using openLocalAction.

INC-224253 · Issue 744974

Corrected UI Kit highlighting error

Resolved in Pega Version 8.8

The highlighting in the drop down of a tag was displaying on another tab. This was traced to the activeTab class not being correctly added in the UI Kit for the case worker portal, and has been corrected.

INC-224317 · Issue 723105

Corrected embedded page list render error

Resolved in Pega Version 8.8

Using a page list within a page list was rendering with overlapping field forms. This has been resolved by removing the negative margin from field group legends when presented in a list.

INC-224446 · Issue 724370

Load more works in non-templatized layout

Resolved in Pega Version 8.8

After adding a repeating dynamic layout inside a tab group layout (which is a deprecated feature) to make it non-templatized, the progressive pagination option to show the "load more" button did not work. This was caused by the load more functionality having a dependency on pega.ui.RDL even though pega.ui.RDL was not available in case of a non-templatized grid, with the result of generating an exception which broke the flow. This has been resolved by adding a null check which will allow the flow to proceed whether the grid is used inside non-auto-generated or auto-generated elements. Please note that it is strongly recommend to update any deprecated layouts to Layout Group as it is a best practice to keep the code updated to avoid any compatibility issues.

INC-225236 · Issue 725704

Corrected LiveDesignViewDisplay error handling

Resolved in Pega Version 8.8

When all rulesets were locked and a section was opened from Live UI in a portal, a "rule deleted" message appeared and it was confirmed the rule was deleted even though the rule was in locked ruleset. Investigation traced this to a pzLiveDesignViewDisplay call to pxChooseBestRuleSet which jumped to failure logic when "allow check out" was disabled, and this has been resolved by correcting the error handling in pzLiveDesignViewDisplay.

INC-225247 · Issue 729607

SessionTimer correctly working in Mashup

Resolved in Pega Version 8.8

When using the pxSessionTimer in the mashup at section pxCaseActionArea, the timer pop up did not appear. Investigation showed the pxSessionTimer control was not correctly triggering in mashup. This has been resolved by updating the pega.desktop.support.restartTimeoutWarningTimer and closeAllPRPCChildWindows functions and adding the new functionality logOff() which uses the control_actions_logoff functionality.

INC-225511 · Issue 733185

cleanUpHarnessElements invoked to clear dirty objects in memory

Resolved in Pega Version 8.8

The objects for complex fields like table were not getting cleared once the current edits were discarded. This was leading to having the objects with dirty status remain in memory, leading to dirty popups or locks on the page. Investigation showed this was caused by the AjaxContainer div (which contains the grid div) being removed from markup but its reference remained in pega.u.d.harnessElements as a complex element. This has been resolved by explicitly invoking the cleanUpHarnessElements api before deleting the microDCDoc by passing the pzHarnessId as a parameter, which will remove the grid reference in pega.u.d.harnessElements.

INC-225753 · Issue 727394

DSS added to control whether empty captions are skipped for display

Resolved in Pega Version 8.8

When the property used a prompt list table type and a prompt value for one of the fields was empty, it is not being shown in drop-down. This caused unexpected default values to appear in drop-down lists. To resolve this, a DSS has been added which may be used to skip empty values. The default behavior of skipEmptyCaption is false to show all values as-is.

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