Adobe constantly evaluates product capabilities, to over time reinvent or replace older features with more modern alternatives to improve overall customer value, always under careful consideration of backward compatibility.
To communicate the impending removal or replacement of AEM capabilities, the following rules apply:
This process gives customers at least one release cycle to adapt their implementation to a new version or successor of a deprecated capability, before actual removal.
This section lists features and capabilities that have been marked as deprecated with AEM 6.5. Generally, features that are planned to be removed in a future release are set to deprecated first, with an alternative provided.
Customers are advised to review if they use the feature/capability in their current deployment, and make plans to change their implementation to use the alternative provided.
|Sites||Experience Fragments properties for Social Media Status.||22.214.171.124|
|Sites||Content fragment templates, for creating simple content fragments.||Model-based structured content fragments now.||126.96.36.199|
|Creative Cloud integration||AEM to Creative Cloud Folder Sharing was introduced in AEM 6.2 as a way to give creative users access to assets from AEM, so that they could open them in Creative Cloud applications and upload new files or save changes to AEM. A new capability released in Creative Cloud application, Adobe Asset Link, provides a much better user experience and more powerful access to assets from AEM directly from inside Photoshop, InDesign, and Illustrator. Adobe does not plan to make further enhancements to the AEM to Creative Cloud Folder Sharing integration. While the feature is included in AEM, customers are advised to use replacement solutions.||Customers are advised to switch to new Creative Cloud integration capabilities, including Adobe Asset Link or AEM desktop app.|
||Configuration described at AEM Security checklist.|
|DTM Tag Manager||The integration with DTM (Dynamic Tag Manager) is deprecated.||Switch to use Adobe Experience Platform Launch as a tag manager.|
|Adobe Target||With adding the ability for AEM to connect to Adobe Target service using the Adobe I/O based Adobe Target Standard API (Rest API) in AEM 6.5, the Target Classic API (XML) way is deprecated.||Reconfigure the integration to use the new API.|
|Adobe Target||Using the
||Switch to use
|Commerce||CIF REST was provided in 2018 as a set of microservices to enable integrations between AEM and commerce engines. After Adobe acquired Magento in mid 2018, Adobe decided to change its approach for two reasons. Magento has its own set of Commerce APIs (REST and GraphQL) and it’s not good practice to maintain two sets of APIs. Market trends indicated that customers were moving towards GraphQL, because it’s a more efficient way of querying data. In 2019, Adobe has released the new Commerce Integration Framework using Magento’s GraphQL APIs as the source of truth. Adobe doesn’t plan to make any further investment in CIF REST. Customers are advised to use the replacement solution.||For AEM-Magento integrations, switch to AEM CIF Archetype and AEM CIF Core Components. See AEM and Adobe Commerce integration using Commerce Integration Framework. Support for third party (other than Magento) integrations with the new approach is on our roadmap.|
|Components (AEM Sites)||Adobe does not plan to make further enhancements to most of the Foundation Components stored in
||Adobe recommends using the Core Components for future projects. Existing sites can remain as is or use the AEM Modernize Tools Suite to refactor the site to use Core Components.|
|Components (AEM Sites)||Design Importer Components
||Adobe plans to provide an alternative implementation of the use case in future releases.|
|Foundation||Granite Offloading Framework. Adobe does not plan to make further enhancements to the offloading framework that was introduced in CQ 5.6.1 to externalize asset processing.||Adobe is working on a next-generation cloud-native offloading framework.|
||Adobe recommends that customers use Selenium automation.|
|Developers||jQuery UI client library. Adobe does not plan to further maintain and update the jQuery UI client library that is shipped as part of the distribution (Quickstart)||Adobe recommends customers that still require jQuery UI for their code to add it into their project code base.|
|Developers||jQuery Animation client library (
||Adobe recommends customers that still require jQuery Animations for their code to add it into their project code base.|
|Developers||Handlebars client library. Adobe does not plan to further maintain and update the Handlebar client library that is shipped as part of the distribution (Quickstart)||Adobe recommends customers that still require Handlebars for their code to add it into their project code base.|
|Developers||Lawnchair client library. Adobe does not plan to further maintain and update the Lawnchair client library that is shipped as part of the distribution (Quickstart)||Adobe recommends customers that still require Lawnchair for their code to add it into their project code base.|
||Adobe recommends customers that are relying on the capability of the library to refactor their code to no longer use it.|
|Developers||Classic UI Dialog Editor in CRXDE Lite. Adobe does not plan to further enhance the Classic UI Dialog Editor that is shipped as part of the distribution (Quickstart)||No replacement is available.|
|Forms||AEM Forms integration with AEM Mobile is deprecated.||No Replacement is available.|
|Developers||Lodash/underscore client library. Adobe does not plan to further maintain and update the Lodash/underscore client library that is shipped as part of the distribution (Quickstart)||Adobe recommends customers that still require Lodash/underscore for their code to add it into their project code base.|
This section lists features and capabilities that have been removed from AEM 6.5. Prior releases had these capabilities marked as deprecated.
|Integration with Experience Cloud||You could synchronize your assets with Experience Cloud using a configuring via Adobe I/O. Adobe Experience Cloud was formerly called Adobe Experience Cloud.||If you have any queries, contact Adobe Customer Support.|
|Analytics Activity Map||The version of the Activity Map that is included within AEM.||Due to security changes within the Adobe Analytics API, it is no longer possible to use the version of Activity Map that is included within AEM. Use the ActivityMap plug-in provided by Adobe Analytics.|
|Integrations||ExactTarget integration has been removed from the default distribution (Quickstart) and it is no longer available.||No replacement.|
|Integrations||Salesforce Force API integration has been removed from the default distribution (Quickstart) and is now an extra package to install from Software Distribution.||The feature is still available.|
|Forms||Support for Adobe Central Migration Bridge service has been removed as Adobe Central product is no longer supported.||No replacement.|
|Forms||Single-hop upgrade from LiveCycle ES4 SP1 to AEM 6.5 Forms on JEE is not available||See available upgrade paths in AEM Forms upgrade documentation.|
|Forms||Removed UPD based clustering support from AEM Forms on JEE||You can use only TCP-based clustering in AEM Forms on JEE. If you upgrade a UDP multicast server from a previous version to AEM 5.5 Forms on JEE perform manual configurations to switch to TCP based gemfire clustering. For detailed instructions, see Upgrade to AEM 6.5 forms on JEE|
|Developers||Firebug Lite has been removed from the default distribution (Quickstart)||Use the browser built-in developer consoles|
|Assets||The assets offloading feature is removed in Adobe Experience Manager 6.5.||No replacement is available.|
||Classes and Slightly cache is stored under the Apache Sling Commons FileSystem ClassLoader bundle. You can check the bundle number in the AEM Web Console and remove the cache folder directly from the file system (
This section is used to pre-announce the upcoming changes in the future releases. The announced changes are not yet effective but will impact customers. For example, the features are not yet deprecated but impacts the users after deprecation. These updates are provided for planning purpose.
|Foundation||UI Framework||Adobe is planning to deprecate the Coral UI 2 components in 2019. Coral UI 3 was introduced with AEM 6.2, and AEM 6.5 is fully based on Coral 3. Adobe recommends customers and partners that have build custom UIs with Coral 2 to refactored them to Coral 3. Adobe is providing a tool to convert Coral 2 dialogs to Coral 3 - Read more.|