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
Oracle Field Service – Delivery Channels / Integrations	Support for legacy encryption protocols SSL 3.0, TLS 1.0, and TLS 1.1 in Delivery Channel configurations	Configuration updates must be completed before September 29, 2026 (documented in Oracle Field Service 26D readiness)	TLS 1.2 or Default Encryption (Delivery Channels will support Not Encrypted (HTTP), Default Encryption, and TLS 1.2 only)	Oracle Field Service 26D	Note This change applies only to outbound integrations configured through the Delivery Channels page in Oracle Field Service environments. You can verify whether you've Oracle Field Service or Oracle Fusion Field Service, by signing in and checking on the About page. To align Oracle Field Service with current industry security standards, support for the legacy encryption protocols SSL 3.0, TLS 1.0, and TLS 1.1 is being removed from Delivery Channel configurations. Delivery Channels will support only the following encryption options: Default Encryption and TLS 1.2. As a result, SSL 3.0, TLS 1.0, and TLS 1.1 will no longer be available in the Delivery Channel configuration page and cannot be selected when creating or modifying a Delivery Channel. Customers should review existing configurations, verify that receiving endpoints support TLS 1.2 or the Default Encryption option and update them before September 29, 2026 to avoid disruption in integrations involving Outbound Delivery Channels and Message Scenarios respectively.
Oracle Field Service Knowledge Configuration	Legacy Fusion Knowledge Classic Search API / V1 knowledge search	Oracle Field Service 27A	Semantic search and answer generation, commonly referred to as Golden Answer Search V2	Oracle Field Service 27A	Note This change applies only to Oracle Field Service environments with  Fusion Knowledge classic search. You can verify whether you've Oracle Field Service or Oracle Fusion Field Service, by signing in and checking on the About page. Oracle Field Service customers using legacy Fusion Knowledge classic search must upgrade their configuration to the latest knowledge search experience. This update is required because the Classic Search API is being retired (End of Notice Announcement). The new configuration enables semantic search and answer generation powered by Oracle AI, helping mobile workers find more relevant knowledge articles and concise answer summaries from the Field Service activity context. What Is Changing The legacy Classic Search API / V1 knowledge search option is being removed. Oracle Field Service customers who have configured Fusion Knowledge using the legacy classic search setup must update their Field Service configuration to use the newer knowledge search setup, commonly referred to as Golden Answer Search V2 or semantic search and answer generation. This screenshot shows the legacy page to configure Fusion Knowledge in Oracle Field Service: Legacy Semantic search and answer generation This screenshot shows the updated page to configure Fusion Knowledge in Oracle Field Service: Latest Semantic search and answer generation Who Is Impacted This change applies only to customers who meet both of these conditions: Customer who use Oracle Field Service with Oracle Fusion Knowledge Management. Customers whose current Field Service knowledge configuration is not setup with Semantic Search and Answer generation option (uses the legacy Classic Search API / V1 classic search setup). No Field Service setup change is required for customers who: Use Oracle Fusion Field Service. Do not use Fusion Knowledge in Field Service. Already use the latest semantic search and answer generation configuration. Impacted customers must review and update their Oracle Field Service Knowledge configuration before the Classic Knowledge removal in the 27A update. Customers should: Review the existing Knowledge configuration in Oracle Field Service. Identify whether the configuration is using the legacy Classic Search API / V1 search setup. Update the configuration to use semantic search and answer generation. Validate search behavior from the Oracle Field Service mobile worker experience. Complete the change before the 27A update to avoid disruption to knowledge article search. Follow the Oracle Field Service setup instructions for Oracle Field Service customers moving to the latest knowledge search https://docs.oracle.com/en/cloud/saas/field-service/faded/t-configure-knowledge.html

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	Note 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.