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.

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.

SR-B17037 · Issue 289405

Handling added for SP initiated logins

Resolved in Pega Version 7.3

Attempting a Service Provider (SP) initiated login request caused the error "The Response did not contain any Authentication Statement that matched the Subject Confirmation criteria" to appear. This was due to the code used to identify whether the flow is IDP initiated or SP initiated SSO not having the handling for encrypted assertions. The system has now been updated to look for the relay state in the DB: if an entry is present then the SSO flow will be SP initiated, otherwise it will be IDP initiated.

SR-A99678 · Issue 272068

Chart clipboard page unloaded properly in tab refresh

Resolved in Pega Version 7.3

When a portal tab containing a chart was refreshed due to use of the "refresh when active" tabbed layout checkmark, the old chart clipboard pages remained. This was due to a missed use case, and has been fixed.

SR-B3591 · Issue 277488

Unit Test Case for DataPage localized for comma decimal indicators

Resolved in Pega Version 7.3

When using Dutch language localization, the use of a comma in a decimal number caused a parsing error when creating a Unit Test Case for a DataPage. Proper handling has been added to handle this localization format.

SR-B3591 · Issue 278006

Unit Test Case for DataPage localized for comma decimal indicators

Resolved in Pega Version 7.3

When using Dutch language localization, the use of a comma in a decimal number caused a parsing error when creating a Unit Test Case for a DataPage. Proper handling has been added to handle this localization format.

SR-B44878 · Issue 301248

displayHarness context maintained if established before passing pageName

Resolved in Pega Version 7.3

The runDataTransform() was running in the context of what was considered an incorrect page when called from the pre-js function of a Question shape when opening the case from the worklist. This was caused by using pega.offline.runDataTransform and passing the pageName parameter as null in an attempt to use the primary page context, but the system defaults to using the context of pyDisplayHarness instead of pyWorkPage when the pageName parameter is null. In order to support this configuration, the PreJS function of a question shape called from the displayHarness will maintain the context as displayHarness for pega.u.d.PrimaryPageName when passed.

SR-B14774 · Issue 285008

Optional Process Child Case correctly sets ObjectClass

Resolved in Pega Version 7.3

When creating a Child Case from an Optional Process on the Case Type Rule, the ObjectClass of WorkPage did not update to the object class of the child case. The proper class was set when generated using an Automatic Process on the ObjClass. This has been corrected by using a performAssignmentCheck before acquiring work object.

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