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-192159 · Issue 691022

Handling added for designtime page used in runtime

Resolved in Pega Version 8.7

After creating a survey with branch Create survey cases routed to different actors, some cases missed the assignments and were left idle with no access to progress. Survey cases (with branches) having the 'when' conditions in flow connectors experienced this intermittently in production. This was traced to the use of D_pzSurveyPage data page called from the ProcessUpdate data transform while creating the survey: this data page is for design time and should not be used at runtime as it requires design time pages like CaseTypePage which will not be available at runtime. To resolve this issue for runtime, in Step 3 of pzGetAllConnectors, pyClassName will be copied from the step page and set for pzGetConnectorsForDecision.

SR-118159 · Issue 174990

Improved handling for Case notes when spellchecker is active

Resolved in Pega Version 7.1.7

If a lot of content was added for a case Note, clicking on the Notes tab caused the text to display in a big yellow box which could not be dismissed. This was traced to the spell checker not properly handling RTE's hidden textarea field, and the code has been modified to correct this.

SR-119909 · Issue 176760

Fixed page toggle when a grid contains an error

Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7

It was not possible to navigate to a different page in a grid when a validation error existed on any page.The error could be corrected if it occurred on the current page and paging ability would return, but if the error as in a different page it was not possible to navigate to correct it. This was traced to code which prevented moving to another page if there was an error on refresh. While there was a workaround, the code has been updated to allow moving to another page unless the error occurs on the current step page.

SR-A3384 · Issue 212375

Added negation(!) handling for 'when' functions in icon control

Resolved in Pega Version 7.2

After migration, the 'when' rule was not evaluating negation(!) correctly in the deprecated icon control. This was caused by changes in the assembly logic stream generation treating 'when' expressions differently when negation is present, and has been resolved by passing the compiled 'when' rule to the handleEvaluateWhen function.

SR-A3384 · Issue 211149

Added negation(!) handling for 'when' functions in icon control

Resolved in Pega Version 7.2

After migration, the 'when' rule was not evaluating negation(!) correctly in the deprecated icon control. This was caused by changes in the assembly logic stream generation treating 'when' expressions differently when negation is present, and has been resolved by passing the compiled 'when' rule to the handleEvaluateWhen function.

SR-D28859 · Issue 502006

Declare expressions validation message persists when clicked

Resolved in Pega Version 8.4

After configuring a section with fields and validation through validate rule where some of the field properties were sourced in declare expressions, clicking on the validation message caused it to disappear. Investigation showed that when validations are displayed on the screen, clicking on any of the fields which have calculatexpression as validationtype triggers a check for errors on the field with caluclateexpression validationtype. As there were no errors, the existing validation message on the field was removed. To resolve this, the system has been updated so that If the calculate expression does not have any error and the field has existing validations, the removal of validation message will be skipped.

INC-185847 · Issue 669526

Handling added for disabling weekends when no weekends are available

Resolved in Pega Version 8.7

A browser exception was generated while selecting the option “Disable weekends”. This was traced to a malformed array of weekends in a scenario where the Data-Admin-Calendar instance had all business days checked (i.e., no weekends). To resolve this, DatePickerAssembly and pzGenerateDatePicker have been updated to handle the case when there are no weekends available in the Data-Admin-Calendar instance.

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.

SR-D29809 · Issue 505257

Extra <p> tag removed when not needed in RTE generation

Resolved in Pega Version 8.4

The RTE was generating an extra <p> tag in the Review harness or when the RTE was non-editable, causing alignment issues in the UI when RTE was displayed using inline dynamic layout with a textarea. This has been corrected.

SR-118725 · Issue 174420

Corrected focus for filter window using WAI

Resolved in Pega Version 7.1.7

With WAI enabled for work object - Audit window- History table - Time column, clicking on Filter window did not properly move the focus to the first element i.e., Add/Remove columns link. The getFirstInputElement API has been modified to fix the reported issue.

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