SR-D75835 · Issue 539302
Added handling for Google Chrome drag and drop of Outlook email
Resolved in Pega Version 8.2.6
Attempting to drag and drop an email from Outlook to a case opened in Chrome resulted in the email being moved to the Outlook deleted folder. This was traced to Chrome defaulting to defining the "dropEffect" attribute as "none" when the expectation is it should be "copy". To resolve this, the recommended handling from Microsoft has been added as an event to make a copy (and not a move) an email from Outlook when dragged and dropped with Chrome.
SR-D76150 · Issue 539453
Logging updated for EmailListener and Data-Agent queue items
Resolved in Pega Version 8.2.6
In order to avoid the pr_sys_queue_ftsindexer table being overwhelmed with Data-Admin-Connect-EmailListener and Data-Agent-Queue instances for queued items, the Data-Admin-Connect-EmailListener and Data-Agent-Queue class definitions have been modified to filter queue items to incremental indexing if updates are from system and instance type is data- .
SR-D76291 · Issue 541014
Check added for Repositories before saving attachment
Resolved in Pega Version 8.2.6
When creating or updating a case through email listener, the Link-Attachment defaulted the pxStorageType to 'WebStorage'. This caused an issue when using PegaS3, which needs pxStorageType 'Repository'. To resolve this, a check has been added to see if Repositories are enabled, and if they are the storageType will be set accordingly.
SR-D77316 · Issue 539260
Resolved thread deadlock for rules upgrade process
Resolved in Pega Version 8.2.6
Platform upgrade was getting hung during the rules upgrade process. This was traced to a deadlock related to the conclusion cache entry for a property needing to make a call to declarative cache, where it tried to hold a read-write lock on a resource that was already locked by another thread. This has been resolved by replacing lock with tryLock to avoid deadlock.
SR-D78531 · Issue 542000
Encoding added for special characters in JFROG filenames
Resolved in Pega Version 8.2.6
A blank screen or the error "Unable to get the file from Repository" appeared when attempting to attach a file from JFROG Repository if the file name contained special characters. This has been resolved by modifying the artificatory URL generation to properly encode special characters during file download.
SR-D80668 · Issue 543867
Performance improvement for queries on Kafka partitions
Resolved in Pega Version 8.2.6
Even though there were multiple dataflow nodes available in the cluster, all requests were going to single node and causing system slowness. Investigation showed there was a queue processor rule that included the pxPartitionKey attribute which forced all records to be sent to a single partition by Kafka producers. This attribute has been removed.
SR-D89304 · Issue 519812
ClusterAndDBCleaner repaired
Resolved in Pega Version 8.2.6
An error in the logic order of events caused a compilation error for pyClusterAndDBCleaner, leading to old records created by the system/node utilities to not be automatically removed as expected. This has been corrected.
INC-158018 · Issue 633374
Archiving updated to include pxobjclass in CTE column list
Resolved in Pega Version 8.5.5
After enabling the case archival feature on a casetype, cases were getting stuck in the Archive-Ready state while being archived, and a 'column not found' error was seen. Investigation showed that the generated SQL statement used to retrieve the resolved case instances used a common table expression (CTE) whose columns were inskey, insclass, and parentinskey, and the query that referenced the CTE was attempting to compare the column pxobjclass when pxobjclass did not exist in the CTE's column list. To resolve this, the CTE column list has been updated to pzinskey, pxobjclass, and parentinskey to prevent the 'column not found error' from occurring, and the query that referenced the CTE was also updated to use the correct column names and aliases.
INC-159244 · Issue 627864
Bulk actions check in preserves declare expression legacy setting
Resolved in Pega Version 8.5.5
When a declare expression was saved in legacy mode with "Whenever used" selected in change tracking, performing a bulk check-in of the rule caused the expression to default to the new forward chaining method. This did not occur when using a direct check-in. Investigation showed this was caused by the check-in page holding a legacy value before the step execution, and has been resolved by adding a pre-save activity before the validation activity that will restore the .pyIsLegacy value from .pyExpressionTypeSelector, if set.
INC-162262 · Issue 654964
Query added to find time zone for MSSQL database
Resolved in Pega Version 8.5.5
The exception "com.microsoft.sqlserver.jdbc.SQLServerException: xp_regread() returned error 5, 'Access is denied.'" was generated when the AES agent PushDBSizeInfo was being run. This was traced to the GetDBInfo activity trying to retrieve the time zone of the MSSQL database by executing a query that used a Microsoft SQL routine to read the windows registry to get the current time zone. The error was not due to security within the SQL Server, but instead was caused by Microsoft Windows security related to the permissions on the registry keys for the users under which specific SQL Server processes were running. To resolve this, an update has been made to call a different query which will get the time zone for the SQL Server.