INC-209419 · Issue 704268
Email bot tags the incoming account correctly
Resolved in Pega Version 8.5.6
When an email bot was created and configured for two email accounts, for example [email protected] and [email protected], an incoming email that had both of the email addresses in the "TO" line correctly created two Work-Channel-Triage-Email cases, but the data on the triage case did not correctly mark the incoming email account in "pzIncomingEmailAccount" or "pyAccountId". This has been resolved with an update that will rely on pyListenerPage if pzIncomingEmailAccount is blank initially, and if pzIncomingEmailAccount is still blank the system will then iterate over the email address and fetch the email account from the channelconfig page.
INC-182423 · Issue 691798
Pull to refresh disabled during case submission
Resolved in Pega Version 8.5.6
Triggering a refresh (swipe down) on mobile while the spinning loading indicator was shown resulted in the error 'This action is not allowed' instead of being able to view the case. This has been resolved by disabling pull to refresh when there is any background network activity in progress.
INC-187230 · Issue 672472
Resolved exception during LDP processing
Resolved in Pega Version 8.5.6
A ConcurrentModificationException was appearing during the processing of Large Data Pages. This has been resolved with the addition of a lock on clear method in ConcurrentReplicatedPage.
INC-194932 · Issue 689290
Handling updated for offlineWorkIDs map
Resolved in Pega Version 8.5.6
Intermittent failures were seen when deleting attachments on Mobile. These were traced to pega.ui.DCUtils being undefined, and has been resolved by populating the offlineWorkIDs map for attachment-related actions.
INC-195519 · Issue 698496
Support added for using CFW when Pega server is unavailable
Resolved in Pega Version 8.5.6
Data synchronization changes have been added to allow Client for Windows to work in offline mode without an AppCache manifest.
INC-195601 · Issue 685769
Basereference context available for attach content control
Resolved in Pega Version 8.5.6
An "undefined" error occurred when attaching a file using the attach content control in the mobile harness. To resolve this, support has been added to run attachcontent in basereference context. This can be enabled by setting pega.attachToCtxPage to true.
INC-206049 · Issue 703470
Resolved activity registration error for Scan Barcode/QR Code
Resolved in Pega Version 8.5.6
Attempting to add the action 'Scan Barcode/QR Code' to a button generated the warning "Unauthorized request detected : Unregistered request encountered with params pyActivity:pzRunActionWrapper pySubAction:runAct pzActivity:pzScanCode". Investigation showed this was due to the pzScanCode activity referred to in pzpega_control_actions_scanCode.js file not being registered, and has been resolved by adding code to register the necessary events for both button and navigation.
INC-164383 · Issue 682542
ElasticSearch ClusterService logging updated
Resolved in Pega Version 8.5.6
In order to support enhanced troubleshooting, the default logging level for ElasticSearch ClusterService has been set to "ALL".
INC-168003 · Issue 655377
BIX Total Instance count matches manifest
Resolved in Pega Version 8.5.6
The BIX Manifest file was showing a count mismatch when the BIX Manifest and Extract files were shared with downstream teams, causing data to not be accepted by the downstream application. Investigation showed this occurred for an embedded page list property in the sequence that was missed and not considered. To resolve this, a DSS has been added: when BIX/generateAllEmptySubscriptForPageList is set to true, an empty subscript will be generated for the missed properties.
INC-173452 · Issue 666439
Quorum capability check added for external Elastic Search
Resolved in Pega Version 8.5.6
The error "java.lang.UnsupportedOperationException: Not supported for client/server mode at search.indexmanager.internal.ESIndexAdminHTTP.isQuorumAvailable" was appearing when attempting to use external Elastic Search to index a dedicated index, and the queue processor was running but showed multiple broken items. This has been resolved by adding a capability check with ES_INITIALIZE_EMBEDDED_CLUSTER to prevent a quorum check with external elastic search.