SR-D56978 · Issue 523328
Enhancements added for mail handling
Resolved in Pega Version 8.4
Numerous EmailClientRuntimeExceptions were seen during listener execution. This was traced to a null folder name in the email client configuration that was expected during listener processing, and investigation showed it had been created during a race condition in creating configuration objects for sender and receiver. Handling has been added to address this conflict. As part of addressing the related issues, enhancements have been made to enable the email listener configuration to utilize all available nodes in a cluster to improve scalability for high load conditions and increased ability to process more messages per hour.
SR-D63579 · Issue 528000
Enhancements added for using AWS file repositories
Resolved in Pega Version 8.4
Enhancements have been added to improve the use of AWS file storage: - Logging for AWS SDK connection metrics can be activated on a per-repository basis, either through the ruleform or through the DSS `storage/class/:/enableMetrics`. - INFO logging can be enabled on PegaAWSSDKMetricReporter to periodically output averages of recorded metrics for all registered S3 repositories with metric collection enabled, or INFO logging can be enabled on PegaAWSRequestMetricCollector to output recorded metrics on every client call for all registered S3 repositories with metric collection enabled. - The interval at which PegaAWSSDKMetricReporter logs metrics at can be configured with the DASS `storage/AWSSDK/metricReportingInterval`. This DASS is a system-wide setting, and not a per-repository setting. The default reporting interval is 90 seconds, and metric collection is disabled on all repositories by default.
SR-D63912 · Issue 531206
Context retained during nested automation
Resolved in Pega Version 8.4
Issues were seen with context being passed correctly with automation. When a Data Page that was used to abstract the call to a REST API used a Data Transform which in turn used a Data Page which also used a call to a REST API to retrieve an OAuth Token, an error appeared. The same worked when a URL was provided on the Connect REST. When a service case was launched but a Flow Action wasn't submitted, then another service case was added and submitted, the post-processing robotic automation activity used the run robotic automation activity from the previous service case instead of the current service case targeted for completion. This has been resolved by updating the webwb • pzpega_ui_doc_submit.js file to pass the correct MDIContext based on the event target of FA submission while invoking RDA automation.
SR-D65362 · Issue 526933
Enhancements added for using AWS file repositories
Resolved in Pega Version 8.4
Enhancements have been added to improve the use of AWS file storage: - Logging for AWS SDK connection metrics can be activated on a per-repository basis, either through the ruleform or through the DSS `storage/class/:/enableMetrics`. - INFO logging can be enabled on PegaAWSSDKMetricReporter to periodically output averages of recorded metrics for all registered S3 repositories with metric collection enabled, or INFO logging can be enabled on PegaAWSRequestMetricCollector to output recorded metrics on every client call for all registered S3 repositories with metric collection enabled. - The interval at which PegaAWSSDKMetricReporter logs metrics at can be configured with the DASS `storage/AWSSDK/metricReportingInterval`. This DASS is a system-wide setting, and not a per-repository setting. The default reporting interval is 90 seconds, and metric collection is disabled on all repositories by default.
SR-D67211 · Issue 534062
Context retained during nested automation
Resolved in Pega Version 8.4
Issues were seen with context being passed correctly with automation. When a Data Page that was used to abstract the call to a REST API used a Data Transform which in turn used a Data Page which also used a call to a REST API to retrieve an OAuth Token, an error appeared. The same worked when a URL was provided on the Connect REST. When a service case was launched but a Flow Action wasn't submitted, then another service case was added and submitted, the post-processing robotic automation activity used the run robotic automation activity from the previous service case instead of the current service case targeted for completion. This has been resolved by updating the webwb • pzpega_ui_doc_submit.js file to pass the correct MDIContext based on the event target of FA submission while invoking RDA automation.
SR-D72368 · Issue 534332
Enhancements added for using AWS file repositories
Resolved in Pega Version 8.4
Enhancements have been added to improve the use of AWS file storage: - Logging for AWS SDK connection metrics can be activated on a per-repository basis, either through the ruleform or through the DSS `storage/class/:/enableMetrics`. - INFO logging can be enabled on PegaAWSSDKMetricReporter to periodically output averages of recorded metrics for all registered S3 repositories with metric collection enabled, or INFO logging can be enabled on PegaAWSRequestMetricCollector to output recorded metrics on every client call for all registered S3 repositories with metric collection enabled. - The interval at which PegaAWSSDKMetricReporter logs metrics at can be configured with the DASS `storage/AWSSDK/metricReportingInterval`. This DASS is a system-wide setting, and not a per-repository setting. The default reporting interval is 90 seconds, and metric collection is disabled on all repositories by default.
SR-D17418 · Issue 498723
Attached note header displays properly in Hebrew locale
Resolved in Pega Version 8.4
With the locale set to Hebrew, the whole portal is presented correctly from right to left, but when opening a case note (attached email) the header was not displayed as right to left. This has been resolved by updating the 'DisplayNote' HTML of class 'Data-WorkAttach-Note' and 'Show' HTML of class 'Data-Corr-Email' to use locale information from the operator.
SR-D17575 · Issue 492689
Survey route to work queue option restored for smartshape
Resolved in Pega Version 8.4
After upgrade, routing to workqueue was no longer available for the new create survey smart shape. This has been restored.
SR-D18589 · Issue 495717
Google Map API updated
Resolved in Pega Version 8.4
When using Address Map control with enabled markers whose source is a datapage, the location in the map was redirected as expected to the address populated by the datapage, but the marker overlay that appeared by default containing address details and a link to "Open in Google Maps" did not load. Clicking on random places on the map caused it to load correctly. This has been corrected with the creation of a custom activity to get section markup that will use reload section with proper context to fix the issue. In addition, enhancements have been made to enable automatic upgrade of existing apps which use Address Map to use pxMap by auto-generating pxMap from the existing configuration. Properties set in Address Map's design time configuration should be mapped to corresponding properties in pxMap as given below. If report definition, clipboard page. or list property was used as marker source, a data page will need to be created manually. 'Starting Lat, Long' property is mapped to 'Custom initial lat / long' 'Markers source' is mapped to 'MARKERS' as follows: - 'None' to 'None' - 'Data page' to 'Data page', 'Property for location' -> 'Location property', 'Marker info section' -> 'Info section' - 'Property' to 'Property', 'Address property' -> 'Address property', 'Allow marker repositioning to change the address value' -> 'Drag marker position to update address value', 'Report lat long in property' -> 'Lat / long logging property', 'Report incorrect address' and 'Error message' is ignored at this time - 'Report definition' is ignored - 'Clipboard page' is ignored - 'List defined on property' is ignored 'Visibility' and 'Tour ID' are mapped 1to1 It is also possible to disable rendering of the Map control from the Address Map configuration: when switched off, pxAddressMap will be generated instead of pxMap.
SR-D21004 · Issue 492467
Corrected case comparison to prevent completed cases being routed to error workbasket
Resolved in Pega Version 8.4
Some cases were routing to the sync error workbasket even while being resolved. Investigation showed that pzSetDeferWrite was comparing the serverside assignhandle with the assignahandle sent by the client upon sync, but since the client was sending assignahandle in lowercase (reproduced if workid prefix is customized), the comparison was failing. To resolve this, the AI has been modified to pass the pzInskey as uppercase to the pzSetDeferWrite activity.