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.

INC-218265 · Issue 720611

DoClose updated to resolve lock and context issues

Resolved in Pega Version 8.8

An interaction case was closing when intent tasks were closed from CSRecents. Investigation showed this was due to the doClose activity not being triggered in the right context, and has been resolved. An additional issue with locks not being correctly released after opening the new case Create stage and clicking Cancel in the modal was traced to a missing pyWorkPage in the safeURL params that was needed by the doClose activity, and this has been resolved by adding the primary page name.

INC-218855 · Issue 718833

DSS added to control section collapse on refresh

Resolved in Pega Version 8.8

After update from 8.5, using dynamic layouts that included certain controls (autocomplete/text/dropdown) configured with Refresh-Other Section -> Parent / Top Level Section such as a pyCaseActionArea with Event 'On Change' showed a different behavior: entering a value in the configured text/auto-complete field that leads to the refresh of the top level section will collapse all expanded sections if there is a refresh trigger within the embedded section or dynamic layout of the collapsible layouts. In order to control this behavior, a new DSS has been introduced. By default HonourExpandWhenOnRefresh (owning ruleset Pega-UIEngine) will be set to false to maintain the current behavior of collapse on refresh, while setting it to true will use the older behavior of maintaining expanded sections.

INC-219004 · Issue 719691

Able to trigger a flow action multiple times

Resolved in Pega Version 8.8

Previously it was only possible to trigger a flow action once in a case. Once a search was triggered via the flow action, it could not be triggered another time in the current case context. It was possible to select the local action, but it did not execute. This has been resolved by modifying the getTargetFromContainerItemID API to get the correct target by iterating over the container and checking the passed containeritemname in it.

INC-219310 · Issue 717113

WorkSearchGadget updated in Theme-Cosmos-02-01

Resolved in Pega Version 8.8

The search icon was not working in Cosmos after update, which was traced to the search icon not having an action set. This has been addressed in Theme-Cosmos-03-01, but in this scenario Theme-Cosmos-02-01 was set as the Application definition instead of Theme-Cosmos-03-01. To resolve this, Theme-Cosmos 02-01-01 has been updated to use the newest version of the @baseclass.WorkSearchGadget section.

INC-219444 · Issue 741323

Undo works as expected in Rich Text ToolBar

Resolved in Pega Version 8.8

Clicking undo was not working as expected after cutting and pasting formatted text from Microsoft Word into the Rich Text Editor of the content toolbar. This has been resolved by updating the image in the after editor change event in the save function.

INC-220351 · Issue 715874

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.

INC-220363 · Issue 720118

Additional page sizes available for PDF generation

Resolved in Pega Version 8.8

Support has been added for using page sizes in PDF generation which are supported by the v4 pd4ml jar including A0-A10.

INC-220411 · Issue 724062

Handling updated for BPF in FinishAssignment

Resolved in Pega Version 8.8

After update, executing Wrapup resulted in a 403 error and the operator being logged out of the system with a SECU0017 alert. This was traced to pzBFP being removed from the headers as part of the FinishAssignment activity, and has been resolved with an update to conditionally add/remove pzBFP by checking its value. If it is empty, it will not be added to the form.

INC-220532 · Issue 739700

Property reference retrieves correct values

Resolved in Pega Version 8.8

When a pageGroup was mapped to a pageList through a page and the checkbox "Allow use as reference property in activities" was enabled, the property reference retrieved old clipboard page values and displayed data from prior work objects opened in the browser section. This has been resolved with an update which will then replace that pageList in clientDataProvider with whatever is received from the server.

INC-220715 · Issue 726415

Currency Code updates

Resolved in Pega Version 8.8

A Section configured with an editable currency input using auto-formatting failed to render at runtime if configured using Type -> Number, Symbol -> Currency, Other currency, and Currency -> "USD". The error "Invalid Locale : USD" was logged. This was an unintended side effect of work done to configure currency codes for the Number control, and has been resolved by accounting for the locale settings and handling the condition for the error "Invalid local-USD" so that the the UI rendering appears as expected. In addition, when the Currency control was configured with editable mode "Editable" and "Display value using read-only formatting" checked, read-only formatting generation did not happen for the control. Entering a value and tabbing out caused the ReloadCell activity to return empty content, which resulted in the server returning full HTML markup with a message "Operation Successful". Because the ReloadCell activity handler expected only control markup with formatted value to be returned, the HTML markup containing inline CSS styles in it appeared in the Currency input field on tab out. There was a workaround of unchecking "Display value using read-only formatting" on the control's presentation tab, but this has been resolved by using Post value infrastructure to get the formatted value from the server.

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