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-D15089 · Issue 485330

Handling added for single quotes in custom DateTime controls when using Export to Excel

Resolved in Pega Version 8.3

A previously resolved issue with the timezone not being appended to datetime when exporting to Excel if a custom control was used has been further updated to better handle single-quote strings in custom DateTime controls.

SR-C91220 · Issue 430362

Modified pzpega_ui_dynamiccontainer to resolve issue with editing the Operator rule form when using IE

Resolved in Pega Version 8.3

The Operator rule form was not opening a second time after being updated in IE. The form worked as expected with other browsers. This has been resolved by modifying the openRuleByKeys function in pzpega_ui_dynamiccontainer to pass a new cloned object to the JSON.stringify function instead of the embedded object.

SR-D564 · Issue 438145

Removed job for column population when it is not needed

Resolved in Pega Version 8.3

While optimizing the data type class properties, the column population job failed with the exception "ERROR - Exception in column population ... column pc1.pzinskey does not exist". Although there was no impact from this error, the SQL exceptions in logs could cause confusion. This has been resolved by updating the system so that if the table has no pzinskey or stream columns, no job will be queued for column population.

SR-D6555 · Issue 457242

Access When check added for pyStartCase privilege

Resolved in Pega Version 8.3

If a privilege was defined in the pyStartCase flow rule and the access role to object assigned a privilege based on 'Access When' (not production level), the user was not able to start a case. This was traced to the havePrivileges RUF passing an incorrect primary page to evaluate the privileges in combination with the 'access when'. To resolve this, the engine API will call tools.getAuthorizationHandle().havePrivilege for each privilege until it finds a match.

SR-D53176 · Issue 541793

Error when adding function filter will persist

Resolved in Pega Version 8.1.8

When an exception occurred while adding a filter in the report viewer, the error was shown but cleared due to an immediate refresh of the parent section. Analysis found that step2 of pzGetFiltersFromContent was failing, after which the error was shown, the section reload happened, and the error disappeared. To resolve the error being cleared prematurely, the pzOnLoadReloadReport control has been modified so that when there are messages on the top level page (pyReportContentPage), a parameter will be set on HarnessContextMgr to not to clear them during the next refresh call.

SR-D18332 · Issue 490989

Enhancements added for scrolling when an overlay is present on the screen

Resolved in Pega Version 8.3

When scrolling the screen with the autocomplete window open, the autocomplete window became disjointed with its field. This has been addressed with an enhancement to improve the visual experience. With these changes, the overlay will be launched at the place where the mouse pointer is located. Earlier, the overlay was launched at the starting of the element on which the launch overlay was configured. Previously, if the parent element was scrolled the overlay used to remain at the same position. With the new changes, the overlay will be attached to the parent element when it is scrolled. In the third use case, when the content was launched dynamically, there used to be a scrollbar in the parent viewport as the viewport expanded. With the new changes, the viewport will remain the same and the dynamic content in the overlay will now have a scrollbar.

SR-D60447 · Issue 522751

Corrected unexpected save warning when switching tabs

Resolved in Pega Version 8.1.8

When using the Interaction Portal, entering case data on one open tab and then switching to another open tab caused the system to display a Save warning message as though the Tab has been closed instead of switched. This has been resolved by updating the system to skip the dirty alert when bPrompt is false in the Ajax Container container case.

SR-C91907 · Issue 433770

Thread context preserved when processing a case in interaction

Resolved in Pega Version 8.3

Thread context was not being preserved correctly when a case was opened from an interaction. This has been corrected.

SR-D76134 · Issue 542160

"Offline" icon shows when simulating offline mode

Resolved in Pega Version 8.1.8

When simulating offline mode by selecting "Settings->SystemInfo->Simulate Offline checkbox" and moving to MyWork, "Offline" did not appear in the header. This has been corrected.

SR-D17919 · Issue 491579

Corrected thread switching when moving between interactions tabs

Resolved in Pega Version 8.3

When using Create New for a Phone Call-Consumer in one tab and Create New for an Outbound Phone Call on another tab, the thread was not changing when switching between the tabs of the interactions. Closing the Outbound call interaction resulted in null pages on the clipboard. This has been resolved by updating the pzpega_ui_doc_tabsupport file so it switches to root document context if called from onActivate function using a flag.

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