INC-160825 · Issue 629370
Search landing page performance improved
Resolved in Pega Version 8.5.3
Performance improvements have been made for the Pega Platform search landing page by implementing timeouts for all requests to ElasticSearch when executing PegaIndexAdminImpl.getIndicesInfo() and changing all requests for single index to requests for all indexes. In addition, SearchUtils.areDummyDocumentsPresent() has been modified to get all 'dummy documents' in case there are duplicate dummy documents in the ElasticSearch indexes.
SR-115511 · Issue 168772
Application Express Wizard updated to correctly bind rulesets
Resolved in Pega Version 7.1.7
New Rule-Access-Role-Obj (RARO) rules created using Application Express wizard were being bound to specific ruleset versions vs. ruleset names. This caused failure to any modification to those RAROs, since modifying a RARO with a ruleset version would mean the save-as would fail if the validation found a RARO already present for that ruleset. In order to ensure proper binding and aid migration, a RARO with ties to a ruleset version will have that the version information removed automatically upon saving of the RARO.
SR-D92590 · Issue 553059
PostgreSQL information updated in Platform Support Guide
Resolved in Pega Version 8.5.2
The Platform Support Guide has been updated to reflect the following:Postgresql-42.2.14.jar supports PostgreSQL 8.2 or newer, and requires Java 6 or newer (Pega only supports Java 8 and 11); this driver also contains support for SSL and the javax.sql package. Prior versions of this .jar file have known problems. Do not use these versions: • 42.2.11 – creates an exception which stops Pega Platform startup • 42.2.12 and 42.2.13 – known vulnerability issues (CVEs) reported
INC-148414 · Issue 615595
Date field correctly extracted for IMAP inbound email
Resolved in Pega Version 8.5.3
After upgrade, email-sourced cases were not being created correctly. Tracer showed the date field was blank, causing an error which was traced to the getReceivedDate being returned as null for the JavaMail AP even though the IMAP protocol was being used. This was an unintended side effect of work done to handle a throttling exception in the IMAP inbound email flow, and has been resolved by updating the system so that if the getReceivedDate is null, the date will be extracted from the mail header while processing dates in EmailMessageInfo class.
INC-154605 · Issue 615662
Date field correctly extracted for IMAP inbound email
Resolved in Pega Version 8.5.3
fter upgrade, email-sourced cases were not being created correctly. Tracer showed the date field was blank, causing an error which was traced to the getReceivedDate being returned as null for the JavaMail AP even though the IMAP protocol was being used. This was an unintended side effect of work done to handle a throttling exception in the IMAP inbound email flow, and has been resolved by updating the system so that if the getReceivedDate is null, the date will be extracted from the mail header while processing dates in EmailMessageInfo class.
SR-115934 · Issue 170092
Corrected deadline escalation for reassigned work
Resolved in Pega Version 7.1.7
When reassigning work with an escalating deadline, the reassignment flowed properly but the corresponding SLA queue item was deleted after reassign and passed deadline events defined in the SLA rule were not triggered. This was traced to the new queuepage being created with a different processEvent activity, meaning Queue Manager could not locate it. A check has been added to ensure the correct queuepage is attached to reassigned work.
SR-115934 · Issue 170387
Corrected deadline escalation for reassigned work
Resolved in Pega Version 7.1.7
When reassigning work with an escalating deadline, the reassignment flowed properly but the corresponding SLA queue item was deleted after reassign and passed deadline events defined in the SLA rule were not triggered. This was traced to the new queuepage being created with a different processEvent activity, meaning Queue Manager could not locate it. A check has been added to ensure the correct queuepage is attached to reassigned work.
SR-115934 · Issue 174331
Corrected deadline escalation for reassigned work
Resolved in Pega Version 7.1.7
When reassigning work with an escalating deadline, the reassignment flowed properly but the corresponding SLA queue item was deleted after reassign and passed deadline events defined in the SLA rule were not triggered. This was traced to the new queuepage being created with a different processEvent activity, meaning Queue Manager could not locate it. A check has been added to ensure the correct queuepage is attached to reassigned work.
INC-155822 · Issue 618269
Locking added to avoid Null Pointer Exception for auto-populate property
Resolved in Pega Version 8.5.3
After configuring the auto populate property "OrgProduct" which referred to a data page, the system experiencing heavy load led to the property not getting properly initialized. This resulted in a WrongModeException and NullPointerException. To resolve this, the system has been updated to lock the requestor when Queue Processors execute their activity. This will prevent race conditions and concurrent modifications if other threads are accessing the same requestor.
SR-116716 · Issue 167507
Execute RDB runs in batch mode for very large data sets
Resolved in Pega Version 7.1.7
The executeRDB query was not able to handle very large large data sets, resulting in an OOM error after clicking on "Create Prior Authorization". ExecuteRDB (which is a select query) has been modified to run in batched mode, i.e. run the same query with limit on max rows, so as to avoid OOM when copying the whole result set into the memory object (similar to Report Definition paging).