SR-D75649 · Issue 547565
OrgChartWorkGroup update issue resolved
Resolved in Pega Version 8.1.8
The instances of Index-PegaFS-Data-OrgChartWorkGroup table were corrupted after adding a new department via the landing page. This was traced to the missed scenario of a Page-Copy with declare index present in it, and has been resolved.
SR-D84880 · Issue 546890
Null check added to resolve addmapcasetomap error
Resolved in Pega Version 8.1.8
Using a createcase flow shape to create child cases by looping on a page list on the parent case resulted in pzaddmapcasetomap throwing an exception related to the activity pzLoadCaseHierarchyWrapper in step 5. This was traced to a page being removed after the list of pages was received in findPageByHandle, and has been resolved by adding a null check.
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.
INC-134932 · Issue 578544
Timeout for node to join cluster increased and made configurable
Resolved in Pega Version 8.5.1
Hazelcast timeouts were causing application restart failures. This was traced to a rare case scenario of heavy processing on the primary node causing the new node to not be able to join the cluster within the designated 5 minute threshold. To compensate for this, the default time to join has been increased to 9 minutes and a prconfig setting has been added to configure the time setting.
INC-133270 · Issue 581839
Automatic agent restart added for temporary connection issues
Resolved in Pega Version 8.5.1
An agent that was stopped due to an issue with the database connection did not recover when the connection was reestablished. To resolve this, updates have been made that will handle an automatic restart of the agents when there are temporary connection issues.
INC-135359 · Issue 587038
CORS header configuration added for Stream tier
Resolved in Pega Version 8.5.1
An enhancement has been added that allows setting the CORS header (Access-Control-Allow-Origin) to allow *.DOMAIN.com on Stream tier (/stream/view & /stream/click) calls by way of the setting /stream/httpHeaders .
INC-134069 · Issue 583024
Added Kafka logging
Resolved in Pega Version 8.5.1
In order to help diagnose issues encountered during Kafka background processing, additional logging has been added to QueueProcessorDatasetHandler.