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.

INC-143320 · Issue 602281

Support added for email addresses with hyphen in domain name

Resolved in Pega Version 8.3.5

When attempting to enter a email with a hyphen '-' in the domain part of an email ID ([email protected]), the reply button was getting disabled. This was caused by the regex validation implemented in the "pzValidateEmailAddress" (Work-Channel-Triage-Email) standard activity not covering all the possible cases. To resolve this, regex has been changed to instead use a platform-provided rule to ValidateEmailAddress.

INC-144399 · Issue 599715

Custom dropdown controls updated for classnames

Resolved in Pega Version 8.3.5

After upgrade, a customized format for Dropdowns was not picked up. This was due to recent changes made to Class name attributes to ensure they are populated for all controls, and was caused by the CSS selector not picking the necessary DOM element. This has been resolved.

INC-136793 · Issue 585605

Updates made to display busy indicator correctly in Google Chrome 84

Resolved in Pega Version 8.3.5

The Pega busy indicator was not displaying correctly in Google Chrome 84 due to changes in that browser. The needed updates have been made to adjust for these changes.

INC-143795 · Issue 599474

Acdatasource_driver call updated

Resolved in Pega Version 8.3.5

When Acdatasource_driver was invoked directly, an exception was generating indicating "This activity may not be called directly from input". This was related to recent refactoring work done, and has been resolved by modifying the code to call the acdatasource_driver activity through pzRunActionWrapper.

INC-138309 · Issue 591150

Added busy state reset to reenable buttons after custom frame cancel

Resolved in Pega Version 8.3.5

When using a custom iFrame in a section that called a third-party URL, clicking on cancel for the popup "Do you want to stay on this page or leave it?" caused the screen to freeze. This was traced to the cancellation of the dirty page setting a busy state which disabled all the buttons and did not have a path to recovery. This has been resolved by updating the busy state so it will reset when the user chooses to cancel the changes and reenable all the buttons.

INC-137100 · Issue 605837

Added predictive text handler for Japanese on iOS

Resolved in Pega Version 8.3.5

The autocomplete function was not working well in MobileView when using Japanese IME on iOS. This has been resolved by adding a new input handler for IOS mobile, which will be triggered when predictive text is selected in mobile.

INC-142248 · Issue 601766

Added safe check for ActivateTabs

Resolved in Pega Version 8.3.5

After configuring a data transform action for a close icon to set a requestor level data page value and a parent-level dynamic layout was configured with a refresh when condition to track this Data page property, pzMicrodynamicContainer was throwing a null pointer exception after this refresh occurred indicating the tag name passed to isRegularTarget function was invalid. This has been resolved by adding a safe check to ensure that activateTabs is called only for tab based Ajax containers.

INC-138968 · Issue 594170

ARIA landmarks added to put dynamic layout in tab order

Resolved in Pega Version 8.3.5

As part of W3 accessibility specifications, ARIA landmarks have been added to dynamic layouts to direct tabbing focus. If the role type is "landmark" or "document", tabindex=-1 will be added, and for component widgets tabindex=0 will be added unless it is a non-focusable element like Alert, log etc.

INC-142141 · Issue 595676

Call to OnBeforeWindowClose changed to asynchronous

Resolved in Pega Version 8.3.5

After accepting a chat and accidentally closing the interaction portal with the active chat, the active record was left in an unresolved state that did not allow bot interaction until the 720 minute bot timeout was reached. This was caused by the pyOnBeforeWindowClose activity not being called as expected, and was traced to Google Chrome blocking the synchronous request needed. To resolve this, the call has been converted to an asynchronous request.

INC-137510 · Issue 591295

CKEditor Source edit with formatting resumes process automatically

Resolved in Pega Version 8.3.5

Buttons on the harness were freezing after applying format using CKEditor when source mode was turned on in rich text editor. Investigation showed that on clicking the source button, after applying styles, the events were being paused and were not resumed automatically. This has been resolved by adding changes to resume the event queue.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us