INC-211178 · Issue 704591
Decimal parameters retain null value instead of being set to 0
Resolved in Pega Version 8.8
When mapping any data in 8.6+, if the source is a decimal property rule and the target is a parameter defined as decimal, the decimal parameter's value will be 0 if the source property is null. This was a behavior change from previous versions of Pega where the target parameter would be null. This has been resolved by changing the code generation for the read operation on the parameter decimal type assignment to use resolveToString() instead of calling resolveToBigDecimal() so a null value is retained.
INC-211292 · Issue 705884
Updated handling for last_access to improve backwards compatibility
Resolved in Pega Version 8.8
After update from Pega 8.3 to Pega 8.6, many errors were seen in the logs regarding the call of the Pega API /api/v1/nodes/all/requestors. In 8.3, the API was responding with the field last_access populated properly, but this field was blank in the new version. This was an unintended consequence of work done to resolve inconsistencies with the date format in Admin Studio, and has been resolved.
INC-211480 · Issue 712420
Handling added updates involving Oracle descending column
Resolved in Pega Version 8.8
The build was failing when attempting to update to Pega 8.6, and an error indicating an issue with Oracle columns was generated. Investigation showed that when a column changed that belonged to an index which had a 'desc' column (even if the changed column was not specified as desc), an Oracle restriction was triggered. This occurred with any column size increase if the column participated in an index containing a descending column or a function index. This has been resolved by adding a step to drop the index before altering the column if a Descending index is involved, and to catch the case where the resized index is part of an index that has a descending column but is not necessarily a descending column itself.
INC-211599 · Issue 708544
Data page definition reload made more robust
Resolved in Pega Version 8.8
The data page was intermittently being removed from the cache. This was traced to the use of a thread from ThreadContainer to reload the data page definition: a null thread could be returned if the request came from a master agent, which would then cause the definition reload to fail. This has been resolved by updating the system to use the current thread in context to reload the data page definition.
INC-211655 · Issue 714060
Removed extra space in Malaysian locale
Resolved in Pega Version 8.8
For the ms_MY locale, an extra space was being appended to Number formats, such as " 0", " 1". This has been corrected.
INC-211977 · Issue 713460
Handling added for large BIX Postgres data sets
Resolved in Pega Version 8.8
BIX extracts were causing timeouts or JVM out of memory errors. This was traced to the Postgres JDBC driver ignoring fetch size in auto-commit transaction mode, which led to everything being loaded into memory at once. To resolve this, changes have been added to support fetch size for large results when using PostgreSQL database for BIX Extraction.
INC-212251 · Issue 720198
Editable data page properly refreshes after interaction
Resolved in Pega Version 8.8
A data page using editable mode was adhering to the "Reload once per interaction" option used for readonly mode. This led to issues such as tables not refreshing after sorting or applying filters. To resolve this, refreshReloadInteraction has been updated to false when mode is not readonly.
INC-212433 · Issue 724512
Clarified SLA calendar error message
Resolved in Pega Version 8.8
If a calculated SLA date is out of calendar end date range, the error "Perhaps the business calendar of year XXXX is missing" is generated. When the provided start date is not the business day and the SLA was calculated by using a custom activity using addTime, isBusinessDay and pxGetSpecifiedTimeOnDate function, this message showed the current year calendar. When checked in the tracer the exception was thrown with the correct year calendar, but when the exception was written as an alert the message was changed and provided the misleading error on the screen. This has been resolved by addressing the misleading error message.
INC-212729 · Issue 699682
ClusterAndDBCleaner updated to with with Oracle query limits
Resolved in Pega Version 8.8
The pzClusterAndDBCleaner job scheduler was not able to cleanup data in pr_op_data session table due to the delete query formed to clean up this table throwing "ora-01795 maximum number of expressions in a list is 1000 oracle 19c" exception. This has been resolved by splitting requestor IDs into batches of 1000.
INC-212900 · Issue 711003
ADLS/File listener support added
Resolved in Pega Version 8.8
Azure Data Lake Storage type support has been added for file listener usecases.