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-129955 · Issue 199160

Extraneous 'save changes' popup removed from PDF viewer

Resolved in Pega Version 7.1.8

A popup asking "Do you want to save changes to pdf before closing" was appearing when closing an unmodified PDF generated from PRPC using the concatenateEforms feature. This was caused by an unneeded appearance setting, which has been removed.

SR-130696 · Issue 199065

Updated config query for VBD date/time support

Resolved in Pega Version 7.1.8

When following the recommendation to add required date-time columns on VBD configuration tables for Oracle Golden Gate set up, the VBD configuration could not be saved to a database table from PRPC. This has been resolved by adding an updated configuration query to support replication.

SR-130731 · Issue 198828

HTTPS support added to DSM applications

Resolved in Pega Version 7.1.8

If the PRPC instance is accessed via HTTPS and the DSM applications (ADM & VBD) are installed on the same Tomcat configurations, the DSM services landing page did not provide the ability to say if the services were accessible via HTTPS. This is now possible through an added configuration option on the landing page to enable secure connection.

SR-130796 · Issue 197804

Enabled restore of persisted Application requestors

Resolved in Pega Version 7.1.8

Prior to this change, service requestors could not be restored from their passivated state because of a code change introduced in PRPC 5.4. This was generally not a problem for most customers, as service requestors tend to be stateless and short-lived. Stateful, long-lived service requestors such as Verizon do need to be restored to their previous state, however. This change retracts the prior fix that prevented that from occurring.

SR-131929 · Issue 200525

Added ability to extend CDM logic with custom shapes

Resolved in Pega Version 7.1.8

In order to support adding customized shapes to strategy rules in the CDM layer, the extension point has been opened by enabling some configurations, mainly for canvas extension and shape validation.

SR-132123 · Issue 202411

Auto-resize parameters added to Pega Image Viewer

Resolved in Pega Version 7.1.8

When a large TIFF image (over 2,000 x2,000 pixels in size) was loaded into the Pega Image Viewer control embedded into any section, both horizontal and vertical scroll bars appeared and the Fit-To-Width button of the control needed to be clicked to scale down the image enough to eliminate the scroll bars. In order to smooth image display, the system now provides image size initialization during startup using a parameter 'ImageSize' in the HTML which accepts three strings: Normal, BestFit, or FitWidth.

SR-132507 · Issue 201175

Upgraded Apache Commons FileUpload

Resolved in Pega Version 7.1.8

In order to enhance system security, Apache commons-fileupload-1.2 has been upgraded to commons-fileupload-1.3.1.

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

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