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

Application Area

Removed Feature

Planned Removal

Replacement Feature

Replaced In

Additional Information

Assignment Assistant

'Use Assignment Assistant on Dispatch Console' setting

25D

The Assignment Assistant feature will be active in all Field Service environments.

If you do not already have this feature enabled, it is recommended that you review the Assignment Assistant documentation and begin your implementation process soon. All dispatchers and any field resources authorized to assign or move activities should be considered in your implementation and informed of the upcoming changes.

We also encourage you to introduce Move Reasons as part of your Assignment Assistant implementation. This can provide valuable insight into understanding the manual efforts being made by dispatchers and identify opportunities for further automation. Refer to the Move Reasons Enhancements documentation for details.

Oracle Field Service Single Sign On Login Policy

Oracle Field Service Personal Identification Number (PIN) for SSO Login Policy

25C

Offline Application Unlock via Device Biometric for SSO Login Policy

25C

With the 25C update, Oracle Field Service will introduce enhanced security measures for users authenticated via SSO Login policies who find themselves working offline. In scenarios where application access needs to be restored for security reasons, such as a re-login timeout configured directly in the Identity Provider (IdP), Oracle Field Service will unlock access to the application by prompting the user to confirm their identity through the default authentication method configured on their device. This could include the use of biometric data, such as a fingerprint or face recognition scan, or by entering the secure PIN code.

To help users prepare for this transition, additional details on the new capability will be provided in the 25A What's New document. We encourage all users to review this information to familiarize themselves with the new authentication options and ensure a smooth transition when the update is implemented in 25C.

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.