INC-205378 · Issue 698513
Added handling for double quotes on Substrategy shapes
Resolved in Pega Version 8.7.1
After update, there were compilation issues on calling substrategies from strategies using datapage.pxResults as another page. This was traced to the handling for a parameterized data page with double quotes on Substrategy shapes, and has been resolved.
INC-206684 · Issue 699365
Empty string handling added to SSA CompareDates
Resolved in Pega Version 8.7.1
The CompareDates implementation in SSA has been updated to fallback to the current datetime/date if it encounters empty string arguments.
INC-208207 · Issue 702800
#resolvedissues note:
GET API will consider case locking mechanism
Resolved in Pega Version 8.7.1
After update, performing a GET call on an assignment was unexpectedly locking the case. This was traced to a difference in handling: Pega 8.3 performed an Obj-Open-By-Handle of the workobject without acquiring a lock, while Pega 8.6 calls Assign-.acquireWorkObject which acquires a lock on the work object thereby affecting the other requestors from accessing the case. This has been resolved by enabling ConsiderLockingMode to independently determine the locking mechanism set for the case type.
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.
INC-198914 · Issue 686938
PMML updated for nested 'if'
Resolved in Pega Version 8.8
Running a model on the openscoring API and the Pega PMML model gave different results. This has been resolved by updating the handling for nested 'if' in PMML.
INC-200802 · Issue 699966
Line break handling added for setting required question asterisk
Resolved in Pega Version 8.8
If a survey question was formed in multiple sentences, the asterisk marking it as required was not displayed in screen. The asterisk displayed as expected if the question was one sentence. This has been resolved by updating the setMandatoryIconforQP script handle linebreaks and set the required symbol as expected.