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-225696 · Issue 736797
Explicit expiration added to avoid searching for expired requestor
Resolved in Pega Version 8.8
A login page was taking long time to display. This was traced to pre-authentication cookie in the browser pointing to the requestor object on the server which triggered a lookup across the entire cluster of servers to find the requestor. This was not only taking time, but the attempt to find the requestor in the cluster would always fail to return results as the requestor was not passivated but instead removed after two minutes. To resolve this, an expiration has been added to the Pega-RULES cookie when the value is pre-authenticated. The time to expire is derived based on the short-lived requestor time for unauthenticated requestors + 1 minute, and will be 2 minutes by default. This will avoid searching for a requestor across all nodes in cluster when the requestor has already timed out and been destroyed by server.
INC-225788 · Issue 728057
Performance improvements for save-as
Resolved in Pega Version 8.8
Performance issues were seen when using save-as for rules such as Declare expression, When rules, activity, etc. This was traced to a very large number of extra database queries that were being executed while building the Declarative Cache. To resolve this, an update has been made so the queries used for the Declarative Cache will only be executed when required.
INC-226762 · Issue 727390
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-226764 · Issue 745051
Performance improvements for save-as
Resolved in Pega Version 8.8
Performance issues were seen when using save-as for rules such as Declare expression, When rules, activity, etc. This was traced to a very large number of extra database queries that were being executed while building the Declarative Cache. To resolve this, an update has been made so the queries used for the Declarative Cache will only be executed when required.
INC-226830 · Issue 727154
Case Archival hierarchy updated for multiple occurrences of a child case
Resolved in Pega Version 8.8
Case Archival did not correctly discover hierarchy when child case appeared multiple times in the hierarchy. This was due to the CaseAssociationsProvider class having a check to skip performing the discovery when the case type had already been processed, and has been resolved by updating the handling for this scenario.
INC-227988 · Issue 736463
Corrected unnecessary declare trigger firing
Resolved in Pega Version 8.8
The crmAuditStage declare trigger was activated whenever the views mentioning the properties were accessed even though the values for the mentioned properties were not changed or updated. This resulted in a row inserted in the audit table. The audit data was in turn read by other processes to determine the age, health status of opportunity, etc, causing several reporting issues. To resolve this, if the target and source pages have the same property(same value), while invoking the Page-Merge-Into with Keep value 3(PUTALL_MERGE), then it will not create changeElements and the Declare Trigger and Declare On Change Rules should not fire unnecessarily.
INC-228622 · Issue 739122
Month names localized correctly for "CZECH"
Resolved in Pega Version 8.8
Localization for the country "CZECH" has been updated to correct the month names displayed in calendar control.
INC-229608 · Issue 732636
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.
INC-229907 · Issue 734305
SOAPAppenderPega includes namespace in ClusterName and Signature fields
Resolved in Pega Version 8.8
After update, the Predictive Diagnostic Cloud (PDC) was not not logging the events, servers status, etc, and was indicating it was blocked by the IBM DataPower Gateway due to the SOAP message format. This was traced to the namespace not being included in the ClusterName field, and has been resolved by updating the sendEvent method in SOAPAppenderPega.java to add the namespace to the ClusterName and Signature fields in the header.