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-B50458 · Issue 306818

Bulk Action select fixed for Microsoft Internet Explorer 11

Resolved in Pega Version 7.3.1

When using the Microsoft Internet Explorer 11 browser, clicking on the 'Select All' check box of the bulk action screen would select all of the assignments and then reset the flags to blank. This was an issue with select All property value being lost on refresh in Microsoft Internet Explorer 11, and has been resolved with an added Post value for the select All property in the pyBulkProcessingAssignDisplay section.

SR-B65922 · Issue 314665

Corrected Property type validation in Complex Question

Resolved in Pega Version 7.3.1

While creating a Complex Question with Property type Value list and referring an embedded property of type text in the Value list field, the validation message was not shown and system allowed the Complex Question to be saved successfully. Referring a top level property of type text (.ResponseText) showed the validation message (.ResponseText is not a valid Value List), but referring an embedded property type of text (.SurveyResponses(CEP).ResponseText) did not show the validation message. This was caused by missing handling, and has been corrected by modifying the ValidateSurveyEmbedPropertyMapping activity to check the last property mode for valuelist type.

SR-B74689 · Issue 323378

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-B65908 · Issue 314482

Serialization fixed for multi-node pre-activity dataflow

Resolved in Pega Version 7.3.1

Attempting to trigger a dataflow run with pre-activity configured to run on every node was failing with a serialization exception. This was caused by the task being distributed across the cluster having a member variable that was not serializable; this has been fixed.

SR-B56530 · Issue 312902

Reworked destination assumptions for child dataflows

Resolved in Pega Version 7.3.1

When activating a Real time data flow run containing a Stream dataset as input which was then output to two child dataflows containing different event strategies, an IllegalArgumentException error appeared. This was traced to the pzDataFlowContainsEventStrategy activity assuming that the last shape had "Destination" in the ID. This has been fixed by properly setting the KVS type: the DataFlowRunConfig.getKeyValueStoreType() will not return NONE but will default instead, and the pzDataFlowContainsEventStrategy now Iterates through all subflows and fixed secondary destination name.

SR-A101514 · Issue 316396

Busy indicator memory leak fixed for multiple iframes

Resolved in Pega Version 7.3.1

A memory leak was found with the client side script busy indicator when multiple iframes were involved. As part of this change, a part of the code in pega_ui_busyindicator.js which removes the status div within hidden iframes has been reworked to avoid memory leakage.

SR-A101514 · Issue 317772

Busy indicator memory leak fixed for multiple iframes

Resolved in Pega Version 7.3.1

A memory leak was found with the client side script busy indicator when multiple iframes were involved. As part of this change, a part of the code in pega_ui_busyindicator.js which removes the status div within hidden iframes has been reworked to avoid memory leakage.

SR-B64971 · Issue 316298

Added alt text attribute to paperclip icon for accessibility

Resolved in Pega Version 7.3.1

A paperclip icon in the pzMultiDragDropControlStandard rule did not have alternative text, impacting its accessibility. An alt="" attribute has been added to the image tag to correct this.

SR-B14710 · Issue 288487

Accessibility added for down arrow button access

Resolved in Pega Version 7.3.1

Accessibility has been added to the tooltip on a button when it is accessed via Down Arrow key so it will be read by JAWS.

SR-B52773 · Issue 312408

Improved null/blank parameter handling when using Microsoft Internet Explorer.

Resolved in Pega Version 7.3.1

After upgrade, opening an assignment in Microsoft Internet Explorer, clicking the save button, and then hitting Function F5 (PF5) caused a null pointer exception on the screen. When OK was clicked in the exception popup it displayed a blank case content screen. This issue was caused by some null parameters on the stored parameter page, and has been resolved by updating the API to better handle null and undefined parameters.

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