The latest update of the Origin Characteristics behavior includes:

• You can now create multiple instances of the Origin Characteristics behavior in a property configuration.
• Requests to a Google Cloud Storage service are no longer authenticated with V2 signatures but with more secure V4 signatures.
• You no longer need to provide the bucket name for your Google Cloud Storage service as part of the V4 signing process.
• You no longer need to provide the hostname for your Amazon Web Services as this value is already present in the Origin Server behavior.

Image and Video Manager June 2020 release:

We’ve added three new Experimental transformations for you to use on staging or on pre-production traffic:

• Remove Color - removes a specified color from an image and replaces it with transparent pixels.
• Chroma Key - changes any color in an image within the specified volume of the HSL colorspace to transparent or semitransparent.
• Mono Hue - sets all hues in an image to a single specified hue of your choosing.

When activating a policy on production the Policy Rollout Speed Recommender provides multiple rollout periods to choose from. To help you select a rollout option we’ve included policy insights about the number of hits or percentage of your total traffic in the last 24 hours.

The latest mPulse update includes the following:

• Fixed an issue where colors for Custom timers were inconsistent with other timers. When the value of a timer increases it is displayed in red, indicating that an increase of a timer is a negative result.
• Introduced a new feature in the Waterfall dashboard: HTTP error codes on XHR beacons are now displayed.

Script Management Updates

• Improved User Interface - As part of our continuous improvement process we’ve updated the technology behind the Script Management UI. Changes to the user experience include updates to colors, fonts, and icons. 
• Bug Fix - Scripts categorized as low or medium now show the correct analysis icon. 

The latest mPulse update includes the following:

• Fixed an issue that in some cases caused charts to report numbers 10 times too low.

The latest mPulse update includes the following:

• Fixed an issue with Apple iPad device classification.
• Fixed an issue causing Native Android SDK error codes to be reported incorrectly.
• Fixed an issue with Android phone classification.
• Fixed an issue where Headless Chrome beacons were accepted even when “Include Bot Beacons” was disabled.

DataStream is now easy to find in Control Center!

• DataStream is directly available under the Common Services section in Control Center.
• DataStream has a new, more intuitive UI for better customer experience. DataStream’s features haven’t changed. These UI changes will make the configuration flow easy and support more modular options in the future.

The CloudTest 60 GA Release includes the following updates:

• Asynchronous updates for global properties.
• Split by HTTP protocol for targets/tests - The option to view target data for both HTTP and HTTP2, independently.
• Annotations for all widgets. These annotations can mark events in time, and can be commented on.
• Test Results Query API - Can be used to retrieve data generated by Cloud Test.
• Results Management API - Can be used to clean up unnecessary results.
• Added new cloud locations as follows: AWS: Hong Kong. Stockholm. Added new M5 server type to CloudTest grids. Azure: eastus2, westus2, francecentral, southafricanorth, uaenorth, eu-west–1 GCE: us-west2, europe-west6, europe-north1, asia-east2
• Bug fixes and improvements.

Upgrading from CloudTest 57/58 to CloudTest 60 may take a significant amount of time due to our upgrade to the Postgres10 DMBS. The time taken will vary and is dependent on the number of results on the customer’s system. Use the Results Management API to remove unnecessary results before migrating to CloudTest 60 to reduce the time it takes to update.

The latest mPulse update includes the following changes:

• Fixed an issue with the application of decimal places for currency and percentage custom metrics, which in some cases had caused numbers in those dashboards to display as higher than they actually were.

Script Management Bug Fix

• The akamai-sw-policy.json file no longer includes unexpected information when a policy is not present on the browser.