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-124313 · Issue 190024

FCM remote case type function restored

Resolved in Pega Version 7.1.8

FCM (Federated Case Management) has a button to discover remote case type, but attempting to use it out-of-the-box generated the error "Remote System is not available. Please check the settings". This was due to a lack of authentication in the Service HTTP rules CaseManagement, and the authentication requirement has been removed.

SR-124382 · Issue 187227

Corrected image resize for RTE

Resolved in Pega Version 7.1.8

In some cases, it was not possible to resize an image in RTE. This was traced to the image plugin setting the height and width for auto resize, and has been changed so the setup and commit function in ckeditor_extras do not set dimensions for auto resize and retain the width and height if specified.

SR-124382 · Issue 185471

Corrected image resize for RTE

Resolved in Pega Version 7.1.8

In some cases, it was not possible to resize an image in RTE. This was traced to the image plugin setting the height and width for auto resize, and has been changed so the setup and commit function in ckeditor_extras do not set dimensions for auto resize and retain the width and height if specified.

SR-124384 · Issue 185899

Stream XML generation and runtime handling enhanced for optional nodes in schema

Resolved in Pega Version 7.1.8

When a stream rule was executed using connect-SOAP and blank data was passed from the UI, a tag corresponding to the XML element marked as optional was being generated. This resulted in those optional properties being unexpectedly created in source systems. To change this, the generation of the Stream XML rule has been enhanced such that at runtime it ignores optional nodes/attributes mapped to properties which do not exist or which have an empty value. NOTE: this new behavior in Stream XML rule generation is effective only with the below DSS configuration (to avoid backward compatibility issues ): Owning Ruleset : Pega-IntegrationEngine Purpose : StreamXML/DetectEmptyProperties Value : true

SR-124385 · Issue 187273

Clicking checkboxes smoothed for Bulk Processing

Resolved in Pega Version 7.1.8

While performing Bulk Processing, if the checkboxes used to select items for processing were marked in rapid succession, not all of the selected items were processed by the bulk action. This was due to the timing of the refresh on the boxes, and this has been adjusted so all boxes are refreshed by a refresh list instead of post value process.

SR-124385 · Issue 193689

Clicking checkboxes smoothed for Bulk Processing

Resolved in Pega Version 7.1.8

While performing Bulk Processing, if the checkboxes used to select items for processing were marked in rapid succession, not all of the selected items were processed by the bulk action. This was due to the timing of the refresh on the boxes, and this has been adjusted so all boxes are refreshed by a refresh list instead of post value process.

SR-124420 · Issue 187126

Flow actions resolved for hidden buttons passing parameters

Resolved in Pega Version 7.1.8

After upgrading, parameter passing to activities from button controls no longer worked and passed an empty string which made other functionality relying on it fail. This occurred due to the default flow action buttons being configured to be hidden, and affected scenarios where a mix of auto and non-auto generated controls existed in old containers. This has been resolved by adding HTML code that specifies inclusion in case of default buttons being hidden.

SR-124450 · Issue 188191

Added alternate method for sorting and filtering listview fragments with Microsoft Internet Explorer 9

Resolved in Pega Version 7.1.8

Using Microsoft Internet Explorer 9, sorting and filtering were not working after upgrade in ListView using the WorkListViewSelector in the Fragment tab of the ListView. This was due to the version of EventListener not being supported for Microsoft Internet Explorer 9 and lower browsers so a check has been added that will call the old methodology of calling window.attachEvent for these functions.

SR-124451 · Issue 185472

Event based subscription processes corrected

Resolved in Pega Version 7.1.8

After migration, "Event" based subscription processes were not firing. In this case, when distributed search was enabled (via following DSS - Pega-SearchEngine . indexing/distributed/index_enabled) and if "Work indexing" was enabled, Business events stopped working. This was due to an incorrect check on the enqueueLightWeight() function and has been corrected to use a blob based table if events fire.

SR-124463 · Issue 186281

Customer Request Header mapping updated

Resolved in Pega Version 7.1.8

A Connect SOAP rule using Custom Request Headers to pass the wsse:Security, wsa:From, wsa:MessageID and wsa:Action fields was failing with the error "The server did not recognize the action which it received." Headers were mapped to a XML stream rule where the root node was mapped to a property, but the mapping was failing due to missing support to add the text node in addition to the elements. This has been fixed with code added to use getChildren() instead of getChildElements().

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