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-116508 · Issue 170253

Large flow handling improved for IE8

Resolved in Pega Version 7.1.7

When opening a large flow in IE8 which includes multiple sub flows, a long-running script warning is displayed. This is caused by too many calls being executed at once on IE8, and has been remedied by turning on the asyncProcessing parameter for IE8.

SR-116818 · Issue 167121

Corrected swim lane routing with shapes

Resolved in Pega Version 7.1.7

While using swim lanes, adding shapes into the flow caused unexpected and random behavior of the process modeler including failure to return control to the user after saving. This error was related to routing handling when swim lanes are present, and has been corrected.

SR-117228 · Issue 168249

Resolved issues with Flow shapes distributed across Swim Lanes

Resolved in Pega Version 7.1.7

Pool size is maintained as both pixels and inches, but auto conversion was failing if the pool dimension was very large. This created an error where saving a flow rule could cause the pool to drastically shrink (for example, 20 inches becoming 20 pixels). In order to maintain the proper dimensions, a check has been added for pool and swimlane to ensure the proper inch/pixel conversions.

SR-B52067 · Issue 311178

Handling improved for extremely large data flow run statistics page

Resolved in Pega Version 7.3.1

A data flow monitoring page with 1000+ data flow shapes in total was hanging while loading the statistics. This happened because the component statistics table had no pagination enabled, and displaying all 1000+ shapes in one screen caused the browser to hang. This has been remedied with: - Pagination on the component statistics table in the data flow monitoring screen - Filtering on the component statics table, allowing monitoring of only relevant data flow components

SR-B69080 · Issue 318226

Local PegaAPI instance added for Monte-Carlo dataset

Resolved in Pega Version 7.3.1

A dataflow running from a Monte-Carlo data set was failing due to stale thread exception. This was due to the PegaAPI variable 'pega' not being defined as local variable in the Montecarlo dataset generator, and has been resolved by creating a local variable PegaAPI instance.

SR-B53147 · Issue 310299

HDFS configuration updated to support KMS server

Resolved in Pega Version 7.3.1

A field has been added in HDFS configuration to allow configuration of a KMS server. This setting will be propagated to all places where Hadoop configuration is used - hdfs & parquet data sets.

SR-B74689 · Issue 324632

Marketing data flow run made more robust

Resolved in Pega Version 7.3.1

After upgrade, it was observed that Pega Marketing Campaigns were failing if there were no customers in the Audience configured on the Campaign, generating the error message "The run failed, because it exceeds the maximum number of failed records, which is currently set to 0". The cause of this was executing a distributed data flow with a database as primary source on an empty table, leading the run to fail as a table without any partition was considered in the handling. The database dataset has now been updated to differentiate the case when there's no partition available from the case when there's a single partition for every record, ensuring the DB data set now returns 'all' records when there is no partition key defined, and the data flow handles the no values for partitions in a more robust way.

SR-B51204 · Issue 309685

Cassandra enhancement to retrieve multiple records and use runinparallel

Resolved in Pega Version 7.3.1

An enhancement has been added to allow the Cassandra Connector GET operation to return multiple rows by querying on clustering keys and/or secondary index. In addition, an issue with Connect-Cassandra not supporting run-in-parallel execution mode has been resolved to allow a result list from list operation to be called from pyoutputpage or primary page.

SR-B64066 · Issue 313310

Cassandra enhancement to retrieve multiple records and use runinparallel

Resolved in Pega Version 7.3.1

An enhancement has been added to allow the Cassandra Connector GET operation to return multiple rows by querying on clustering keys and/or secondary index. In addition, an issue with Connect-Cassandra not supporting run-in-parallel execution mode has been resolved to allow a result list from list operation to be called from pyoutputpage or primary page.

SR-B56597 · Issue 311992

IBM AIX CRC32 result forced positive for stream data generation

Resolved in Pega Version 7.3.1

An issue with IBM AIX intermittently returning a negative CRC32 result caused files generated by a Stream data set to be corrupted. A check has been added that will force the CRC32 result to always be positive.

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