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-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-132538 · Issue 201237

Updated RD handling for WorkBasketAssignments

Resolved in Pega Version 7.1.8

After upgrade, if the Assign-WorkBasket pyWorkBasketAssignmentsDefinition report definition included the WHERE criteria .pxSystemFlow== 'FALSE', workbasket assignments for existing cases were not displayed in the harness. This was due to the new PXSYSTEMFLOW column in the pc_assign_workbasket DB table not properly handling this criteria, and a check has been added to resolve this.

SR-132547 · Issue 200946

WAR file updated for WebSphere

Resolved in Pega Version 7.1.8

The web.xml file within the prweb.war file has been updated with the resource references that are needed to run within WebSphere.

SR-132569 · Issue 201349

Corrected portal refresh after chart unload

Resolved in Pega Version 7.1.8

When a chart is unloaded, a separate request was sent to the server to remove all chart-bounded data pages, i.e. pzRuntimeChartCleanup. If nothing is returned, the ActivityStatusSuccess Message was seen instead of the Work Item when the portal was refreshed. The API has been updated to return the correct information.

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.

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