SR-B5911 · Issue 275066
Data flow ramp up queuing improved
Resolved in Pega Version 7.2.2
Running a very large data flow was generating the error "Unable to queue record for 5 minutes for processing in data flow. Retrying." This issue was caused by the data flow run ramp up procedure, which was creating multiple assignments (1000+in some cases) and acquiring a lock for each of them. With very large flows, this procedure would take a long time and cause the "Unable to queue record for 5 minutes ..." error. To resolve this, the system has been modified to reduce the number of simultaneous database locks so the ramp up procedure will take much less time and the flow will run smoothly.
SR-B5634 · Issue 274799
Stack frame handling made more robust
Resolved in Pega Version 7.2.2
Stack frame handling has been made more robust to prevent the stack trace from getting out of sync in cases where the strategy execution throws an exception.
SR-A98315 · Issue 268392
Proposition landing page date/times localized
Resolved in Pega Version 7.2.2
The Date values entered in the Proposition landing page (unversioned propositions) were always rendered in GMT time zone and not the user's time zone. This has been fixed.
SR-A98315 · Issue 270099
Proposition landing page date/times localized
Resolved in Pega Version 7.2.2
The Date values entered in the Proposition landing page (unversioned propositions) were always rendered in GMT time zone and not the user's time zone. This has been fixed.
SR-A89001 · Issue 257712
Cassandra made more robust and dx logging enhanced
Resolved in Pega Version 7.2.2
The Dnode/adaptive logic worked as expected on an environment with a single node, but was working sporadically on a eight node setup and generated the "DNodeException: Cannot execute modification statement". After analysis it was determined that Cassandra was intermittently seeing the other nodes due to several issues: - Server is overloaded and cannot receive ping from other nodes - Network difficulties - Topology issues due to series of sporadic server restarts To resolve this, the system has been updated to retry Cassandra requests several times to account for temporary network issues and will provide more robust and detailed diagnostics information to help in problem solving.
SR-A87989 · Issue 255973
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-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.