SR-D62755 · Issue 522827
Enhanced diagnostic logging for Email Listener failures
Resolved in Pega Version 8.1.8
In order to better diagnose issues where the email listener entered a disabled state as soon as it was started, a catch block has been added to enhance logging the reason of failure
SR-D64558 · Issue 527676
AttachmentContent supports S3 storage
Resolved in Pega Version 8.1.8
Using a D_AttachmentContent data page to display the contents of an attachment by way of the pyGetAttachmentContent activity worked when using the Pega database for storage, but generated an error stating CMIS access was disabled after switching to S3 storage. This was traced to restrictions on Link-Attachment pages in Step 2, Line 64 of pyGetAttachmentContent to enable attachment stream retrieval from web storage and repositories by D_AttachmentContent, which has now been removed. In addition, pyGetAttachmentContent has been updated to behave the same whether a Link-Attachment page or Data-WorkAttach page is provided when populateAttachStream is set to false, and the rule documentation (description/usage) has been updated accordingly.
SR-D71669 · Issue 540099
Logic trimmed for better Listener performance
Resolved in Pega Version 8.1.8
After multiple email listeners with Data indexing were enabled, the FTSIndexer queue was filling with Email Listener instances. Investigation showed that although Listener Management has logic for updating the last access time of all listeners by using APIs, the Email Listener was explicitly opening the email listener rule to update the last access time every time it was run. This has been corrected.
SR-D76291 · Issue 541013
Check added for Repositories before saving attachment
Resolved in Pega Version 8.1.8
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-D27161 · Issue 503154
Step staus fail logic updated to handle agent activity exception
Resolved in Pega Version 8.2.4
Attempting to execute an advanced agent containing logic that set a step status to fail resulted in the error "Agent activity disabled due to execution errors; ErrorMsg: unable to execute agent: Cannot obtain a lock on instance as Requestor already has the lock ". This was traced to a backwards compatibility issue with previous work done to handle cases where agent activity requires authentication and agent has "bypass auth" flag set to false. Agent activity is not allowed to execute by the engine, and to show this scenario as exception case instead of showing it as running in admin studio, changes were made to rely on step status as the engine internally sets step status to false in this case. However, this inadvertently affected use cases where agent activity sets the status as fail in its logic. To resolve this, the system has been updated to handle the exception case and not consider StepStatus.
SR-D38492 · Issue 505489
Batching now enabled when using IH Summary shape in substrategies
Resolved in Pega Version 8.2.4
Batching was not being enabled when using IH Summary shape in substrategies. This was traced to the IH_SUMMARY_CACHE field not automatically being passed to sub-strategies, and has been corrected.
SR-D32332 · Issue 502269
Removed unneeded table name calculation
Resolved in Pega Version 8.2.4
After giving short names (less than 30 characters) for "To Table", saving did not produce an error, but an error was thrown during Check In. Investigation showed that while checking in the extract rule, a block of code in the Rule-Utility-Function validateTreeProperties was being executed to recompute the pagelist's table name instead of using the name provided by the user. To resolve this, the RUF has been modified to not execute this block of code during check-in of the extract rule. The validation will be seen during save if the 'To field' has more than 30 characters.
SR-D26160 · Issue 504069
Corrected duplicate records being inserted in to the index table
Resolved in Pega Version 8.2.4
Rows in the index table were duplicated. This was traced to a logic error on the ClipboardPage relating to workObject2, and has been resolved.
SR-D38450 · Issue 505656
Added workaround to handle HiddenPropertiesToIgnore when a page is in Read Only mode
Resolved in Pega Version 8.2.4
A 'WrongModeException' was generated while trying to use the Data Transform pxHiddenPropertiesToIgnore to remove system properties from page. When the Datapage was set to Editable/Savable mode, the Activity ran without an error and executed the Data transform. When the Datapage was in Read only mode, the error occurred. This was traced to a process that previously was allowed to set a page to an empty string, but which was removed during recent work. To resolve this, four instances of pxHiddenPropertiesToIgnore that included Single Page Value properties have been updated by moving them to the bottom of the Data Page and changing them to an "Update Page" from a "Set".
SR-D33934 · Issue 503333
Parent case lock properly released when child case is resolved
Resolved in Pega Version 8.2.4
After creating Parent-Child casetypes with default locking where the child case had the “Allow access to parent” check box checked, the temporary lock acquired on the parent during resolution of the child case was not released afterwards. If “Allow access to parent” was not checked, then the locks were released on both the parent and the child. This was traced to a combination of parameters used by the openIfStale() API where aUnlockOnCommit could be set to false despite the provided locking strategy expecting it to be true, as well as honoring UnlockOnCommit when maintainLockingStrategy is false. To resolve this, the system has been updated to always check whether the lock is available in the map already and if it is, then set unlockonCommit to true. Otherwise, under all cases, honor the passed-in unlockOnCommit value.