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-A87989 · Issue 255978

DSM Operations Guide updated for Interaction History Database Tables setup

Resolved in Pega Version 7.2.2

The DSM Operations Guide has been updated to clarify that when setting up Interaction History Database Tables in a Dedicated SchemasetupDatabase.properties file, the argument should be dbDataSchema and not dbSchema as was given previously. Also, data.schema.name=PEGADATA entries will take precedence if already entered.

SR-A96425 · Issue 262660

Cassandra enhancements

Resolved in Pega Version 7.2.2

The following enhancements and updates have been made to Cassandra usage: all independent services initialize in parallel, nodes will not start (Add node) while there is another node leaving, auto_snapshot is disabled on truncate, nodes will join the DDS cluster properly when booted together, and a check has been added to ensure Cassandra is up before adding the node in DDS.

SR-A90314 · Issue 258672

DSM service will not start in non-web environment

Resolved in Pega Version 7.2.2

The import of NBAA using prpcUtils did not terminate due to the DSM services threads not being properly shut down during program termination. As DSM service is not needed in this circumstance, DSM service has been fixed to not start in non-web environments such as prpcUtils or prgit.

SR-A38580 · Issue 252790

Improved Extended Interaction History cache handling for column removal

Resolved in Pega Version 7.2.2

The Interaction History Component was generating an error when IH was extended with additional attributes in the transform rule:Data-Decision-IH-Configuration -pyInteractionHistoryConfiguration and then deleted at a later stage. Once the new property was mapped and the IHFact table was altered to add the new column, the Interaction History component in the strategy which retrieves the IH data was not able to handle the removal of that column from the IHFact table or from the data transform due to a static marker in the rule not being updated with the deletion. The cache function has been modified to correctly reflect the deletion of the column.

SR-B2803 · Issue 272409

Proposition Filter performance improvement

Resolved in Pega Version 7.2.2

The logic for the Proposition Filter rule has been modified to not perform constant database lookups in order to get its requested information but rather to always pass the proposition data into strategy.

SR-A102123 · Issue 270203

EventStore compiler save error fixed

Resolved in Pega Version 7.2.2

The Save Operation for pxEventStore in Activity was giving a compile error. This was due to an incorrect class/method being generated, and the event-store code which controls the custom Dataset-Execute params has been updated to resolve this.

SR-A94062 · Issue 268346

Performance improvements for DSM SOAP decisioning

Resolved in Pega Version 7.2.2

The SOAP service providing decisioning functionality has been updated with memory allocation efficiencies in the DSM solution, specifically around DSM pages, to improve performance.

SR-A99633 · Issue 270062

ADM startup made more robust

Resolved in Pega Version 7.2.2

The Strategy execution was failing when the ADM server was unavailable. To support a more robust process, the server proxy will be wrapped with circuit breaker to prevent propagation of errors caused by ADM unavailability, and backup is no longer taken after reading event queue on ADM server startup (if failsafe on), but instead will just happen on next model update call (every 30 seconds). This is to reduce the window in which responses are lost when server is starting up.

SR-A92162 · Issue 260005

Proposition Filter Strategy logic more flexible for testing

Resolved in Pega Version 7.2.2

The Strategy test run was giving inconsistent results whenever the LOGIC STRING of the Proposition Filter used in that strategy was changed. This was traced to the order of sub-strategy execution, and has been fixed by modifying the component referencing to be execution-order independent and cache the component results regardless of whether the component has been executed or not.

SR-A97134 · Issue 263264

TW connectors made more robust

Resolved in Pega Version 7.2.2

The Twitter data flow extraction has been made more robust with better error handling for any failures the the TW connectors might encounter.

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