Deprecated and Removed Features

You are reading the AEM 6.3 version of Deprecated and Removed Features.
This documentation is also available for the following versions:  AEM 6.2  AEM 6.1 

Adobe constantly evaluates capabilities in the product and over time plans to replace capabilities with more powerful versions, or decides to re-implemented selected parts to be better prepared for future expectations or extensions.

Backwards compatibility is key when replacing capabilities, to make sure our customers investment in our technology is safe.

The general rule is: Capabilities are 1st announced to be deprecated, and the earliest removed in the following release. That gives customers at least one release cycle to adapt their implementation to the new version of the capability, before it might get removed.

Changes Relevant for Customers that Update

Following list are changes that have direct impact after update to AEM 6.3. They are changed behaviors that might requires changes in the project implementation.

Area Feature
Change

Deprecated Features

This section lists features and capabilities that have been marked as deprecated with AEM 6.3. Generally, feature 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
Foundation UI Shell 2.0 components UI Shell 3.0 components introduced with AEM 6.2
Foundation Deprecate renderReadOnly on Granite UI form components UI Shell 3.0 no longer uses this option
Foundation Deprecate Coral 3 coralui-component-badge Use coral-tag instead
Foundation Deprecate Coral 3 pathbrowser Use foundation-picker instead
Foundation Deprecate Coral 3 tags picker
/libs/cq/gui/components/common/tagspicker
Use /libs/cq/gui/components/common/coral/form/tagfield
Foundatino Deprecate Coral 3 user picker
/libs/granite/ui/components/coral/foundation/form/userpicker
Use /libs/granite/ui/components/coral/foundation/authorizable/autocomplete
Foundation Deprecate granite.ui.quickactions clientlib Use coral-quickactions
Foundation Deprecate granite.ui.notifications clientlib Use foundation-ui
Foundation Deprecate Sling Event Bridge Adobe strongly recommends to use the performance optimized ResourceChangeListener whiteboard instead.
Workflow Notification UI used between 5.6-6.2
(/libs/cq/workflow/content/notifications.html)
Workflow Inbox /aem/inbox
Workflow Project task list used between 6.0-6.2
(/libs/cq/core/content/projects/showtasks.html)
Workflow Inbox /aem/inbox
Classic UI JCR Event Notification Inbox in Classic UI
(/libs/wcm/core/content/inbox.html)
Recently changed/visited rail.
Sites Deprecate Server-side Redirect based on device capabilities using WURFL com.day.cq.wcm.mobile.core.impl.redirect.RedirectFilter  
Sites Deprecate Foundation Components /libs/foundation/components/mobile* Use Core Components
Sites Deprecate Marketing Campaign Management UI in Classic UI Use Offer Library UI
Sites Deprecate components /libs/mcm/components/cta* Use Core Components
Sites Deprecate components  /libs/mcm/components/newsletter Replaced with /libs/mcm/campaign/components
Sites Deprecated legacy Offline Importer in Classic UI No replacement
Assets Deprecate legacy API to manage /var/dam to /content/dam asset migration used in CQ 5.4 No replacement needed
Commerce Deprecate Classic UI Product Importer Use the new UI
Commerce Deprecate Classic UI Catalog Importer Use the new UI
Mobile Apps Stop using /content/phonegap Use /content/mobileapps instead
Mobile Apps Stop using /etc/clientlibs/mobile/content-sync Use /etc/clientlibs/mobile/content-sync-2 instead introduced with AEM 6.2
Mobile Apps Stop using Pushwoosh and Amazon SNS notification servicdes Use AEM Mobile SDK and it's notification support

Removed Features

This section lists features and capabilities that have been removed from AEM 6.3. Prior releases had these capabilites marked as depreacted.

Area Feature Replacement
Marketing Cloud Integrations

Removed legacy integration with Adobe Audience Manager

  • Built-in Page Tagging of AAM JS
  • Client-side Rules via synced AAM segments

Adobe recommends to leverage the next generation integration that leverages the User ID service:

  • Page Tagging via DTM (works since 6.0)
  • Client-side Rules: Replaced by server-side integration between Adobe Target and AAM.
