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, capabiiities 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.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.
|
At the point of writting, it's not planned to provide a replacement. |
| Portal Integration | Portal Director, JSR Portlet to load AEM content in Portal Server /libs/portal/director (cq-portlet-webapp.war) |
At the point of writting, it's not planned to provide a replacement. |
| Forms | Support for Adobe Central Migration Bridge service has been deprecated as Adobe Central product is no longer supported. |
This section lists features and capabilities that have been removed from AEM 6.4. Prior releases had these capabilites marked as depreacted.
| Area | Feature | Replacement |
| Components | 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 (/libs/cq/taskmanagement/content/taskmanager.html) |
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 (/libs/cq/workflow/content/notifications.html) |
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 default AEM Captcha service in adaptive forms has been removed. | Use ReCaptcha by Google instead. |
| Forms | Support for images inside document fragments has been removed. | Interactive communications provides the capability to use images in print and web channels directly. |
| Communities | Support for Allow Captcha has been removed. | Use the ReCaptcha by Google. |
Twitter™ 및 Facebook 게시물은 Creative Commons 약관을 적용받지 않습니다.