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-D53488 · Issue 520014

Tab layout group handling improved

Resolved in Pega Version 8.2.6

A difference in scrolling speeds between left and right arrows and an issue with the cursor correctly being redirected to mandatory fields were traced to errors in the tab layout group handling. The right scrolling issue was due to the calculation for right tab movement being incorrect in certain resolutions with relatively positioned elements, and has been corrected. The cursor redirect was caused by an error in the layoutgroup focus when used inside a screen flow where the first focus goes to the screenflow navigation on load, and has been resolved by adding a try catch for an invalid selector in case of a div error.

SR-D53725 · Issue 516829

Corrected column alignment for TextExtraction model in IE

Resolved in Pega Version 8.2.6

When using the Microsoft Internet Explorer browser, vertical alignment problems were seen in the TextExtraction Model: 'Entity type' column. This was related to recent changes made to support Flex, and has been resolved.

SR-D54034 · Issue 520008

Check added to only show active popover

Resolved in Pega Version 8.2.6

After selecting the autocomplete value and going to calendar field to select the date value, scrolling on the calendar field caused the calendar popup to reappear but it was not possible to select a date value.This was traced to the DOM using _popOversContainer ID for both the fields, autocomplete and date calendar. Removing the autocomplete caused the behavior to work as expected. To resolve this, the isActive() check in popover.js has been modified to reposition and show a popup only when it is active.

SR-D54068 · Issue 518160

Calendar edit properly disabled when set to no text entry

Resolved in Pega Version 8.2.6

Clicking the input box of a date control used as Date+calendar popped up the calendar even when the calendar control was disabled and "Allow text entry" was set to No. If "Allow text entry" was set to yes, the entire calendar was disabled. To resolve this, the system has been updated to disable calendar control when 'Allow text entry' is selected to No in the presentation tab.

SR-D54594 · Issue 521634

Enhancement added to customize the clearing of error messages when performing modal actions

Resolved in Pega Version 8.2.6

Opening any modal dialog, for example adding a row in Table/Grid layout, cleared any existing validation error messages on UI screen. In order to make this behavior customizable, a flag has been introduced to control the clearing of error messages from primary pages on grid actions. Updates have been made in the ui_grid, ui_grid_dragdrop and ui_repeatlayout JS files to include this flag in activity parameters and the pzdoGridAction activity has been modified to consider the flag.

SR-D54785 · Issue 524803

Corrected grey area seen when dragging tabbed layout Smartinfo scroll

Resolved in Pega Version 8.2.6

When using Show Smartinfo in a tabbed layout group, a grey area was seen in the harness while scrolling. Scrolling up so that Smartinfo was out of view port caused another scroll bar to seen: one scrollbar was attached to the workarea div and the other to the body, and the gray area issue was only reproducible when explicitly dragging the (second) scrollbar attached to the body. To resolve this, if the popup is below the viewport using Smartinfo and the height calculated is negative, then the popup's height will be set to 0px.

SR-D54920 · Issue 518273

Extra checks added for pasting Excel content to RTE

Resolved in Pega Version 8.2.6

Copying content from Excel into RTE pasted an image of the content either instead of the actual content or in addition to the actual content. This was traced to the handling of the isHTML flag: the flag should be set to true when there is HTML content in the datatransfer item or while pasting images (!isHTML is the condition in if). However, the sequence of the data items in the datatransfer can change depending on the browser/OS, causing isHTML to sometimes not be set to true before it is used in the condition while pasting images. To resolve this, changes have been made to the pasteHandler in the pzpega_ckeditor_extras file so proper checks are made to figure out the type of data from the clipboard that is being pasted.

SR-D55233 · Issue 520720

AJAX container handling updated to use Harness context API

Resolved in Pega Version 8.2.6

After creating a service case and adding a task to the case, a button configured to refresh the section on a condition worked correctly the first time but did not respond to a second click. This was traced to the tasks being located in two different Ajax containers: in this usecase the condition evaluation logic related to actions was still using the regular DOM API and using the context from the first AJAX container. To resolve this, the system has been updated to use the harness context API pega.ctx.dom.getElementsByName instead of DOM API to resolve the necessary elements from the correct AJAX container.

SR-D55295 · Issue 518360

ISO country codes updated

Resolved in Pega Version 8.2.6

Support has been added for two letter ISO 3166 country codes, and the list has been updated.

SR-D55781 · Issue 523204

Corrected Microsoft Internet Explorer 11 view for Data-Corr-Letter attachments

Resolved in Pega Version 8.2.6

When opening an attachment of type “Data-Corr-Letter”, the document showed correctly in Google Chrome but in Microsoft Internet Explorer 11 was displayed in a small frame that did not allow viewing the entire content. This was traced to a legacy HTML rule with an IE8 emulation meta tag to support OCX, and has been resolved by adding a 'when' condition for the meta tag.

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