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-217304 · Issue 714589

Regex handling updated for non-empty inputs

Resolved in Pega Version 8.8

Expression evaluation for non-empty regex has been updated to include testing for unicode characters to align with recent updates made to CKEditor.

INC-217655 · Issue 723566

Resolved validation check freeze for Dynamic Layout Group

Resolved in Pega Version 8.8

After creating a multi-step form where step 1 had a Dynamic Layout Group(tabbed) that used form fields configured with validations, clicking next with empty/invalid values in the form intermittently caused the screen to freeze and a javascript exception was logged. This was traced to a missed use case related to templates in the childNode, and has been resolved by adding the necessary safe checks in lgtemplate and lgcelltemplate.

INC-217680 · Issue 717605

Tab name displayed correctly in embedded mashup portal

Resolved in Pega Version 8.8

"Work Item" was given as as the tab header instead of the Case ID## when:a case link was clicked/opened in an application embedded in an external site (IAC). This was traced to the pega.desktop.support.doGadgetAction function not calling the regular handleGadgetLoad function in this scenario, and has been resolved by explicitly directing work items opened in a multi-doc mashup portal to use handleGadgetLoad.

INC-217821 · Issue 719168

Ensured data refresh for cascading dropdown controls

Resolved in Pega Version 8.8

When using two cascading dropdowns where the options within the second dropdown depended on the selection in the first dropdown, making both selections and then going back to change the selection in the first dropdown appeared to allow changing the selection in the second dependent dropdown, but autocomplete was still holding the previously selected value in memory even though the source property changed. This caused an unexpected behavior when the selections were submitted. Investigation showed that changing the value of the first dropdown triggered an API call to the Refresh assignment action that updated the value, but changing the first dropdown did not cause a refresh call to set the value back to blank in the second dropdown. This issue was seen when the dropdown values were hard-coded but did not occur if each dropdown used a data page. This has been resolved by ensuring the dependent property in a cascade is reset when the source property changes.

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.

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