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-B9662 · Issue 282622

Silverlight version upgraded and URL obfuscation error fixed

Resolved in Pega Version 7.3

The "Create Merge Document" functionality failed with error "Silverlight Control ERROR in 'ProcessHttpResponse'" when when the Pega node was accessed via load balancer. To correct this, the SL Pre-Reqs installer version has been upgraded to the MSI version which supports automated installations and a URL obfuscation error in section WordMergeSL has been corrected.

SR-B9718 · Issue 286254

Corrected picking for mobile circumstanced harness

Resolved in Pega Version 7.3

On mobile devices the circumstanced version of tablet was getting picked instead of the mobile device. The invoke addSectionForOfflinePackaging_X method has been updated to resolve this.

SR-B9780 · Issue 286188

work object progression fixed after cancel/close with errors

Resolved in Pega Version 7.3

A repeat grid's modal dialog could be cancelled or closed without correcting the validation error fired by a field in it, but afterwards no actions could be performed on that specific work object even if the error was then fixed. This was caused by Messages added onto the pyWorkPage not being cleared on click of cancel if followed by clicking on grid pagination actions, and has bene resolved by changing the cancelmodal method from ModalButtonSubmit to ModalButtonCancel.

SR-B9879 · Issue 278433

RTE linkbox input handling corrected for modal windows

Resolved in Pega Version 7.3

In an "inline editable" grid with 'click to edit' selected, clicking on the RTE link inputbox in the modal window caused the grid row to be submitted as if the click took place outside the grid. The gridEventHandler has been updated to correct this.

SR-B9916 · Issue 283675

Hyperlink works on custom HC login page

Resolved in Pega Version 7.3

In a Hybrid Client App with a custom login page, a simple HTML link which calls the function to load the mashup code for the gadget worked in the browser but not in the HC. This was caused by window.open not working inside HC. To enable this, the _launchPopup api of compositegadgetmgr.js has been modified to use launchbox.Browser.start instead of window.open and the isCookieConsentRequired API has been updated to return false for popup case.

SR-B9998 · Issue 279141

Improved handling for apostrophe in email addresses

Resolved in Pega Version 7.3

In order to improve mail handling, the system will now only remove the the starting and ending apostrophe in an Email address and will not strip apostrophes in the middle of an address.

SR-B7729 · Issue 277669

Resolved file upload error for locales with special language characters

Resolved in Pega Version 7.3

Uploads to Pulse were failing when the file names or file paths contained special Turkish characters. This was an issue with the conversion to lower case changing the length of the string for some locale packages and has been resolved by swapping the call to string.toLowerCase for a call to StringUtils.indexOfIgnoreCase.

SR-D47018 · Issue 517032

Corrected parameter being encrypted during change portal configuration

Resolved in Pega Version 8.2.5

After configuring a changePortalLayout control using .pyDescription as property, trying to switch the portal was throwing a error page. The same configuration worked in earlier platform versions. This was traced to recent updates where the activity parameter ended up being encrypted along with the activity name, and has been resolved by removing the parameter from encryption input and adding it to encryption output.

SR-D5904 · Issue 511600

Discard changes dialog now showing for local actions

Resolved in Pega Version 8.2.5

After having modified case data without saving and clicking on a menu entry (left menu, search, ...), the system shows a dialog box to ask the user to confirm it is ok to discard changes. However, this confirmation dialog did not work with local actions, leading users to lose their work without any warning nor any way to step back. This was traced to a difference in the dirty form check, which was not present when launching a local action from a case. An enhancement has now been added to the handleMenuAction js function in pypega_ui_harnessactions.js which will perform a dirty form check with a prompt.

SR-D24527 · Issue 504402

Improved requestor cleanup

Resolved in Pega Version 8.2.5

Batch- and Browser-type Requestors were building up over time in both the Admin Studio and in the PegaRULES log and not removed until the system was restarted. This has been resolved by adding two extra cleanupRequestor calls to the Email Listener implementation.

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