INC-199320 · Issue 696941
Corrected duplicate record error message
Resolved in Pega Version 8.7.1
When inserting a duplicate record in a grid, the error was shown at the harness level instead of the record level. This was traced to the error messages being removed from the step page, and has been resolved by updating the system so messages will not be cleared if the same value is being set.
INC-189136 · Issue 679516
Dataflow with report definition source repaired
Resolved in Pega Version 8.7
After update, data flows using a report definition dataset as source were throwing a null pointer exception. This was traced to previous work done around retry handling for Oracle queries where there were issues identifying the correct column types; that previous work has been reverted to resolve this null pointer exception, and further work will be done to refine the solution to the Oracle CLOB DatabaseException.
INC-197610 · Issue 688003
Dataflow with report definition source repaired
Resolved in Pega Version 8.7
After update, data flows using a report definition dataset as source were throwing a null pointer exception. This was traced to previous work done around retry handling for Oracle queries where there were issues identifying the correct column types; that previous work has been reverted to resolve this null pointer exception, and further work will be done to refine the solution to the Oracle CLOB DatabaseException.
INC-176785 · Issue 656077
Validation on DateTime property working for mobile
Resolved in Pega Version 8.7
A mandatory DateTime field with "Allow text entry" set to 'No' was not restricting validation when no value was provided. This was an unintended consequence of recent work done to validate input type date along with input type hidden, and has been reverted.
INC-193507 · Issue 681748
DSS added to control DADT purge
Resolved in Pega Version 8.7
Thread dumps and service restarts were seen when Decision Engine data nodes were working with a very large number of tables. This has been resolved by adding a DSS as part of the CDH layer which will skip CDH DADT that contains pattern DATA_BATCHOUT, for instance "DATA-ADMIN-DB-TABLE DATA-BATCHOUTPR469001" to prevent the deletion causing full cache invalidation of the table information map. With this DSS set to true, when the purge agent runs and deletes the DADT, class cache should no longer be invalidated. With the DSS missing or set to a value other than true, the class cache invalidation will still occur.
INC-204672 · Issue 699355
Handling updated for database function GREATEST
Resolved in Pega Version 8.7.1
When deploying Pega on Red Hat OpenShift, attempting to index data via the SRS resulted in the landing page loading and RULES indexing appears to start, but when it finally completed it showed no records. While the index operation was running log entries showed the SRS service was unavailable and that the isolation context did not exist. Investigation showed there was an exception being generated indicating "com.microsoft.sqlserver.jdbc.SQLServerException: 'greatest' is not a recognized built-in function name". Because the function GREATEST is not supported in Microsoft SQL Server 2019, an update has been made to change GREATEST into an expression like "IIF(COALESCE(column_name, 0)>value, COALESCE(column_name, 0), value)" for compatibility.
INC-209688 · Issue 702729
Handling updated for database function GREATEST
Resolved in Pega Version 8.7.1
When deploying Pega on Red Hat OpenShift, attempting to index data via the SRS resulted in the landing page loading and RULES indexing appears to start, but when it finally completed it showed no records. While the index operation was running log entries showed the SRS service was unavailable and that the isolation context did not exist. Investigation showed there was an exception being generated indicating "com.microsoft.sqlserver.jdbc.SQLServerException: 'greatest' is not a recognized built-in function name". Because the function GREATEST is not supported in Microsoft SQL Server 2019, an update has been made to change GREATEST into an expression like "IIF(COALESCE(column_name, 0)>value, COALESCE(column_name, 0), value)" for compatibility.
INC-170130 · Issue 643776
Null check added for debug logging pointer error
Resolved in Pega Version 8.7
When DEBUG logging was enabled on the class 'com.pega.pegarules.session.internal.mgmt.base.AbstractPageDirectory', system restart resulted in the node failing to startup with a null pointer error in a debug block of this class. A null check has been added to resolve this.
INC-183960 · Issue 674381
Cases Created through email bots remains searchable
Resolved in Pega Version 8.7
When a case was created through Email Bot, the delete attachment link in pzCreateTriageWork activity was triggering a delete event in incremental indexing that removed the main work object. This has been resolved by adding a condition check in the SearchIncrementalIndexNotifier class for the link page, and the work object will be updated instead of deleted.
INC-175797 · Issue 662048
Date/time filter works in source column
Resolved in Pega Version 8.7
The date/time filter was not working in the Source column for a report definition. This was traced to "pxCreateDateTime" resolving and storing the pyDataType in the report as "DATE TIME". While "DATE TIME" is an acceptable data type it was not supported by pzGridSortPaginate and thus the filter did not work. This was a missed use case, and has been resolved by updating pzGridSortPaginate to check the dataType as both "datetime" and "date time".