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-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.

SR-129156 · Issue 200004

Corrected Data Page parallel loading

Resolved in Pega Version 7.1.8

Data Page parallel loading could not access requester level pages in an activity trying to do property-set from one data page (source) to another data page(target) property. The data page referenced (source) was created in the clipboard, but its value was not set to the target. This was caused by an implementation bug where the data pages of all scopes were put into a thread page directory instead of putting them in their respective directories, and has been corrected.

SR-128963 · Issue 197101

Agent no longer exceeds lock timeout

Resolved in Pega Version 7.1.8

If an agent was accessing a work item for a long time, it was possible to exceed the lock timeout and have an agent on a different node open a new lock and overwrite the first agent's work on the item. To resolve this, mDBOpenTime has been set to persist through passivation.

SR-129239 · Issue 200337

Added handling for Flow not at Task error

Resolved in Pega Version 7.1.8

Flow not at task and flow removed errors were appearing sporadically. This happened when the trigger fired off the commit inside the post-processing called CorrUpdateNoWO and returned a stale copy of the Workobject, and was complicated by an assumption that was trying to iterate over "pzInternalCaseFlow". This has been addressed in the CORRUPDATENOWO activity.

SR-129312 · Issue 198553

Corrected HTML display of characters in reply emails

Resolved in Pega Version 7.1.8

HTML characters were appear in the email body and subject for outbound reply messages. For example, if subject is test, the reply email would display the subject as RE: test<%gt; An HTML reply to an HTML email did not contain these entities/artifacts. Reply emails can now be configured to use HTML format, and the 'HTML' option has been added to the Message Type drop-down on the Response tab of Service Email rule.

SR-132880 · Issue 201431

Design time clarification for radio button configurations

Resolved in Pega Version 7.1.8

Previously, it was possible to configure an on-click event on a radio button in a repeating grid. This configurability was an error - although it was possible to set it up, the actions would not actually fire as intended due to the way the radio buttons work. In order to remove confusion, the actions tab for radio buttons has been removed from design time and checkboxes should be used if on-click actions are desired.

SR-130352 · Issue 199182

Corrected Microsoft Internet Explorer error for opening harness in a popup

Resolved in Pega Version 7.1.8

Configuring a button click to launch a harness in a pop-up with the Microsoft Internet Explorer 11 browser caused the error "Internet Explorer cannot display the webpage." The cause was an errant space included in the pega.u.d.url for this browser, and the GenerateHarnessHTML and GenerateLayout RUFs have been updated.

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