SR-B49357 · Issue 306843
Enhancement to configure multiple Cassandra instances in single rule
Resolved in Pega Version 7.3.1
To facilitate connecting multiple external Cassandra instance hosts in a connect-Cassandra rule, it is now possible to establish connection to Cassandra instances on Cassandra Connector rule form by defining multiple hosts in the field: 'eng-bigbang-perf06,eng-bigbang-perf05' using comma (,) as a separator.
SR-B49995 · Issue 308428
Proposition filter rule description updated to match decision data description changes
Resolved in Pega Version 7.3.1
Updating the description field of a proposition in the decision data did not update the description in the proposition filter rule involving that proposition as expected. This has been resolved by updating the rule which is refreshing proposition name changes to handle description change as well.
SR-B56530 · Issue 316311
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 in addition to an error obtaining the class. This has been fixed by properly setting the KVS type: the DataFlowRunConfig.getKeyValueStoreType() will not return NONE but default instead, and the pzDataFlowContainsEventStrategy now Iterates through all subflows and fixed secondary destination name.
SR-B69595 · Issue 317880
Fixed UnsupportedOperationException from decision table
Resolved in Pega Version 7.3.1
When using embedded properties (e.g. .OfferData.Action) within a decision table, an UnsupportedOperationException appeared on the DSMClipboardProperty if it was executed via a Strategy rule. The issue was with a function being not implemented within DSMClipboardPage, and has been fixed.
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.
SR-B52773 · Issue 312968
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.