أنت تعرض محتوى المساعدة للإصدار:

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:

  1. Announcement of deprecation comes first. While deprecated, capabiiities are still available, but they will not be further enhanced. 
  2. 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

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.

Area Feature Replacement
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 expereince 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 Assset Link or AEM Desktop App. Please review AEM and Creative Cloud Integration Best Practices for more details.
Assets
  1. AssetDownloadServlet is disabled by default for the publish instances. For more details, see AEM security checklist.
  2. If a user does not have sufficient (read and write) permissions on /content/dam/collections, the user cannot create a Collection.
  1. Configuration described at AEM Security checklist.
  2. Honor the access control setup of user and ensure appropriate permissions.
Adobe Search & Promote

The integation 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
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)

Scrible Signature

/libs/fd/afaddon/components/esign
/cq:dialog/content/items/accordion/items/basic/items/signingService

Use Adobe Sign
Foundation

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.
Developers

Hobbes.js 

Adobe does not plan to make further enhancements to the hobbes.js UI testing framework.

Adobe recommends customers to 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 thier code to add it into thier project code base.
Developres

jQuery Animiation 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 thier code to add it into thier 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 thier code to add it into thier 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 thier code to add it into thier project code base.
Developers

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 capablity of the library to refactor thier code to no longer use it.
Developers Using YUI to compress/minify JavaScript client libraries. Adobe does not plan to further update the YUI library. Up until AEM 6.4, YUI was default to minify JavaScript with the option to switch to Google Closure Compiler (GCC). Starting AEM 6.5, GCC is default. Adobe recommends customers that upgrade to AEM 6.5 to switch to GCC for thier implementation
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)

 

Removed Features

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

Area  Feature Replacement
Integrations ExactTarget integration has been removed from the default distribution (Quickstart) and is now an extra package to install from PackageShare. Feature is still available.
Integrations 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.
Forms Support for Adobe Central Migration Bridge service has been removed as Adobe Central product is no longer supported. No replacement
Forms com.adobe.fd.df.fdinternal.model.ConfigurationInstance No replacement
Forms
com.adobe.fd.ccm.channels.print.fdinternal.api.service.PrintDataTransformer
No replacement
Developers Firebug Lite has been removed from the default distribution (Quickstart) Use the browser built-in developer consoles
Developers Remove customJavaScriptPath support in HTML Client Library Manager. No replacement
Assets The Assets Offloading feature has been removed in AEM 6.5 No replacement

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
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.

تم ترخيص هذا العمل بموجب الترخيص العام غير المعدل الخاص بالإسناد وعدم التجارة والمشاركة الإصدار 3.0 ‏من ‏‏Creative Commons‏‏  إن بنود Creative Commons لا تشمل منشورات Twitter™‎ وFacebook.

إشعارات قانونية   |   سياسة الخصوصية على الإنترنت