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-132588 · Issue 202025

Corrected Save Rule-Connect-JMS with Global Resource Set

Resolved in Pega Version 7.1.8

Attempting to save Rule-Connect-JMS containing dynamic settings to avoid hardcoded parameter values was failing. This was due to a validation step that wrongly converted formatting warnings to errors, and has been corrected.

SR-132677 · Issue 201726

Resolved decimal property validation error

Resolved in Pega Version 7.1.8

On validation, an extra space was being added to a decimal property which then caused the validation to fail. This was caused by the pzPerformGridAction activity calling the ProcessAction activity with a new parameter page which was not receiving the inStandardsMode parameter value from the original request, leading pzGenerateFormat to assume that the browser is in Quirks mode. This has been fixed.

SR-132895 · Issue 201403

Fixed onchange while offline for PegaMobile

Resolved in Pega Version 7.1.8

If a post value on a checkbox or radio button controlled the visibility of another layout in Mobile, checking or unchecking a checkbox many times or running the screenflow several times while offline caused the visibility based on the post value to stop working. This has been resolved by changing the handling to click events for Checkbox and RadioButton in mobile instead of tap.

SR-132919 · Issue 201479

REST querystring not forced to lower case

Resolved in Pega Version 7.1.8

A Rule-Service-REST.validate activity which forced the query string to lowercase was leading to REST services are not receiving the input values in case of capital or camelCase query strings. To resolve this, the code that fetches querystring name for REST will not convert it to lower case.

SR-133155 · Issue 202487

Modified locking to handle popup switch

Resolved in Pega Version 7.1.8

The lock on a Work Item opened in No Frame Portal was being lost when a Pop up was opened from the Work Item. In NoFrame portal scenarios, moving away from a Work Item releases the lock as per design, but the lock was also being released when a popup was opened. This has been corrected by adding a popup check that will maintain the lock .

SR-128332 · Issue 199072

Added detection for WSDL import failure

Resolved in Pega Version 7.1.8

Issues were encountered while importing WSDL in the ML6 environment while SoapUI was successful using the same SOAP service. This error happened when the WSDLParser.parse(Reader) was trying to read a closed java.io.Reader instance and silently generating an exception. Error handling has been added to report the failure and give an informative message.

SR-128373 · Issue 200522

RTE spellcheck maintains correspondence images

Resolved in Pega Version 7.1.8

After using the RichTextEditor control to edit correspondence, images were removed from the correspondence that was sent if spell check had been run using the control's built in spell check button prior to sending. The issue happened with only YUI RTE in quirks mode. YUI RTE is a deprecated control and is replaced by CKEDITOR in Pega7. The issue is not reproducible in CKEditor.

SR-128463 · Issue 193907

Create KeyRing updated for split schema

Resolved in Pega Version 7.1.8

If a command line script is configured (viz. keyringGen.sh) to encrypt user passwords for prconfig.xml databases using Keyring utility, a prconfig.xml could have three database entries but the keyring tool only prompted for two databases and did not allow encrypting password for the user for the third database. The prconfig.xml file requires very specific location information to run: to resolve this, the variables to hold schema name in case of split schema configuration have been added.

SR-128684 · Issue 194308

Corrected save-as for Activity using API "02"

Resolved in Pega Version 7.1.8

In drop down generation, if a value was empty then adding the selected attribute for the first option assuming no options should have the empty value other than no selection text. To make this work as expected, if the value is empty then the system will add the selected attribute on the option which has empty value to avoid setting first option value to the hidden field.

SR-128738 · Issue 200611

Corrected label text wrap for other template layout for Google Chrome/Firefox

Resolved in Pega Version 7.1.8

Text Wrapping for labels was not working for layout which uses other template with the FireFox and Google Chrome browsers, but was fine in Microsoft Internet Explorer. This has been fixed by setting the other style to White-Space:normal.

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