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.

SR-C45846 · Issue 391842

Improved handling for parsing multiple formats of DateTime

Resolved in Pega Version 8.1

In order to further correct an issue with DateTime formats, the system will now use the parseAsDateTime and parseAsDate functions to properly handle the parsing of the date and date time values. The Pega format will be tried first, and if that doesn't work then the UTF formats will be used. If there is still an issue, the system will call back on the original parseAsXSDDateTime/Date which should catch all cases. An exception will no longer be thrown until after all parsing methods are tried.

SR-C62820 · Issue 404256

Fixed dropdown value reset on Microsoft Edge 41 browser

Resolved in Pega Version 8.2

When using the Microso9ft Edge 41 browser, any value selected in a dropdown was getting reset to the placeholder. Also, if there was a dropdown with required validation, then after the selection was made a reset happened and fired a validation message. This was traced to the selectedIndex of dropdown not getting updated properly in Edge if the option was added dynamically with selected attribute, and has been fixed by setting selectedIndex to dropdown in constructOptions function of pzpega_ui_dropdown.js.

SR-C65633 · Issue 408042

Improved handling for parsing multiple formats of DateTime

Resolved in Pega Version 8.2

In order to further correct an issue with DateTime formats, the system will now use the parseAsDateTime and parseAsDate functions to properly handle the parsing of the date and date time values. The Pega format will be tried first, and if that doesn't work then the UTF formats will be used. If there is still an issue, the system will call back on the original parseAsXSDDateTime/Date which should catch all cases. An exception will no longer be thrown until after all parsing methods are tried.

SR-D26642 · Issue 483436

Layout Refresh on Value Change works with Property Empty

Resolved in Pega Version 8.3

Layout refresh on value change was working when changed from "Yes" -> "No" or "No" -> "Yes", but was not triggering the refresh when the first change was from Empty to "Yes" or "No". To resolve this, the pre-replacement event validationType attribute on this function has been removed so an empty value will be processed.

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.

SR-D17919 · Issue 491582

Corrected thread switching when moving between interactions tabs

Resolved in Pega Version 8.4

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.

INC-147457 · Issue 621710

Elapsed time in Work History Table includes sub-flow

Resolved in Pega Version 8.6

Elapsed times were not captured when an assignment was in a wait shape followed by a utility which set a ticket and moved the assignment to a sub-flow. Investigation showed that when flow execution is in a sub-flow and a ticket is raised, the assignment in sub-flow was removed but audit history was not captured. To handle this scenario, the functions pzCleanSplitForTicket and pzRemoveFlowForTicket have been added, and FlowMethodBody FUA has been modified to include pzCleanSplitForTicket instead of CleanSplit.

INC-146098 · Issue 607792

Keyboard shortcuts work in Decision Trees

Resolved in Pega Version 8.6

Keyboard short cuts in Decision Trees used to copy/paste by holding ctrl button in Decision Trees were not working. This was an unintended side effect related to changing non-auto grid to an auto-generated hierarchical table to make the Decision tree rule form multi-browser compatible, and has been resolved by adding cut/copy/paste/insert-after/insert-before functionality to the decision tree context menu.

INC-146098 · Issue 633722

Keyboard shortcuts work in Decision Trees

Resolved in Pega Version 8.3.6

Keyboard short cuts in Decision Trees used to copy/paste by holding ctrl button in Decision Trees were not working. This was an unintended side effect related to changing non-auto grid to an auto-generated hierarchical table to make the Decision tree rule form multi-browser compatible, and has been resolved by adding cut/copy/paste/insert-after/insert-before functionality to the decision tree context menu.

INC-146098 · Issue 633723

Keyboard shortcuts work in Decision Trees

Resolved in Pega Version 8.5.4

Keyboard short cuts in Decision Trees used to copy/paste by holding ctrl button in Decision Trees were not working. This was an unintended side effect related to changing non-auto grid to an auto-generated hierarchical table to make the Decision tree rule form multi-browser compatible, and has been resolved by adding cut/copy/paste/insert-after/insert-before functionality to the decision tree context menu.

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