Oracle Field Service Cloud 24C What's New

IMPORTANT Actions and Considerations

REPLACED OR REMOVED FEATURES

Features and technical components of the solution may be removed or replaced to enhance the security, performance, and overall quality of the cloud service. When this occurs, the deprecation of a feature or component will be announced in advance, allowing customers sufficient time to anticipate the change and transition to any enhanced replacement feature/component. After the deprecation is announced, the deprecated feature or component will remain in the solution until the planned removal date and will not be enhanced or made compatible with other new features.

New Deprecations/ Removals

Previously-Announced Deprecations

Application Area	Removed Feature	Planned Removal	Replacement Feature	Replaced In	Additional Information
Work Zones	Travel Areas	25C	OFS will dynamically determine the set of travel data to be sent for automatic activity assignment in routing requests.	-	Travel Areas are primarily used to group travel data to be sent to the routing engine for automatic activity assignment. However, the manual configuration of Travel Areas often results in areas that are not optimally sized, which causes data transmission inefficiencies. With the 25C update, Travel Areas will be removed from OFS, and the system will dynamically calculate travel-related data to be sent to each routing request based on factors such as work zones of activities, buckets, and past data. This will streamline the process and enhance efficiencies. The concept of Travel Areas will be removed from all parts of the system, including Configuration > Work Zones, Statistics API's, and the Travel Statistics Report.
Delivery Channels for Message Scenarios	Support for HTTP 1.0	25D	All existing Delivery Channels will be automatically transitioned to HTTP 1.1 with the 25D update.	-	As a part of our continuous efforts to enhance security, reduce latency, and optimize performance, we are deprecating support for HTTP 1.0 with the 24B update. Beginning with the 25D update, Outbound Delivery Channels will exclusively support HTTP 1.1. Please review your integrations with the OFS system and verify the necessity of adjustments to ensure compatibility with HTTP 1.1. We highly recommend fully validating your integrations by changing the HTTP version within the Delivery Channel settings (Configuration > Message Scenarios > Channel) to HTTP 1.1 in your Test environment before applying the changes to your Production environment. If the HTTP version of the configured Delivery Channels have not been set to HTTP 1.1, they will be automatically switched to HTTP 1.1 upon the 25D update.

Application Area

Removed Feature

Planned Removal

Replacement Feature

Replaced In

Additional Information

Work Zones

Travel Areas

25C

OFS will dynamically determine the set of travel data to be sent for automatic activity assignment in routing requests.

Travel Areas are primarily used to group travel data to be sent to the routing engine for automatic activity assignment. However, the manual configuration of Travel Areas often results in areas that are not optimally sized, which causes data transmission inefficiencies. With the 25C update, Travel Areas will be removed from OFS, and the system will dynamically calculate travel-related data to be sent to each routing request based on factors such as work zones of activities, buckets, and past data. This will streamline the process and enhance efficiencies.

The concept of Travel Areas will be removed from all parts of the system, including Configuration > Work Zones, Statistics API's, and the Travel Statistics Report.

Delivery Channels for Message Scenarios

Support for HTTP 1.0

25D

All existing Delivery Channels will be automatically transitioned to HTTP 1.1 with the 25D update.

As a part of our continuous efforts to enhance security, reduce latency, and optimize performance, we are deprecating support for HTTP 1.0 with the 24B update. Beginning with the 25D update, Outbound Delivery Channels will exclusively support HTTP 1.1.

Please review your integrations with the OFS system and verify the necessity of adjustments to ensure compatibility with HTTP 1.1. We highly recommend fully validating your integrations by changing the HTTP version within the Delivery Channel settings (Configuration > Message Scenarios > Channel) to HTTP 1.1 in your Test environment before applying the changes to your Production environment. If the HTTP version of the configured Delivery Channels have not been set to HTTP 1.1, they will be automatically switched to HTTP 1.1 upon the 25D update.