Deprecated and Removed Features
CAUTIONAdobe 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.
Deprecated Features
The table below lists features and capabilities that have been marked as deprecated with AEM 6.4. 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.
| Area | Feature | Replacement |
|---|---|---|
| UI |
Adobe does not plan to make further enhancements to the Classic UI. AEM 6.4 has the Classic UI included, and customers upgrading from earlier releases can keep using it as is. Note that Classic UI remains fully supported while being deprecated.
| Customers are advised to switch to use the new AEM UI. |
| Components |
Adobe does not plan to make further enhancements to the Foundation Components listed below. AEM 6.4 has the Foundation Components included, and customers upgrading from earlier releases can keep using them as is. Note that Foundation Components remain fully supported while being deprecated.
| Customers are advised to use the Core Components for future projects. Existing sites do not need to be changed. |
| Components |
Adobe does not plan to make further enhancements to the Foundation Components listed below. AEM 6.4 has the Foundation Components included, and customers upgrading from earlier releases can keep using them as is. Note that Foundation Components remain fully supported while being deprecated.
| Adobe does not plan to provide a replacement. |
| Portal Director |
The Portal Director is a set of features, that enables the hosting of AEM content via Portlet in 3rd party servers. Adobe does not plan to make further enhancements to the Portal Director feature under the location listed below. AEM 6.4 has the Portal Director included, and customers upgrading from earlier releases can keep using it as is. Note that Portal Direct remains fully supported while being deprecated.
| Adobe does not plan to provide a replacement. |
| Portlet Component | Portlet Components under /foundation/components/portlet enables the hosting of JSR Portlets in AEM as components. Adobe does not plan to make further enhancements to the Portlet Component feature. AEM 6.4 has the Portlet Component included, and customers upgrading from earlier releases can keep using it as is. Note that Portlet Component remains fully supported while being deprecated. | Adobe does not plan to provide a replacement. |
| Forms | Support for Adobe Central Migration Bridge service has been deprecated as Adobe Central product is no longer supported. | No replacement |
| Forms |
Deprecated use of JSONObject in Query and OperationOptions. The following APIs are deprecated:
| Use the IValueMap API |
| Forms | Deprecated Central Migration Bridge service. | No replacement is offered. |
| Assets | Assets Offloading has been deprecated starting with AEM 6.4. | |
| 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. |
Removed Features
The table below lists features and capabilities that have been removed from AEM 6.4. Prior releases had these capabilities marked as
deprecated.
| Area | Feature | Replacement |
|---|---|---|
| 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 Marketing 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. The ActivityMap plug-in provided by Adobe Analytics should now be used. |
| Components-Forms | Form Captcha (foundation/components/form/captcha) | Use the ReCaptcha by Google component instead |
| Components | Slideshow (foundation/components/slideshow) | No replacement |
| Components | Flash (foundation/components/flash) | No replacement |
| Components | Removed support to playback SWF files in the video component (foundation/components/video) | Use none-flash based video formats. |
| Components | Product Table (commerce/components/product_table) | No replacement |
| Task Management | Classic UI Task Management (https://experienceleague.adobe.com/libs/cq/taskmanagement/content/taskmanager.html?lang=en) | Deprecated since 6.0. Use the new task management that is combined with the workflow UI. |
| Workflow | Notification UI used between 5.6-6.2 (https://experienceleague.adobe.com/libs/cq/workflow/content/notifications.html?lang=en) | Workflow Inbox /aem/inbox |
| Forms | Export PDF to PDF/E-1 format using PDF Generator has been removed. | PDF Generator continues to support exporting PDF to PDF/A-1a/b, PDF/A-2a/b, and PDF/A-3a/b formats. |
| Forms | Support for images inside document fragments has been removed. | Interactive communications provides the capability to use images in print and web channels directly. |
| Forms | Out of the place upgrade | Support to perform out of the place upgrade is not available |
| Forms | Sidegrade for TarMK to DocumentMK migrations | You can export the data from older system and then import in a freshly setup system. For detailed instructions, see AEM Forms on JEE upgrade documentations |
| Forms | AEM Forms on JEE 32-bit installer not available. | Adobe has stopped shipping AEM Forms on JEE 32-bit installer. You can continue using 64-bit installer to install AEM Forms on JEE. |
| Forms | Removed support for using DAM images in Document Fragment Component. | You can use Image and Chart component in interactive communication’s print channel. If you are using adaptive document’s document fragment component in adaptive forms, it stops working after upgrading to AEM 6.4 Forms. |
| Forms | Removed the Adaptive Documents feature | You can use the interactive communications feature to create printed and web-based communications. If you use Adaptive Documents, install the compatibility package to continue using existing adaptive documents |
| Forms | Removed AEM Forms on JEE-specific landing page. | AEM Forms on JEE landing page is replaced with AEM landing page (https://experienceleague.adobe.com/aem/start.html?lang=en) |
| Forms | Removed support for default Captcha | Use reCAPTCHA service by Google. |
| Forms | Removed support for flash fields in AEM Designer. AEM Designer does not allow editing flash fields used in a form. | You can use AEM Designer released for a previous version to edit such forms. |
| Communities | Support for Captcha verification has been removed. | Use custom captcha integration (such as reCAPTCHA by Google) for verification. |