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 |
|---|---|---|---|---|---|
|
Oracle Field Service Single Sign On Login Policy |
Oracle Field Service Personal Identification Number (PIN) for SSO Login Policy | TBD |
Offline Application Unlock via Device Biometric for SSO Login Policy |
TBD |
This feature was initially announced for removal in 25C. However, the removal has now been postponed. New timelines for this change will be communicated in future updates. 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 through the What’s New document as soon as the new update version has been confirmed. We encourage all users to review this information once available to become familiar with the new authentication options and ensure a smooth transition. |
| 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. |
|
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. |
- |
This information applies only to Oracle Field Service environments, where Delivery Channel configuration is a legacy feature available to these customers. 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 Oracle Field Service 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. |
| Work Zones | Travel Areas | 26B | Oracle Field Service will dynamically determine the set of travel data to be sent for automatic activity assignment in routing requests. | - |
This feature was initially announced for removal in 25C; it will now be removed in 26B. 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 26B update, Travel Areas will be removed from Oracle Field Service, 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. |
| Oracle Fusion Field Service - Configuration Section - User Types | User Types General Tab > Field Restrictions > Hide All Activities, Hide Activity Fields and Configure Activity Fields will be removed for ONLY those customers NOT relying on the feature |
25D | For customers not relying on the feature, there's no replacement needed - your experience remains unchanged. | N/A | Customers using the Field Restrictions > Hide All Activities, Hide Activity Fields and Configure Activity Fields can continue to do so; it remains fully supported, and there are no plans to deprecate it at this time. |
| Oracle Fusion Field Service Application Configuration | Oracle Fusion Service and Service Logistics Application Configuration | 26A | Unified Workflows Across Fusion Field Service and Fusion Service | 25D |
Oracle Fusion Field Service now provides out-of-the-box connectivity between Oracle Fusion Service Work Orders and Oracle Field Service Activities. No additional setup or configuration is required for this connectivity. If you require continue use of Fusion Service – Field Service accelerator, you can set it up following the instructions in the provided guide. https://docs.oracle.com/en/cloud/saas/fusion-service/faefs/integrating-fusion-service-with-field-service.pdf To use Fusion Service Logistics - Field Service Accelerator, follow the instructions mentioned in the below: guide This change only applicable for Oracle Fusion Field Service customers. |
| Oracle Fusion Field Service Application Configuration | Oracle Analytics | 26A | Oracle Autonomous Database | 25D |
The direct connectivity from Oracle Field Service to Oracle Analytics will not be available from 26A. You can continue to utilize your OAC dashboards or create new dashboards in OAC using Oracle Field Service data based on the following configuration.
OAC customers already configured an ADW database system for saving OAC data, after migration tables won't be deleted from the ADW database. Realtime tables data flow will work as expected. For Daily tables and tables supporting both Daily & Realtime, wait for the next scheduled daily job to get the data in the target application. |
| Oracle Fusion Field Service Application Configuration | Oracle HCM | 26A | Integrating with Oracle HCM Cloud Using an Oracle Integration Accelerator | 25D |
This application is no longer required for Oracle Fusion Field Service and Oracle Field Service customers. Mobile worker management, user creation, and administration in Oracle Fusion Field Service now follow the Fusion standards outlined in the documentation below: Fusion Field Service customers can continue using the Oracle HCM Accelerator to retrieve employee work availability and job profiles from Oracle HCM Cloud. Details are available in the documentation below: https://docs.oracle.com/en/cloud/saas/field-service/faint/c-overview.html#Step-1:-Prerequisites For Oracle Field Service customers, the latest functional flows are described here: |