What do I need to know about Oracle B2C Service deprecations?
Deprecations of Oracle B2C Service features/modules
Note: This answer applies to Oracle B2C Service. For information regarding deprecations in Oracle Field Service, refer to Answer ID 9376: Deprecations and Removals for Oracle Field Service..
Please see below for common Q&A about feature deprecations and scheduling.
What is deprecation?
Oracle B2C Service defines ‘deprecation’ as a status where a technology or feature is being phased out of the product and its use is discouraged, often to allow an improved technology or feature to take its place. The deprecation time period, typically 2 years (although extensions may be applied to specific product technologies/features), is the period from announced deprecation to removal of the feature from the product.
What happens during deprecation?
During the deprecation period, the deprecated technology/feature is not available for purchase or new implementations. The deprecated item is not enhanced or changed during the period; support and documentation may be limited. One or more replacement technologies/features are typically made available at the start of or during the deprecation period. The deprecation period is the best opportunity for sites to migrate off of the deprecated functionality to new or replacement functionality.
How do I know if a deprecation is relevant to my site?
Site administrators should review relevant notices for all in-process and completed deprecations based upon the current release of their production site. Information about migration and replacement technology/feature is provided in a related answer where available. Additional information about migration is available in the Upgrade Guides. These are available in the Documentation Overview answers for each version.
These features are within the 2-year deprecation period and will be removed in a future release. You should begin migration efforts to the replacement technology/feature as soon as possible.
These features are no longer available after the release noted below. You must begin migration efforts to the replacement technology/feature before your next scheduled update.
|Removal||Feature Area||Additional Information|
|19D||PHP Mail Files||Mail Files deprecation begins August 19, 2013 (a.k.a. mail scripts)|
|February 2017||Agent Console||Oracle B2C Service Legacy Console removed|
|February 2017||Accessibility Interface||Oracle B2C Service Accessibility Interface deprecation|
|November 2015||RightNow ODBC||Deprecation period ends for RightNow ODBC export|
|November 2012||XML API and CDI||Deprecation period ends for XML API and CDI|
|February 2016||WAP||Deprecation period ends for WAP|
|November 2011||Incident Thread Control||Deprecation period begins for v1 of Incident Thread Control|
|(also referred to as the 'Plain-Text Incident Thread Control')|
|May 2011||Direct SQL and IAPI||Deprecation period ends for Direct SQL and IAPI|
|November 2010||Classic Enduser Pages||Deprecation period ends for Classic End User Pages|
How can I stay informed of Oracle B2C Service Deprecations?
All deprecations are announced through the Service Update Notification Console, the Oracle Cloud Customer Connect and direct communications to administrators of affected sites. To receive automatic updates about Oracle B2C Service deprecations, site administrators are also encouraged to subscribe to this Answer by selecting the ‘Notify Me’ option (appears to the right, below Related Answers listing).