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-124054 · Issue 189568

Simulation delete timing issue resolved

Resolved in Pega Version 7.1.8

When attempting to delete a simulation, if the deletion process exceeded the system time-out or the space on the database required for undo was too small (as can occur when many simulations have been run and the simulation output table contains many millions of records), the mass deletion failed and the system became hung or returned a time-out screen which required logging out and in again. At that point it was seen that the simulation results had been removed from the list but the actual results deletion did not complete. This was caused by the simulation work item being closed first, followed by the delete of the table. In the case of a failed deletion because of any DB issue, manual intervention was required to delete the records from the table as the simulation object was no longer available. To resolve this, the sequence of steps while deleting the Batch WO from LPhas been updated to show the relevant error message in case of failures for any reason, and the work object is closed after the output table is deleted.

SR-125937 · Issue 190307

Aligned Connector lines in Process Modeler

Resolved in Pega Version 7.1.8

Upon opening a flow rule, the Connector lines in Process Modeler were rerouted inconsistently with what was the saved state of the rule. The root cause was traced to code defects that resulted in the incorrect display of an error message and the incorrect drawing of the connector lines when the process modeler is loaded. These have been corrected.

SR-131162 · Issue 201045

Corrected inheritance for Data classes

Resolved in Pega Version 7.1.8

After migration, an API used to pull the list of concrete classes from RootClass Work- was pulling an additional class (Data-Portal-Padportal) when work- was supplied as an argument for rootclass. This additional class caused issues with reports due to it pointing to pr_history_data table and looking for non-existent columns. These inheritance issues have now been corrected.

SR-131162 · Issue 201046

Corrected inheritance for Data classes

Resolved in Pega Version 7.1.8

After migration, an API used to pull the list of concrete classes from RootClass Work- was pulling an additional class (Data-Portal-Padportal) when work- was supplied as an argument for rootclass. This additional class caused issues with reports due to it pointing to pr_history_data table and looking for non-existent columns. These inheritance issues have now been corrected.

SR-127035 · Issue 193206

Improved opening custom flow rules with Microsoft Internet Explorer 9

Resolved in Pega Version 7.1.8

Opening up a flow rule with many sub-process references was taking an excessive amount of time when using Microsoft Internet Explorer 9 due to general browser slowness and the system loading all referenced flow rules at that time. This has been resolved by tuning the JavaScript code to improve the performance of the viewer and to disable drilldown functionality from the server.

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-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-D37421 · Issue 514593

Cross-site scripting security added to Marketing Offers

Resolved in Pega Version 8.1.8

Cross-site scripting protections have been added to Marketing Offers, which had a potential vulnerability when using Firefox.

SR-D45608 · Issue 519902

Correct service instance name passed for data flow in DSMStatus

Resolved in Pega Version 8.1.8

When using the Connect-HTTP service "DSMStatus" to provide the node and status information as seen on the various tabs of the Designer Studio > Decisioning > Infrastructure > Services landing page, using DataFlow as the service parameter for the HTTP service method resulted in an empty response when the expectation was to get the information regarding the cluster details of Dataflow node type. This was traced to the service instance name not being parsed correctly when used for Data Flow services, and has been resolved by ensuring the correct service instance name is passed for this use.

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