Marketing Cloud Integrations Removed Global MBox component Recommendation is to switch to DTM based delivery of Adobe Target and leverage at.js
Marketing Cloud Integrations Removed legacy Publish Adobe Target Offer function that was used in the 1st generation integration Recommendation is to leveage the Adobe Target integration as introduced with AEM 6.2
Marketing Cloud Integrations Removed legacy Adobe Analytics impression importer and SAINT integration

Replacement for ImpressionsImporter is ReportImporter

SAINT integration uses ClassificationsService/ClassificationsTransformer

Foundation

On update to 6.3, a set of search index will no longer be used:

  • profiles
  • slingResource
  • damResolvedPath
  • users
  • groups
 
Foundation Removed Sling Background Servlet (org.apache.sling.bgservlets) Use Sling Jobs mechanism instead. See Apache Sling docs
Foundation Removed legacy HTML Library Manager  
Foundation Removed legacy com.day.cq.theme  
Foundation Removed unsed granite.ui.utils.clientlib and Coral.Colorpicker from granite.u.coralui3  
Foundation Removed legacy CQ login pages.  They were deprecated with CQ 5.5. Adobe recommends to use the 'Granite' login components and pages.
Foundation Removed legacy security APIs The com.day.cq.security.* API has been deprecated with CQ 5.5 as it was donated to the Apache Foundation. Adobe recommends to refactor the custom code and move to org.apache.jackrabbit.api.security.*
Foundation Removed legacy com.adobe.sightly.engine The com.adobe.sightly.engine API has been deprecated with AEM 6.1 as it was donated to the Apache Foundation. Adobe recommends to refactor the custome code and move to org.apache.sling.scripting.sightly
Foundation Removed legacy search predicates used in Touch-UI of 5.6 and 6.0. Further, the release upgrade logic that was used to rewrite them to the new format in 6.1 was removed.  
Sites Removed legacy CQ Statistics service. This is the servlet tracking page impressions that are shown in the Classic Site Admin. Recommendation is to use the integrated Adobe Analytics for measuring content efficiency. Please contact your Adobe account manage to find out if you are eligible for Adobe Analytics Essentials.
Sites Removed legacy com.day.cq.wcm.api.msm Was deprecated in 2010.
Sites Removed the Manuscript Editor UI AEM 6.2 introduced the Content Fragments that are replacing the Manuscripts. 
Sites Removed the Sites Importer UI from Classic UI. This capability was originially developered to create quick POC to get template from externally hosted sites.  
Assets Removed legacy API and workflows from Scene 7 integration from 5.6.1 no longer in use since 6.1  
Integration with DPS Classic The 'Publication UI' to manage content for Classic DPS apps has been removed. Customers that still need the AEM to Classic DPS integration can leverage the AEM Classic UI.
Sample Geometrixx Sites were fully removed from AEM 6.3 AEM 6.3 comes with a new set of samples sites, representing the state-of the-art of leveraging AEM for Sites, Communities, Assets and Mobile.

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.

Area
Feature
Annoucement
Java Language
Java VM AEM 6.3 is the last version that supports Java 7. The 2018 relase Java 8 is the minium Jave VM supported
Dispatcher Web Server
Oracle iPlanet By the end of 2017, Adobe will remove support for Oracle iPlanet Web Server 7
Foundation UI Framework Adobe is planning to deprecate the Classic UI in 2018. Customers are advised to plan to update to AEM 6.3 and follow on with switching to use the new UI. Adobe will provide a tool to help convert Component Dialogs from Classic UI to Coral 3 in 2017.
Foundation UI Framework Adobe is planning to deprecate the Coral UI 2 components in 2018. Coral UI 3 was introduced with AEM 6.2, and AEM 6.3 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 will provide a tool to help convert Component Dialogs from Coral 2 to 3 in 2017.

Any questions?

Have a question about this or any other AEM topic? Ask our Community.
Learn more about AEM topics on our help hub.
Was this helpful?

By submitting your feedback, you accept the Adobe Terms of Use.

Thank you for submitting your feedback.