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-184109 · Issue 671193

Handling updated for customDateTime formatting

Resolved in Pega Version 8.6.3

When a feature date was entered, for example as 2021/07/29 12:00:00 AM, changing any other property caused the time to be off by 4 hours and display as 2021/07/28 08:00:00 PM. Investigation showed this was caused by the parameters being passed in an incorrect order while calling pega.ui.Formatter.formatDateTime() in combination with customTimeZone, and has been resolved.

INC-191013 · Issue 683757

Number fields display the $ and % signs correctly

Resolved in Pega Version 8.6.3

After configuring a table with source as a page list and the fields with number control the symbol constant $ and % symbols were showing up as separate from the amounts in a cell. The $ symbol was all the way on the left of the field, and not aligned correctly with the number. The % symbol showed below the cell. This has been resolved by adding code for displaying the symbol inside the text input when the symbol alignment is configured as right.

INC-173944 · Issue 660180

Cancel button on embedded GridRow cancels single action

Resolved in Pega Version 8.7

When a modal Flow Action contained a Table with the Row operations configured as Master-detail and the Detail flow action was specified, if a validation error defined in a Validation rule (i.e. other than required field error) occurred while entering details for one of the rows and the Cancel button for that row was clicked, the entire action was cancelled and the modal window was closed without saving anything. This has been resolved by updating the system to prevent the modal closure if a row is added and then cancelled.

INC-193047 · Issue 694049

Added handling for nested clipboard pages

Resolved in Pega Version 8.6.3

On save of sections that have items (cells) nested more than one layer deep and have either "Show menu" or "Run data transform" actions, silent errors were found in the tracer indicating "Attempting to access a rule with a bad defined-on class: Trying to open rule ... of class "Rule-Navigation", but no defined-on class (pyClassName) was specified". This was due to the pzActionShowMenu Rule-Utility-Function and pzActionRunDataTransform Rule-Utility-Function assuming the clipboard page structure was only one layer deep, and has been resolved by using findRulePageFromCurrentPage from SectionUtils.java .

INC-190708 · Issue 688134

Save works on Ajax container without Dynamic container

Resolved in Pega Version 8.6.3

After opening a work object and making changes to a required field, pressing the save button did not give any visual indication that the save was performed. Hitting cancel generated a dirty pop up saying changes will be discarded, indicating no save was done. When an Ajax container is configured without a Dynamic Container, all the content is rendered inside a fieldset tag instead of a form tag. While performing the save, the API was looking for the form element in the document and could not find any, and the save failed. This has been resolved by updating the submitWhenFail() API to handle both fieldset and form elements in the dom.

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