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-129278 · Issue 568856

Date range filter error resolved

Resolved in Pega Version 8.2.8

When using different locale settings, an "Invalid date" issue was seen when selecting a value for a date range filter. This has been resolved.

INC-129388 · Issue 571375

Check for mobile added to Pega Client for Windows time control

Resolved in Pega Version 8.2.8

When attempting to enter time using the out of the box time control in Pega Windows Client application, the control became stuck and continued to show on the UI even when screens were progressed. If the control was marked as a required field, this was a blocker. This was due to the 'validation_validateFromUIEvent' overlay invoking the 'pega.util.Event.getEvent()' function: this function was trying to get the events by traversing all the way to the event initialization, but the process was timing out on mobile/touchable devices and returning the parent event as undefined. Because 'pega.util.Event.getEvent()' was undefined, the validation_validateFromUIEvent caused js errors. To resolve this, a check for mobile has been added to the validation.

INC-129517 · Issue 572490

Support added for Ajax container refreshCaseSections

Resolved in Pega Version 8.2.8

The Refresh/Visibility Condition in Dynamic Layout was not working in the Interaction portal, but did work in a Stand alone service case. This resulted in the summary area not being refreshed when a case was opened in a new tab, which is a new feature supported in Cosmos, leading to a post value used in the case processing area to not be present in the Summary panel on blur of the input field. This was due to the use of the new Ajax container, which did not yet have support for all the out-of-the-box actions such as Refresh-Section or Refresh-Condition. That support has now been added by way of the javascript API pega.u.d.refreshCaseSections.

INC-129603 · Issue 568215

Calendar Mode accessibility enhanced

Resolved in Pega Version 8.2.8

Accessibility has been added for datetime control's calendar mode by adding alternative text and an aria-label for the image icon with a value from fieldvalue "Choose from calendar".

INC-129848 · Issue 580457

Refresh handling added for cancel 'add item' while offline

Resolved in Pega Version 8.2.8

When using iPad and iPhone offline, filling in one required field, hitting submit (click action: 'Add item') without filling in a second required field, and then hitting cancel resulted in a blank record being added. Clicking the cancel button first without clicking submit before did not add the item. This was traced to the underlying repeating dynamic layer being refreshed during the submit and adding the record, and has been resolved by adding a refresh for the cancel button process as well.

INC-130011 · Issue 571834

Resolved stale reference error when swapping stages with drag and drop

Resolved in Pega Version 8.2.8

If user swapped stages (2nd stage to 1st stage) using drag and drop and then added a participant or role in the stage, a Pega blue screen appeared. This was traced to using a grid with reorder and an inner grid in the cell. On drag and drop, the grid reference object was stale and not in sync with the latest table. To resolve this, code has been added to reinitialize the inner grid on drag and drop.

INC-130090 · Issue 573263

Added handling for sourced radio-buttons group rendered in an inner iframe

Resolved in Pega Version 8.2.8

When using a radio button sourced with a pxTextinput using a Local List 'Yes' and 'No', the Assertion conditions were populated with incorrect data while a test scenario was being recorded, causing the test case run to fail. This was traced to the radio buttons being inside an iframe (dynamicContainer): when the scenario test was run, the radio-buttons group was rendered in an inner iframe that caused the document to refer to the outer document on the webpage instead the inner document. This has been resolved by adding handling to get the OwnerDocument of the DOMElement in domUtils's getDOMElementValue() and call getElementsByName on itso the references are correct.

INC-131225 · Issue 579732

Child cases correctly created on mobile app

Resolved in Pega Version 8.2.8

After upgrade, creating a child case from the device generated the error "Failed to reset case type. Not starting optional process : undefined" when launching a "nestedRDL" case and clicking on the "CreateCase1" button on the top. This has been resolved by updating the harness action API to read the harness purpose from DOM instead of the harness context for the HC case.

INC-131523 · Issue 573852

Parameters to Property UI Field available in report

Resolved in Pega Version 8.2.8

When using a parameterized control like Decimal for a property in the UI control of the Property rule with inputs given to the parameters, once the property was optimized and referred to in Report Definition, the value was rendered using the Control with parameters defined in its rule form. In the report, the column was not rendered as it is designed on the property rule, but the same worked as expected in a section. This behavior was a change after upgrade. This was traced to "pyPropertyName" being added to the stepPage as part of the pzMergeAutoGenForProp Activity, and has been resolved by adding it to the stepPage only when it is an auto-generated control.

INC-132176 · Issue 588807

Cache cleared before PDF generation to ensure proper fonts

Resolved in Pega Version 8.2.8

The font File OCRAEXT.ttf added at location "/usr/local/tomcat/fonts" was not being picked when the PDF was generated via an agent execution. When the same activity was run manually, the font issue was sporadic. Investigation showed that when multiple apps use the same props directory but different fonts directories, the handling would sometimes cause one app to use another app's props file with the result of the improper fonts mapping. To resolve this, an update has been made to clear the cache before PDF generation starts to ensure the library reads the proper fonts.

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