|Products||Adobe Experience Manager 6.5|
|Type||Service Pack Release|
|Date||August 26, 2021|
|Download URL||Software Distribution|
Adobe Experience Manager 220.127.116.11 includes new features, key customer-requested enhancements, and performance, stability, and security improvements, that are released since the availability of 6.5 release in April 2019. The service pack is installed on Adobe Experience Manager 6.5.
The key features and enhancements introduced in Adobe Experience Manager 18.104.22.168 are:
Enhanced Content Fragment Models and Editor: You can now create complex and custom models for structured content using nested Content Fragment models. Content structures are modularized into basic elements that are modeled as sub-fragments. Higher-level fragments reference these sub-fragments. More data type enhancements such as advanced validation rules further enhance the flexibility of content modeling with Content Fragments. The Experience Manager Content Fragment editor supports nested fragment structures in a common editor session, with enhancements such as structure tree view and tabbed breadcrumb navigation through fragment hierarchies.
GraphQL API for Content Fragments: The new GraphQL API is the standard method to deliver structured content in JSON format. GraphQL queries let clients request only the relevant content items to render an experience. Such a selection eliminates content over-delivery (possibility with HTTP REST APIs) that requires content parsing on the client side. GraphQL schemas are derived from Content Fragment models, and API responses are made in JSON format. In Experience Manager as a Cloud Service, GraphQL queries persist and process cache friendly GET requests. It is not yet possible in Experience Manager 22.214.171.124.
Hierarchy management and future preview: Users now have an interface to access the content structures of their Experience Manager launches, including the ability to add and remove pages in a launch. This feature enhances the flexibility of Experience Manager launches to author content versions targeted for future publishing. Time-warp feature lets users preview launches as future content states.
Connected Assets: Experience Manager extends the Connected Assets functionality to the use of Dynamic Media images in the applicable core components. See use Connected Assets.
Link share options to download assets or renditions: When sharing assets and Collections as link, users can choose whether to allow the download of original assets, or their renditions, or both using the shared link. Also, the users who download the assets shared with them through link get the option to download only the original assets, only the renditions, or both.
Limit sub-assets generated: Administrators can limit the number of sub-assets that Experience Manager generates for compound assets such as PDF, PowerPoint, InDesign, and Keynote files. See Manage compound assets.
Camera Raw support: A new Camera Raw package is available that supports Adobe Camera Raw v10.4. See process images using Camera Raw.
The built-in repository (Apache Jackrabbit Oak) is updated to 1.22.8.
User experience enhancements:
Experience Manager directly displays a list of all the content models under a folder without content authors having to navigate through the file structure. The feature now requires fewer clicks and improves authoring efficiency.
Pathfield in Sites editor allows authors to drag assets from Content Finder.
Added support for
GuideBridge#getGuidePath API in AEM Forms.
You can now use Automated Forms Conversion service to convert PDF Forms in French, German, Spanish, Italian, and Portuguese languages to adaptive forms.
Error messages in Properties browser: Added error messages for each property in the Adaptive Forms Properties browser. These messages help understand allowed values for a field.
Support to use the literal option to set value for a JSON type variable: You can use literal option to set value for a JSON type variable in the set variable step of an AEM Workflow. The literal option allows you to specify a JSON in the form of a string.
Platform Updates: Adobe Experience Manager Forms on JEE has added support for the following platforms:
For a list of all features and enhancements introduced in Experience Manager 126.96.36.199, see what is new in Adobe Experience Manager 6.5 Service Pack 10.
The following is the list of fixes provided in Experience Manager 188.8.131.52 release.
The focus shift to another field when typing in the Default Value field under the Properties tab of the Content Fragment Editor (NPR-36992).
While filtering Content Fragment models under a specified path, Experience Manager search returns all nodes with
cq:Template instead of returning paths and nodes only for the Content Fragment model (SITES-1453).
Content Fragments return
null as the status of folders (SITES-1157).
Experience Manager does not let users disable and enable Content Fragment Models (SITES-1088).
When a user moves, rename, or deletes Content Fragments or media assets, the referenced Content Fragments are not automatically updated (SITES-196).
When page properties are viewed quickly, Page Properties for a different page are opened (NPR-37025).
The Content Fragment allows the Content Fragment to reference itself. The picker does not support the operation (NPR-36993).
After upgrading to service pack 9, some users cannot move folders in Experience Manager and see errors in the logs (SITES-1481).
While adjusting the width of the component in the layout container on edit mode, a flicker is observed (NPR-36961).
On promoting a launch, the changes in the promoted launch are double rolled out to the other launches. If a user promotes the double rolled out launch, the doubled contents is reflected on the source page (NPR-36893).
Experience Manager adds a gray border to some PNG images with transparency if you add the images to a page using the Image Core Component or if you resize using the Foundation Image component (NPR-36879).
Experience Manager Sites Admin UI with a high number of templates results in slow navigation (NPR-36870).
Upgrade to service pack 9 prevents authoring of a few components. This issue does not allow Sites users to create new pages (NPR-36857).
ContextHubImpl method creates a
ResourceResolver that is not closed. It leads to warning messages about long-running
ResourceResolver and the service returns unexpected results at times (NPR-36853).
On synchronizing a single live copy from blueprint page properties, all other live copies are also synchronized (NPR-36829, NPR-36522).
When only XLS MIME type is used, the file upload function does not work as expected (NPR-36785).
New tags with pascal case and all upper case words are not displayed in the tag field within Content Fragments (NPR-36742).
The Single Text Element option when adding a Content Fragment causes text to be missing and creates odd formatting related to lists and nested lists (NPR-36565).
When an author annotates any component on a page, deletes the component, and performs an undo on the delete operation, an error is encountered when attempting to view the Timeline data for the page in the sites console (NPR-36528).
Page properties Bulk Editor’s Save & Close option saves changes but does not close the editor (NPR-36527).
When a user attempts to drag and drop a new Text component to a page, the component immediately disappears (NPR-36442).
When a user types in an on-demand tag that includes space (the tag that does not exist on the system) and presses enter, the tag appears under the field. However, when the Content Fragment is saved and reopened, the on-demand tag does not appear (NPR-36441).
The template cannot be deleted when the instance is accessed via the Dispatcher (NPR-36385).
When a page is moved, a manual refresh of the browser is required to render the changes (NPR-36381).
When selecting a component, you can cut or copy it with Ctrl+X or Ctrl+C (and Command+X or Command+C on Mac). When you click another component, you can paste with the toolbar, but not the keyboard (Ctrl+V or Command+V) (NPR-36379).
When a user tries cut components using the scissor icon to move them somewhere else, a console error happens. Moreover, when pasting only one component gets moved (NPR-36378).
Experience Manager has a query without index on WCM or notifications, it slows down performance (NPR-36303).
When an author restores the inheritance on the deleted inherited component, the available option is to synchronize all page content. The content authors are required to sync the complete page even if the inheritance is restored only on one component. A complete sync can result in unwanted content getting synchronized (NPR-34456, CQ-4310183).
Live Usage of a component on Author instance does not display all the occurrences. Some components are used in more than 1000 pages but the report only displays about 40 pages (CQ-4323724).
When there is a site structure that has lot of subpages, loading of the subpages in column view takes more time in Experience Manager 6.5.8 as compared to Experience Manager 184.108.40.206 (CQ-4322766).
Uncheck ‘All’ does not work on the ‘Rollout Page’ option (NPR-37070).
When opening an existing v3 component version of a page, the page Properties dialog does not open and a
NullPointerException is logged (SITES-1830).
The following issues are fixed in Assets:
The value of the property
jcr:title is not updated on the Publish instance after a folder is moved. Renaming and republishing a folder within author does not update the
jcr:title property value of the same in the Publish instance (NPR-36369).
If two or more assets are selected and one or more metadata fields are edited, the save operation fails with error code 500 in Safari browser (NPR-36413).
Bulk metadata import fails because of incorrect date format (NPR-36428).
When a selection is made in the Properties page to update metadata, the interface is slow to respond when there are many options provided by the schema (NPR-36430).
Search Filter using the Expiry Status predicate is not working (NPR-36436).
The popup menu for various fields in Folder Metadata properties does not display the last selected values (NPR-36937, CQ-4314429).
When searching for files and folders, if user applies a filter and selects Files & Folders, only the files are displayed but not the folder (CQ-4319543, NPR-36627).
The toolbar options are different when the same Collection is selected from within a folder and when it is selected from a search result (NPR-36620).
The Quick Publish option is not available on the search results page (NPR-36904, CQ-4317748).
When users create live copy of an asset without specifying its extension, then after download the live copy file is not usable (NPR-36903, CQ-4326305).
When a user is added as an owner of a child folder, then the user gets owner permission of its parent folder too and hence of the other children folders of the parent. Also, the user is not removed as owner of parent folder on attempting to remove it. (NPR-36801, CQ-4323737).
Experience Manager generates an out-of-memory exception when you attempt to create sub-assets for compound assets, such as a PowerPoint presentation (NPR-36668).
When users move an asset that is already used in a published sites page, then the sites page is published again even if the option to publish is not selected (NPR-36636, CQ-4323500).
When using the Apache Tika MIME type detection feature, the assets uploaded using the
AssetManager.createAsset method leave a temporary file named
apache-tika-*.tmp file in the temporary directory. This temporary file uses all the available free disk space (NPR-36545).
All DRM-protected assets are downloaded and user selection to download specific asset is not followed (CQ-4327422).
Cannot drag assets to
pathfield on the user interface (NPR-36849).
When you select an asset in the Column view, the asset details panel disappears (NPR-36667).
The following accessibility enhancements are available in Dynamic Media Viewers.
Screen readers now narrate the placeholder text to search and add Email address as a required field on share assets as a link dialog, and also announces the Please fill out this field tooltip (CQ-4327761).
Screen readers now correctly narrate the names and purposes of various fields in the Image Preset Editor on accessing the user interface fields using keyboard (CQ-4325677).
Keyboard focus now appropriately moves to search tab of Viewer Presets dialog box from asset picker of Rich Media Type option (CQ-4324736).
When navigating in forms mode using keyboard keys, the screen readers narrate the labels corresponding to increment and decrement options on Create tab of Image Presets (CQ-4323900).
Screen readers now announce the Search and Add Email Address option on share assets as a link dialog box (CQ-4323352).
Keyboard focus is retained on the toolbar when navigating assets using keyboard keys (CQ-4322037).
Screen readers now narrate the newly added Edit field information after selecting the Add Crop option within the Responsive Image Crop on Edit Image Processing Profile page (CQ-4290734).
On Edit Image Preset and Create Interactive Video pages, screen readers now appropriately announce the page heading when navigating the pages using heading keyboard shortcut keys (CQ-4290730)(CQ-4290701).
Screen readers can now recognize the various regions of the screen (such as right panel region, left panel, action toolbar, viewer toolbar landmark, and zoomable image landmark) using landmark and region shortcut keys when navigating the following pages.
Viewer Preset Editor (CQ-4290729)
Image Set Editor (CQ-4290710)
Create Interactive Video (CQ-4290702).
Screen readers now announce the name for the share option in the video frame, when navigating using down arrow key (CQ-4290728).
Screen readers now narrate the names for various options in Sprite and Background tabs in Appearance tab in Viewer Preset Editor (CQ-4290727).
Mandatory fields, like the field to edit Width, in the Basic tab of Edit Video Encoding page now have an asterisk symbol (*) (CQ-4290725).
Screen readers now announce the label for the options on Image Profiles page (CQ-4290723).
Windows users can now navigate out of the expanded CSS editor on Viewer Preset Editor when the focus is on the CSS Editor (CQ-4290720).
On Basic tab of Edit Image Preset when navigating in Form mode, the screen readers now narrate the labels for various edit fields and options (CQ-4290717).
Screen readers now narrate the role and state (selected or not selected) for user interface options in the left navigation on assets’ details page (CQ-4290709).
Screen readers now correctly narrate the state (selected or not selected) and link for the image toggles in the Content tab of Create Interactive Video page (CQ-4290707).
Screen readers now correctly narrate the name, role, and state of various segments in the video timeline scale when navigating using down arrow key on Create Interactive Video page (CQ-4290706).
Screen readers now narrate the name, role, and default state (selected or not selected) and property when navigating the options in Create Interactive Video page (CQ-4290704).
Screen readers now narrate the name, role, and default state (selected or not selected) of options in All Assets and All Collections options when navigating the Publish page (CQ-4290705).
When you upload an unsupported video format (other than MP4) on Create Interactive Video page, Experience Manager displays and announces error messages (CQ-4290700).
The contrast of the numbers (time in seconds) in the timeline scale on Create Interactive Video page now meet minimum required luminosity ratio, so that users with limited perception of color can easily read (CQ-4290699).
Screen readers now announce the label for the Product Name field when navigating the Create Interactive Video page (CQ-4290697).
The following bug fixes are available in Dynamic Media.
dynamicmedia_scene7runmode is enabled and sync is disabled (CQ-4327791).
The following enhancements are delivered in this service pack:
Clientlibsusing ECMAScript 6 features without complying with strict mode. Specifically,
emitUseStrictflag is added to the
The following bug fixes are part of this service pack:
Resourceresolver mapmethod returns incorrect result for alias pages (NPR-36767).
Community site pages are opening in
LoggedIn state for anonymous guest users (NPR-36908).
When there is more than one page in the Community > Ideas > Comments page, the page navigation does not work (NPR-36541).
AEM 220.127.116.11 Forms includes the following bug fixes:
If the validations performed on the field values in an adaptive form are successful, AEM Forms fails to invoke the Form Data Model (CQ-4325491).
When you add a language dictionary to a translation project and then open the project, AEM Forms displays an error message (CQ-4324933):
Uncaught TypeError: Cannot read property 'PROJECT_LISTING_PATH' of undefined at openButtonClickHandler (clientlibs.js:245) at HTMLButtonElement.onclick (clientlibs.js:258)
Performance issues after installing AEM Forms Service Pack 7 (CQ-4326828).
Delay in the display of characters in the Data tab as well as in the HTML letter preview (NPR-37020).
When you are editing a text document fragment, the new words display as HTML tags after saving the fragment (NPR-36837).
Unable to view the letters that are saved as drafts (NPR-36816).
When you edit a text document fragment and then preview the letter, AEM Forms displays the expression language in the HTML letter preview (CQ-4322331).
Issues while rendering data with a self-service letter template (NPR-37161).
A tab character duplicates between two words each time you print preview an Interactive Communication after editing a text document fragment (NPR-37021).
AEM Forms displays an error when you save a text document fragment that exceeds the maximum size limit (NPR-36874).
When you add an image to an Interactive Communication, an additional empty block displays after the image (NPR-36659).
When you select all text in an editor, you cannot change the font text to Arial (NPR-36646).
When you create a URL in an editor and preview the changes, a black background displays instead of the URL text (NPR-36640).
When you copy and paste text to an editor, there are issues while changing the font to Arial for bullets available in the document (NPR-36628).
Indentation issues for bullets in the text editor (NPR-36513).
When you convert XDP files to PDF files and then assemble the resultant PDF, the PDF generations fails and displays the following error message:
Caused by: com.adobe.fd.assembler.client.AssemblerException$ClientException: Document is in a disposed state!
When you set the value for the
mfAllowAttachments property as
True in the CRX DE repository, the
dataXml gets corrupted on submitting the HTML5 form (NPR-37035).
When you render an XDP as HTML using
dataXml, AEM Forms displays a
Page Unresponsive error (NPR-36631).
For information on security updates, see Experience Manager security bulletins page.
Setup requirements and more information
Adobe does not recommend removing or uninstalling the Adobe Experience Manager 18.104.22.168 package.
To install the service pack on an Adobe Experience Manager 6.5 instance, follow these steps:
Restart the instance before installation if the instance is in update mode (when the instance was updated from an earlier version). Adobe recommends a restart if the current uptime for an instance is high.
Before installing, take a snapshot or a fresh backup of your Experience Manager instance.
Download the service pack from Software Distribution.
Open Package Manager and click Upload Package to upload the package. To know more, see Package Manager.
Select the package and click Install.
To update the S3 connector, stop the instance after installation of the Service Pack, replace the existing connector with a new binary file provided in the install folder, and restart the instance. See Amazon S3 Data Store.
Dialog on Package Manager UI sometimes exits during the installation of the service pack. Adobe recommends that you wait for error logs to stabilize before accessing the deployment. Wait for the specific logs related to the uninstall of the updater bundle before being assured that the installations is successful. Typically, this issue occurs in Safari browser but can intermittently occur on any browser.
There are two ways to automatically install Experience Manager 22.214.171.124 on a working instance:
A. Place the package into
../crx-quickstart/install folder when the server is available online. The package is automatically installed.
B. Use the HTTP API from Package Manager. Use
cmd=install&recursive=true so that the nested packages are installed.
Adobe Experience Manager 126.96.36.199 does not support Bootstrap installation.
Validate the installation
The product information page (
/system/console/productinfo) displays the updated version string
Adobe Experience Manager (188.8.131.52) under Installed Products.
All OSGi bundles are either ACTIVE or FRAGMENT in the OSGi Console (Use Web Console:
The OSGi bundle
org.apache.jackrabbit.oak-core is version 1.22.3 or later (Use Web Console:
To know the platforms certified to work with this release, see the technical requirements.
Skip if you are not using Experience Manager Forms. Fixes in Experience Manager Forms are delivered through a separate add-on package a week after the scheduled Experience Manager Service Pack release.
Experience Manager 184.108.40.206 includes a new version of AEM Forms Compatibility Package. If you are using an older version of AEM Forms Compatibility Package and updating to Experience Manager 220.127.116.11, install the latest version of the package post installation of Forms Add-On Package.
Skip if you are not using AEM Forms on JEE. Fixes in Adobe Experience Manager Forms on JEE are delivered through a separate installer.
For information about installing the cumulative installer for Experience Manager Forms on JEE and post-deployment configuration, see the release notes.
After installing the cumulative installer for Experience Manager Forms on JEE, install the latest Forms add-on package, delete the Forms add-on package from the
crx-repository\install folder, and restart the server.
The UberJar for Experience Manager 18.104.22.168 is available in the Maven Central repository.
To use UberJar in a Maven project, see how to use UberJar and include the following dependency in your project POM:
<dependency> <groupId>com.adobe.aem</groupId> <artifactId>uber-jar</artifactId> <version>6.5.10</version> <scope>provided</scope> </dependency>
UberJar and the other related artifacts are available on Maven Central Repository instead of Adobe Public Maven repository (
repo.adobe.com). The main UberJar file is renamed to
uber-jar-<version>.jar. So, there is no
apis as the value, for the
Below is a list of features and capabilities that are marked as deprecated with Experience Manager 22.214.171.124. Features are marked deprecated initially and later removed in a future release. An alternate option is provided.
Review if you use a feature or a capability in a deployment. Also, plan to change the implementation to use an alternate option.
|Integrations||The AEM Cloud Services Opt-In screen is deprecated since the Experience Manager and Adobe Target integration is updated in Experience Manager 6.5. The integration supports the Adobe Target Standard API. The API uses authentication via Adobe IMS and Adobe I/O and supports the growing role of Adobe Launch to instrument Experience Manager pages for analytics and personalization, the opt-in wizard is functionally irrelevant.||Configure system connections, Adobe IMS authentication, and Adobe I/O integrations via the respective Experience Manager cloud services.|
|Connectors||The Adobe JCR Connector for Microsoft® SharePoint 2010 and Microsoft® SharePoint 2013 is deprecated for Experience Manager 6.5.||N/A|
As Microsoft Windows Server 2019 does not support MySQL 5.7 and JBoss EAP 7.1, Microsoft Windows Server 2019 does not support turnkey installations for AEM Forms 126.96.36.199.
If you are upgrading your Experience Manager instance from 6.5 to 188.8.131.52 version, you can view
RRD4JReporter exceptions in the
error.log file. To resolve the issue, restart the instance.
If you install Experience Manager 6.5 Service Pack 10 or a previous service pack on Experience Manager 6.5, the runtime copy of your assets custom workflow model (created in
/var/workflow/models/dam) is deleted.
To retrieve your runtime copy, Adobe recommends to synchronize the design-time copy of the custom workflow model with its runtime copy using the HTTP API:
Users can rename a folder in a hierarchy in Assets and publish a nested folder to Brand Portal. However, the title of the folder is not updated in Brand Portal until the root folder is republished.
When a user selects to configure a field for the first time in an adaptive form, the option to save a configuration does not display in Properties Browser. Selecting to configure some other field of the adaptive form in the same editor resolves the issue.
The following errors and warning messages may display during installation of Experience Manager 6.5.x.x:
com.adobe.granite.maintenance.impl.TaskScheduler: No maintenance windows found at granite/operations/maintenance.
com.adobe.granite.maintenance.impl.TaskScheduler- No maintenance windows found at granite/operations/maintenance.
com.adobe.cq.social.cq-social-jcr-provider bundle com.adobe.cq.social.cq-social-jcr-provider:1.3.5 (395)[com.adobe.cq.social.provider.jcr.impl.SpiSocialJcrResourceProviderImpl(2302)]: Timeout waiting for reg change to complete unregistered.
The following text documents list the OSGi bundles and Content Packages included in Experience Manager 184.108.40.206:
These websites are only available to customers. If you are a customer and need access, contact your Adobe account manager.