INC-210855 · Issue 715821
BigDecimal handling updated for @ sum function
Resolved in Pega Version 8.8
The @ sum function was not behaving correctly. This was traced to the java code in the 'sum--(ClipboardPropertyCollection)' function which was not properly converting the double to Bigdecimal for some of the inputs like 500, 500, 600.11. This has been resolved by modifying the function to convert input properties to BigDecimal, add BigDecimal values, and return the result.
INC-216381 · Issue 716614
BigDecimal handling updated for @ sum function
Resolved in Pega Version 8.8
The @ sum function was not behaving correctly. This was traced to the java code in the 'sum--(ClipboardPropertyCollection)' function which was not properly converting the double to Bigdecimal for some of the inputs like 500, 500, 600.11. This has been resolved by modifying the function to convert input properties to BigDecimal, add BigDecimal values, and return the result.
INC-139611 · Issue 587600
Timezone.getDefault function replaced for performance improvement
Resolved in Pega Version 8.6
Blocking threads were seen around the GregorianCalendarFactory.clearObject(Object) function, leading to an adverse impact on the performance.TimeZone.getDefault() is a synchronized method call, and under high load this method caused contention when more date-related APIs were invoked. To resolve this, Timezone.getDefault() has been removed and the function has been assigned to a static variable used in the clearObject() API.
INC-139810 · Issue 592835
New Rule-Utility-Function added to allow customizing filename formatting in repository
Resolved in Pega Version 8.6
When using S3 as file storage, uploading a file with a name such as "sample.tar.gz" resulted in the file name in the repository being formatted as "sample.tar_.gz" instead of the expected "sample_.tar.gz". This was caused by the handling in pzSaveToRepository, which was meant to include the CaseID for the customer use case of same-name attachments on every instance of a case. In order to handle attachments with multiple file extensions such as "<FILE_NAME>.tar.gz", the logic for the fileName formatting has been moved from pzSaveToRepository to the new Rule-Utility-Function pyFormatAttachmentName so that is is possible to override and customize the behavior.
INC-225687 · Issue 739708
Handling added to avoid incorrect true value for DateTimeisPastOrFuture
Resolved in Pega Version 8.8
When the Function pxDateTimeisPastOrFuture() was called with the arguments "" (the empty String) and "false", it sometimes returned "true" instead of "false". This function internally calls the Function CompareDates() which takes two Strings as arguments. In this case, one is provided by the caller of pxDateTimeisPastOrFuture, the other one is generated at runtime, as the current date/time. As the second argument of pxDateTimeisPastOrFuture, the generated date/time will be the first parameter, while the second one is the date/time argument for pxDateTimeisPastOrFuture. If that argument is the empty String, is will be replaced by the current date/time. This means that the value for the second parameter is determined after the first parameter and that can result in a gap in time by a few milliseconds. This in turn results in "true" as the return value for pxDateTimeisPastOrFuture. This has been resolved by adding handling for a blank string so "false" is returned correctly.
INC-138649 · Issue 585357
Timezone retrieval performance enhancement
Resolved in Pega Version 8.6
In order to improve performance and reduce a potential bottleneck for concurrent threads, PRDateTimeUtilsImpl has been updated to use a common GMT time zone object rather than getting the time zone for each operation for each function call.
INC-169518 · Issue 649156
Email address parsing logic updated
Resolved in Pega Version 8.5.4
Email listener functionality for case creation and email notifications was not working as expected after update due to a difference in the the service email rule request header properties (pyInboundEmail.pyFrom & .pyInboundEmail.pyFromDisplayName) clipboard values. This has been resolved by updating the parsing logic for the email addresses to look for an InternetAddress object and then fallback to a regex match.
INC-143376 · Issue 604530
Adding handling for property without parent page
Resolved in Pega Version 8.6
Filtering was not working for a DateTime control in an optimized grid with embedded property which was a function alias defined in a report definition referenced by a Data Page. This was traced to the system assuming that every property has a parent page, which this use case did not. To resolve this, an update has been made that will return null for the parentGroupOrListProp if one does not exist.
INC-220137 · Issue 715266
UpdateDateTime casing corrected in filters
Resolved in Pega Version 8.7.2
When using Job Scheduler with MS/SQL, the error "Cannot find either column 'mktdata' or the user-defined function or aggregate 'mktdata.pr_read_from_stream', or the name is ambiguous." This was traced to a casing issue and has been resolved by updating the pxupdatedatetime property to pxUpdateDateTime in Filters F1 and F2.
INC-220137 · Issue 721896
UpdateDateTime casing corrected in filters
Resolved in Pega Version 8.8
When using Job Scheduler with MS/SQL, the error "Cannot find either column 'mktdata' or the user-defined function or aggregate 'mktdata.pr_read_from_stream', or the name is ambiguous." This was traced to a casing issue and has been resolved by updating the pxupdatedatetime property to pxUpdateDateTime in Filters F1 and F2.