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-A1705 · Issue 205449

Fixed scrumboard intermittent failure

Resolved in Pega Version 7.1.9

After upgrading, it was seen that the scrumboard would intermittently fail to load, partially displaying and then hanging if the columns did not fit within the window boundaries due to the number of elements. This was traced to an error in the functionality that resizes parts of the scrumboard, and has been fixed.

SR-A4995 · Issue 213355

Fixed flow line distortion in Process Modeler

Resolved in Pega Version 7.1.9

When clicking through to a subprocess from a parent flow (by clicking the + sign in the blue subprocess shape), flow lines in the subprocess were shown in a distorted fashion. When opening the same flow in a separate tab (by right clicking the blue subprocess shape and selecting Open Flow) the flow lines were correctly painted. This was an issue caused by the different renderings of the flow depending on whether there was a click through to it (with the + on the parent flow?s subprocess shape), or the subflow was opened in a separate tab (with open Flow). After the Process Modeler saved and checked-in the flow, the connector lines were re-drawn in ways that were non-intuitive and hard to interpret due to the edge routing in PM being calculated off incorrect input data that was taking into account shapes that were not represented on the screen. To fix this, the system now ensures the edges are routed without taking into account any shapes not represented on the canvas.

SR-A1479 · Issue 205900

UpgradeDataSchema target sets resume.action correctly

Resolved in Pega Version 7.1.9

Attempting to resume an upgrade after correcting a local error failed due to resume.properties having the default resume.action=install instead of =upgrade, causing the system to attempt to create tables in the data schema which already existed. The default of "install" that is set for resume mode has been removed, and the install process will now specifically set it when appropriate. A check has also been added to ensure the flag is set properly for the work being done.

SR-A1479 · Issue 205896

UpgradeDataSchema target sets resume.action correctly

Resolved in Pega Version 7.1.9

Attempting to resume an upgrade after correcting a local error failed due to resume.properties having the default resume.action=install instead of =upgrade, causing the system to attempt to create tables in the data schema which already existed. The default of "install" that is set for resume mode has been removed, and the install process will now specifically set it when appropriate. A check has also been added to ensure the flag is set properly for the work being done.

SR-A1479 · Issue 205895

UpgradeDataSchema target sets resume.action correctly

Resolved in Pega Version 7.1.9

Attempting to resume an upgrade after correcting a local error failed due to resume.properties having the default resume.action=install instead of =upgrade, causing the system to attempt to create tables in the data schema which already existed. The default of "install" that is set for resume mode has been removed, and the install process will now specifically set it when appropriate. A check has also been added to ensure the flag is set properly for the work being done.

SR-A3062 · Issue 209372

Added Unicode character error handling for JAR Import Wizard

Resolved in Pega Version 7.1.9

When there are files with Unicode characters in the import directory of a Unix system, the JAR import wizard would throw an exception and not display any files. This exception has been corrected by adding error handling in the selectfile control.

SR-A3697 · Issue 210718

Resolved Revalidate and Save freeze

Resolved in Pega Version 7.1.9

After upgrade, running revalidate and save on imported rules with the option "During Update Move To?" enabled, the first rule was processed but the process then stopped and generated the error "Uncaught TypeError: parentRow.all is not a function" if the Google Chrome or Mozilla browser is used. This problem was caused by old non-auto-generated controls, and has been resolved by modifying the ShowBulkUpdateList html section.

SR-A438 · Issue 210728

Global Resource Settings syntax examples documentation updated

Resolved in Pega Version 7.1.9

An error was found in the documentation examples for using the Global Resource Settings; this has been updated to remove the dot in the syntax examples.

SR-A789 · Issue 205761

Enhancement added for handling DB2 BLOB sizes

Resolved in Pega Version 7.1.9

BLOB schema changes were not being picked up during import due to the schema import/export process being limited in its ability to preserve the BLOB size changes being dynamically set in the db. An enhancement has been added to make meaningful use of reported blob sizes (DB2 LUW and DB2 z/OS).

SR-A1350 · Issue 205576

Added support for adding custom GuardrailWarning

Resolved in Pega Version 7.1.9

A customer-created custom activity "addGuardrailWarning" with incoming parameter (WarningMessage) of type Rule-Message with the intent that whenever the new activity was called from another activity, the SmartPrompt-enabled parameter would provide a list of Rule-Message instances starting with any defined on the class of the Step Page (or the class of the calling Activity when the Step Page is blank), and then working up the inheritance hierarchy, much like the behavior provided on other activity methods such as the Data Transform parameter of the Page-New method. However, the SmartPrompt for this custom function only showed rule-messages of pyCategory "Error", or "blank" due to lack of support for this custom Guardrail Warning. In order to support this customization, the function alias pxAddGuardrailMessage has been created and this FA can be accessed by a call-function method in activity as 'Add a message to a page using [Name of the Message Rule]'.

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