SR-B70652 · Issue 325760
Read operations updated for Datastax 3.1.x use
Resolved in Pega Version 7.3.1
In the 3.1.x Datastax driver reads are no longer retried by default. Therefore, the read operations have now been explicitly marked as idempotent to force the Datastax driver to retry timed out reads.
SR-B70652 · Issue 325924
Timeout error resolved for write future
Resolved in Pega Version 7.3.1
With retries enabled, the write future was timing out before retries could be completed. This has been fixed by removing the timeout on the write future since timeouts will be caught using Datastax driver exceptions.
SR-B74934 · Issue 327017
Facebook connector refined to handle page deletion while the AADrivetech is active
Resolved in Pega Version 7.3.1
A Facebook connector trying to connect to a invalid page was causing out of memory errors. In this scenario, a Facebook Page that was no longer required was deleted but the AADrivetech Facebook connector was left running. This connector, in its attempts to contact the Facebook page and retrieve the getFrom parameter which was now null, started to consume resources on the node leading to the outage. To solve this, the code has been modified to not expect the user name to always come from Facebook but instead put in an anonymous name if the page disappears.
SR-B76526 · Issue 326533
Backwards compatibility enhancement for @when() validation
Resolved in Pega Version 7.3.1
After upgrade, a Strategy rule which referred a 'when' with the syntax @when(isOnlineApplication) was failing with design time validation saying that when rule was not found in the SR and instead it had to find it in the Customer/Applies to class. For the @when() issue, the root cause was that the validation context of @when() was switched from Applies-To class to the Step Page class due to a change in the core engine. The behavior of expression parsing for when rule calls was changed in release 7.2. It used to take the Apply-to class to validate the existence of the rule, but not it is taking the Step Page class. And Strategy rule doesn't push/pop stackframe due to performance reasons, thus StepPage on stack for Strategy is always the same as Primary page. For greater compatibility, the system will set the PageContextClass to the Apply To class so the expression parser can validate the setup which is expected at run-time.
SR-B69409 · Issue 317548
CLOB type handling enhanced in Marketing
Resolved in Pega Version 7.3.1
Pega Marketing uses the out-of-the-box DSM activity pxRunDDFWithProgressPage for triggering Data flow runtime. After upgrade in DB2 environments, the DF execution completed but the activity returned a failure. It was found that if a CLOB column is present in the filter of a NativeSQL object invoked from an activity, the status had an error message even though functionality was fine. To ensure consistent behavior, CLOB has been added to supported data types so the severity of the exception can be changed so as to not show error message in activity's status.
INC-174785 · Issue 651461
Flow connector attachment point control updated
Resolved in Pega Version 8.8
Previously, attempting to change the target point for a connector in the flow modeler to a different point on the same shape did not work without placing the point on an intermediate connector first. An enhancement has now been added to support moving the connector directly to a different constraint point on the same shape.
INC-179727 · Issue 704543
Modified batch requestor handling to ensure cleanup
Resolved in Pega Version 8.8
A large buildup of batch requestors was seen, and restarting the node did not clear it. Investigation showed that in the case of one class reading a DSS value, a Pega requestor was being created when it was unable to retrieve any Pega context, and this requestor was not cleaned up afterwards. To resolve this, an update has been made to the way the requestor and Pega context is being created along with ensuring it will be cleaned up properly after use.
INC-180246 · Issue 664948
Support for apostrophe added to keyword tokenization
Resolved in Pega Version 8.8
A keyword containing an apostrophe was not detected properly in Text extraction model. This has been resolved by updating the annotator used in the tokenization.
INC-180762 · Issue 666291
Calendar gadget correctly displays event of >31 days
Resolved in Pega Version 8.8
When using the pxCalendar gadget to display a hotel reservation of duration > 31 days, the entire bar was not displayed on the PEGA calendar. Investigation showed that eventslist was not considering the month value, and this has been resolved by updating the pzEventPreProcessing activity to check for month.
INC-194348 · Issue 682339
Resolved multiple copies of Pega0050 alerts
Resolved in Pega Version 8.8
The PDC alert Pega0050 was seen multiple times for the standard pxgetoperatordetails activity, step 6.This has been fixed by removing the pagecopy and updating the data page properties.