SR-D52523 · Issue 519165
Smart Prompt refreshes the cache after deleted instances
Resolved in Pega Version 8.4
When running an activity where a data type with one data model acted as key to the data type, the parameter declared was shown with an input box. If the down arrow was pressed in the input box, all the records stored for the data model (key) in data type were shown. If one record was deleted from the data type records and the activity run again, the deleted option was included in the list shown when pressing the down arrow. When a new record was added to the data type and the activity was run, the correct option list was shown in the dropdown and the deleted record was correctly omitted. This was caused by a difference in the APIs used for adding and changing the records and for deleting the records which resulted in the list not being refreshed after deletion of a record. To resolve this, a step has been added to reload the cache after a successful delete and commit.
SR-D54314 · Issue 517291
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-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.