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-207996 · Issue 709665

Check added for parent case dependency if deferred-save is used

Resolved in Pega Version 8.8

After updating the status of a parent case to "Pending-ChildCaseDependency", the wait shape for the child case that should have been triggered by the status did not work and the child case remained on hold. This was a missed use case for the pxCheckFlowDependencies activity where defer-save operations on Index-AssignDeps class was not considered, and may happen when the Queue Processor is evaluating the dependencies while instances to Index-AssignDeps are not committed yet. To resolve this, code has been added to check the entry of the parent case dependency in deferred-save if its not present in Index-AssignmentDeps table.

SR-C79205 · Issue 416400

OnChange event only triggered on date field when value changes

Resolved in Pega Version 8.1.3

After configuring the onchange event for a date control field with some action, clicking on the Date picker option and selecting the same date triggered the onchange even when the value had not changed. This has been resolved by updating the code to store the previous value and check for a value change before firing the change event.

INC-176757 · Issue 657785

Interaction History properly saved when running strategy on a different data flow

Resolved in Pega Version 8.7

Customized Interaction History properties that had been added to pyInteractionHistoryConfiguration and pyDefaultWorkingSet and saved into the PR_DATA_IH_FACT table were not being saved properly after upgrading from 7.3 to 8.3. This was a missed use case and has been resolved.

SR-B12737 · Issue 283588

Resolved harness error after using pagination 'load more'

Resolved in Pega Version 7.3

After using the Pagination 'load more' option and clicking on any of the newly loaded items, a blank harness was opened. This was traced to missing change tracking data for the newly loaded rows, and has been corrected.

SR-B12737 · Issue 282869

Resolved harness error after using pagination 'load more'

Resolved in Pega Version 7.3

After using the Pagination 'load more' option and clicking on any of the newly loaded items, a blank harness was opened. This was traced to missing change tracking data for the newly loaded rows, and has been corrected.

SR-B40177 · Issue 297056

Resolved harness error after using pagination 'load more'

Resolved in Pega Version 7.3

After using the Pagination 'load more' option and clicking on any of the newly loaded items, a blank harness was opened. This was traced to missing change tracking data for the newly loaded rows, and has been corrected.

SR-B43621 · Issue 300812

Back/Previous years calculation fixed to use current year

Resolved in Pega Version 7.3

In the year dropdown for Date control, the number of back/previous years was calculated based on the selected year and not from the current year. The calculation logic has been fixed to resolve this.

SR-B7143 · Issue 281865

Div fixed for Add button using GridAction section include

Resolved in Pega Version 7.3

After upgrade, using the "Add" button configured as a section include with pzGridAction caused UI issues. This was due to pzGridAction (@baseclass) not closing the div tag properly after calling pzGadgetInclude, and has been fixed.

INC-154189 · Issue 617247

Harness used to determine read-only for button/text input

Resolved in Pega Version 8.4.4

If a button/text input was configured to always be editable in a section by using the /v1/cases/{ID}/pages/{pageID} API (say i.e PageID as Review), the button/text input was always returned as readonly. This was due to the API being hardcoded to return readonly info, and has been resolved by updating pzGetPageDetails to not force read-only and let the harness configuration decide the behavior.

INC-138840 · Issue 599980

Data-Summary reports default will not use the rule resolved setting

Resolved in Pega Version 8.4.4

An intermittent issue was seen where a query could become stuck for ~2 hours in the database. This has been resolved by setting the default for Data-Summary reports to not use the rule resolved setting.

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