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. Also, as Adobe Experience Manager as a Cloud Service provides a cloud-native deployment model, certain capabilities and features were replaced by cloud-native counterparts.
To communicate the impending removal/replacement of Experience Manager 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 in Experience Manager as a Cloud Service. Typically, features 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.||The feature will be removed soon.|
|Sites||Template-based simple content fragments.||Model-based structured content fragments now.|
||Asset ingestion uses asset microservices now.|
|Assets||Upload assets directly to Experience Manager. See deprecated asset upload APIs.||Use Direct binary upload. For technical details, see direct upload APIs.|
|Assets||Certain workflow steps in
||Asset microservices provide a replacement for many workflows. For custom processing, use post-processing workflows.|
|Assets||FFmpeg transcoding of videos.||For FFmpeg thumbnail generation, use Asset microservices. For FFmpeg transcoding, use Dynamic Media.|
|Foundation||Tree replication UI under the replication agent’s “Distribute” tab (removal after September 30, 2021)||Manage publication or publish content tree workflow approaches|
|Foundation||Neither the replication agent admin screen’s Distribute tab nor the Replication API can be used to replicate content packages over 10MB (enforcement after September 12, 2022)||Manage publication or publish content tree workflow approaches|
| Foundation | Neither the replication agent admin screen’s Distribute tab nor the Replication API can be used to replicate content packages over 10MB. Instead, use either Manage publication or publish content tree workflow |
This section lists features and capabilities that have been removed from Experience Manager with Experience Manager as a Cloud Service.
|Area||Feature||Replacement||Target Removal Date|
|User Interface||Classic UI is removed from the product user interface. A few Classic UI dialogs are available for a few select capabilities, such as Link Checker, Version Purge, and some Cloud Service configurations. Upcoming product updates may further remove Classic UI availability.||Standard UI||Removed|
|Dynamic Media||Previous integrations with Dynamic Media Classic and Dynamic Media Hybrid mode are not available in Experience Manager as a Cloud Service.||Use Dynamic Media provided with Experience Manager as a Cloud Service.||Removed|
|Sites||Portal Director and Portlet Component||These capabilities were deprecated in Experience Manager 6.4 and have now been removed from Experience Manager.||Removed|
|Sites||Design Importer||This capability has been removed as immutable sections of the Experience Manager repository are not accessible at runtime.||Removed|
|Assets||Assets sharing with Marketing Cloud Assets Core Service and Creative Cloud services is not available.||For integration with Adobe Creative Cloud, use Adobe Asset Link.||Removed|
|Foundation||Support for Apache Sling datasources (OSGi bundle org.apache.sling.datasource)||N/A||Removed|
|Foundation||Suppport for JST scripting templates (OSGi bundle org.apache.sling.scripting.jst)||N/A||Removed|
|Foundation||Support for the Apache Felix Http Whiteboard||OSGi Http Whiteboard||March 2022|
See this page for any deprecated or removed Java APIs, which are occasionally introduced.
See this article for any restrictions around configuration of OSGI properties, some of which may be introduced over time.