Adobe Experience Manager 6.5 Latest Service Pack Release Notes aem-service-pack-release-notes

After configuring a connection between remote DAM and Sites deployments, the assets on remote DAM are made available on the Sites deployment. You can now perform the update, delete, rename, and move operations on the remote DAM assets or folders. The updates, with some delay, are available automatically on the Sites deployment (NPR-37816).

Push-rollouts of a live copy source to multiple live copies is now possible by default, without requiring a blueprint configuration (CQ-4259951).

The status of in-progress async operations is now shown in the user interface to help prevent users from accidentally triggering multiple async operations on the same path (NPR-37611).

Support for IMS-based authentication is provided for Analytics 2.0 APIs (CQ-4285474, NPR-37803, NPR-37701, NPR-37702, NPR-37703).

API support for JSON offer type experience fragment (NPR-37796).

Offer request is now provided for Delete offer (Experience Fragment API) in IMS (NPR-37668).

The built-in repository (Apache Jackrabbit Oak) still remains at 1.22.9.

When adding an asset or folder (containing single quote in the name) in Connected Assets, the reference path fails and results as an exception (NPR-37712).

When adding watermark to an asset, the watermark is always displayed in black color irrespective of the color defined by the user (NPR-37720).

When using Connected Assets, a non-admin user is able to search for an asset even when the non-admin users are restricted to access the DAM repository (NPR-37644).

When updating asset metadata using bulk edit, the changes applied to the dropdown fields are not saved and reset to the default values (NPR-37345).

Deleting a folder in taking too long which impacts the overall performance (NPR-37107).

When applying rules in metadata schema, the user is not able to view the complete value for the dropdown Field Value and Field Choices if the value is larger than the text box (CQ-4338074).

After upgrading to version 6.5.10.0, the asset properties page reflects an unnecessary HTML rendering message (CQ-4336994).

Sorting the assets in List View does not work effectively (CQ-4335298).

When sharing assets using share link, the assets are downloaded in separate folders (CQ-4335000).

When verifying the Experience Manager Inbox settings, the Share and Out of office tabs reflect untranslated content (CQ-4334858).

The following fixes are related to cascading metadata in asset properties.

• A mandatory dropdown reflects multiple error messages for each selection in the multivalue field (NPR-37859).
• Only the last selection of the parent field is saved for the dependent uneditable field (NPR-37858).
• The dependent dropdown (multivalue field) reflects the default value intermittently for the selected parent dropdown (NPR-37791).

When a text component in an adaptive form contains a table, pasting content into the component results in erasing the table in the editor (NPR-38078).

A form displays a toolbar only when you open a saved form (NPR-38060).

The undo operation does not work correctly for the rule editor (NPR-37973).

getAemFormContainer returns a null pointer after installing AEM Forms 6.5.10.0 (NPR-37881).

Accessibility - The screen reader announces the long description of a text box as soon as the tab focus shifts to the field instead of announcing only when you click the field (NPR-37855).

When you enable the Allow Rich Text property for a text box, there are issues with the maximum allowed character length (NPR-37825).

CSS issues when you copy any component in an adaptive form (NPR-37812).

While generating the adaptive forms translation the generated XLIFF file does not contain the same sequence of texts as in the Adaptive Form. In some cases it is needed to see the context of the texts. This is not possible if the sequence in XLIFF is alphabetic. (NPR-37435).

When an adaptive form is translated, the HTML tags are part of the translation. If a user makes a mistake and the tags are not valid, the whole text is not shown in the document of record. (NPR-37499)

Assembler does not embed fonts, as expected (NPR-38056).

Unable to convert PDF to PDFA using workbench (NPR-37879).

Issues with office documents while using the PDF Generator service after upgrading from AEM 6.5.7.0 Forms to AEM 6.5.10.0 Forms (NPR-37758).

Multithreaded PDF Generator service deadlocks after a random amount of time for AEM 6.5.7.0 Forms (NPR-38053).

In the AEM Workbench version 6.5.0.20210518.1.338459, when you use an email startpoint and edit the username and password, the configurations are not saved (NPR-37967, CQ-4336081).

Saving logs result in high CPU utilization that requires a server restart (NPR-37868).

Gemfire.log does not get created in the temp\adobejb_server1\Caching folder after installing AEM Forms-6.5.0-0038 (CQ-4340237).

The following error displays after executing the ConfigurationManager.sh command (CQ-4338323):

  [root@localhost bin]# ./ConfigurationManager.sh
  bash: ./ConfigurationManagerCLI.sh: /bin/sh^M: bad interpreter: No such file or directory

AEM 6.5 Forms on RHEL8 does not support JBOSS EAP 7.3 and MySQL8 (CQ-4331770).

Issues while storing UTF-8 special characters as part of a workflow on AEM 6.5.10.0 Forms publish instance (NPR-37673).

Issue while creating variable of ArrayList type and JSON subtype (NPR-37600).

Issues with XPath/Dot Notation browser with Set Variable step in Workflow in AEM 6.5.9.0 Forms and AEM 6.5.10.0 Forms (CQ-4336582).

When you install AEM 6.5 with Service Pack 12, and try to download the status ZIP file, Experience Manager downloads a corrupt file. Download and install AEM Sites SEO Index Package on your AEM instance before downloading the ZIP file to resolve the issue.

If you are using Content Fragments and GraphQL then it is recommended that you install the following packages on top of 6.5.12.0:

• AEM 6.5.12 Sites HotFix-NPR-38144 (this replaces SP12, but can be installed on top of SP12)

• AEM Content Fragment with GraphQL Index Package 1.0.3

When trying to move/delete/publish either Content Fragments or Sites/Pages, there is an issue when Content Fragment references are fetched, as the background query fails; that is, the functionality does not work.
To ensure correct operation, you need to add the following properties to the index definition node /oak:index/damAssetLucene (no re-indexing is required) :

"tags": [
    "visualSimilaritySearch"
  ]
"refresh": true

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

If you upgrade your Experience Manager instance from 6.5.0 - 6.5.4 to the latest service pack on Java 11, you see RRD4JReporter exceptions in the error.log file. To stop the exceptions, restart your instance of Experience Manager.

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:

• "When the Adobe Target integration is configured in Experience Manager using the Target Standard API (IMS authentication), then exporting Experience Fragments to Target results in wrong offer types getting created. Instead of type “Experience Fragment”/source “Adobe Experience Manager,” Target creates several offers with type “HTML”/source “Adobe Target Classic.”
• com.adobe.granite.maintenance.impl.TaskScheduler: No maintenance windows found at granite/operations/maintenance.
• Adaptive Form server-side validation fails when aggregate functions such as SUM, MAX, and MIN are used (CQ-4274424).
• com.adobe.granite.maintenance.impl.TaskScheduler - No maintenance windows found at granite/operations/maintenance.
• Hotspot in a Dynamic Media interactive image is not visible when previewing the asset through Shoppable Banner viewer.
• 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.