Deprecated and Removed Features
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/replacement of AEM capabilities, the following rules apply:
- Announcement of deprecation comes first. While deprecated, capabilities are still available, but they will not be further enhanced.
- Removal of deprecated capabilities will occur in the following major release at the earliest. Actual target date for removal will be announced.
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 make use of the feature/capability in their current deployment, and make plans to change their implementation to use the alternative provided.
|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 CC 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 strongly advised to use replacement solutions.
|Customers are advised to switch to new Creative Cloud integration capabilities, including Adobe Asset Link or AEM desktop app. Please review AEM and Creative Cloud Integration Best Practices for more details.|
|Adobe Search & Promote|
The integration with Adobe Search & Promote is deprecated.
Adobe does not plan to make further enhancements to the Search & Promote integration. Note that Search & Promote integration remains fully supported while being deprecated.
|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 mbox.js based integration with Adobe Target in AEM is deprecated.||Switch to use at.js 1.x|
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:
1. Magento has its own set of Commerce APIs (REST and GraphQL) and it's not good practice to maintain two sets of APIs
2. 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 strongly advised to use the replacement solution.
Have a look at AEM and Magento Integration using Commerce Integration Framework for more information.
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 /libs/foundation/components.
Look for the cq:deprecated and cq:deprecatedReason property in the component folder.
AEM 6.5 has the Foundation Components included, and customers upgrading from earlier releases can keep using them as is. Further, the Foundation Components remain fully supported while being deprecated.
|Customers are advised to use 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 /libs/wcm/designimporter/components have been marked as deprecated starting 6.5. Adobe does not plan to make further enhancements to that implementation of the design importer.||Adobe is planning to provide an alternative implementation of the use case in future releases.|
|Components (AEM Forms)|
Signature step allows users to verify and sign an adaptive form. In previous releases, the signature step could use both Adobe Sign and Scribble Signature components as signature fields. In AEM 6.5 Forms, Scribble Signature-based signing experience of Signature Step is deprecated.
Granite Offloading Framework
Adobe does not plan to make further enhancements to the offloading framework that was introduced in 5.6.1 to externalize asset processing.
|Adobe is working on a next-generation cloud-native offloading framework.|
Adobe does not plan to make further enhancements to the hobbes.js user interface testing framework.
|Adobe recommends that customers use Selenium automation.|
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.|
jQuery Animation client library (granite.jquery.animation)
Adobe does not plan to further maintain and update the jQuery Animation client library that is shipped as part of the distribution (Quickstart)
|Adobe recommends customers that still require jQuery Animations for their code to add it into their project code base.|
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.|
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.|
Granite.Sling.js client library
Adobe does not plan to further enhance the Granite.Sling.js client library that is shipped as part of the distribution (Quickstart)
|Adobe recommends customers that are relying on the capability of the library to refactor their code to no longer use it.|
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)
This section lists features and capabilities that have been removed from AEM 6.5. Prior releases had these capabilities marked as deprecated.
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 plugin provided by Adobe Analytics .
ExactTarget integration has been removed from the default distribution (Quickstart) and it is no longer available.
Salesforce Force API integration has been removed from the default distribution (Quickstart) and is now an extra package to install from PackageShare.
Feature is still available.
Support for Adobe Central Migration Bridge service has been removed as Adobe Central product is no longer supported.
Firebug Lite has been removed from the default distribution (Quickstart)
Use the browser built-in developer consoles
The Assets offloading feature has been removed in AEM 6.5
system/console/slingjsp is removed is no longer available in AEM 6.5.
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 ( crx-quickstart/launchpad/felix/bundle<ID> ).
Pre-announcement for Next Release
This section is used to pre-announce changes in future release, that are not deprecated, but will impact customers. These are provided for planning purpose.
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 .