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-132143 · Issue 201187

Enhancement added to allow setting extract directory for BIX

Resolved in Pega Version 7.1.8

An option has been added to override the output directory of the command line BIX extraction. The command line parameter -P allows specifying the desired path by saving a copy of the Extract Rule XML and setting appropriate pyOutputDirectory path value in it.

SR-132265 · Issue 200632

Improved hotfix detection

Resolved in Pega Version 7.1.8

Migrating from ML6 to ML7 was failing with an error reporting the system contained hotfixes that were generated after the release of ML7. This was due to the ML Readiness step incorrectly identifying pre-7.1 rules as having been updated after the upgrade to 7.1.6. This happened when the revalidate and save was run after the release of ML7, which updated the pxUpdateDateTime for the rules in question and led to them being caught by the validation. This was meant to catch hotfixes, and the handling has been improved to avoid this error.

SR-132414 · Issue 201583

Resolved duplicate result column on Decision Table

Resolved in Pega Version 7.1.8

On a decision table rule, checking "Allowed to return values" check box caused an additional Result column to be added to the table configuration if the Microsoft Internet Explorer or Google Chrome browser was used. On saving, this erroneous result column was inconsistent about being removed. This has been corrected.

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.

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