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

Annotation swatch selector button was missing an accessible name. That is, using a screen reader, there is no human-understandable name for the button to select after entering a new hex value. (SITES-11992)

The following elements in the left rail menu appear like a list but are not marked up as such in the screen reader:

• Site
• Live copy
• Launch
• Language Copy
• Folder
• CSV Report (SITES-2874)

The AEM Core Web Content Management requires an accessibility label for hyperlinks in the Rich Text Editor. When a hyperlink is used in the text component, the anchor tag should include the aria-label attribute to ensure that screen readers can read and convey the link text accurately for accessibility purposes. (SITES-11511)

In AEM, interactive elements in the table header in List View do not have the required “button” role. As such, the NVDA screen reader does not announce the expected button roles for the following table headers: Title, Name, Modified, Published, Preview, Template, Operation, Workflow. Each interactive element in the table header should be assigned a “button” role to ensure compatibility with assistive technologies like NVDA. (SITES-10962)

In some instances of AEM, the version preview and comparison functionalities were not working as expected across several pages. Specifically:

• Preview Issue: When attempting to preview a page version, an error appears initially. After retrying, the preview results in a blank page.
• Version Comparison Issue: The “Compare to Current” feature only displayed the current version, without highlighting any differences between versions. (SITES-23988)

An unexpected <br> tag appears in the Rich Text Editor (RTE) field when using the defaultPasteMode set to plaintext during a copy and paste action. This issue results in different markup for the same content, resulting in the same text content being translated twice in a customer’s translation memory. (SITES-23606)

In AEM 6.5.20.0, a functionality issue was encountered with the Manage Publication feature. When selecting a node and scheduling it for future publication, an error message—“Failed to retrieve child resources for selected items”—could appear when trying to include child nodes. This issue was blocking the use of the Include Children option, preventing complete publication of the intended content hierarchy. (SITES-23000)

A template’s “Published” timestamp was not updating in the author environment, even though the template was successfully replicated to the publish instances. The expected behavior was for the timestamp on the author instance to reflect the latest publication, but this update was not occurring as intended. (SITES-21585)

There was a discrepancy in the count of Incoming Links in the AEM author environment. The left side rail showed fewer links compared to the Classic UI. Also, some Incoming Links that were legitimate, do not work. (SITES-24837)

Extremely long loading times were being reported when viewing page versions in the Timeline view of AEM. It was taking up to 19 minutes to display versions. This issue was ongoing since the upgrade from AEM 6.4.8 to 6.5.18, significantly disrupting workflow efficiency. (SITES-22468 & SITES-22467)

Experience Fragments do not sort by title as expected when the Title column header is clicked in the List View. A quick flicker of the screen is observed, but it does not sort. (SITES-23706)

In AEM 6.5.17, an issue was encountered when converting a page component into an Experience Fragment using the out-of-the-box feature. After conversion, the Experience Fragment appeared empty during editing, despite displaying correctly on the page where it was used. The issue stemmed from incorrect node creation: the component node was placed outside the root / container node, violating the template’s structure. You needed to move the component node manually into the correct root / container node to restore the fragment’s editability. (SITES-22974)

After migrating from AEM 6.5.11 to 6.5.20, Cloud configurations on Experience Fragments were not saving correctly. Although the configurations appeared to save in crx/de, they would not display upon reopening the configurations console, indicating an issue with persistence. (SITES-22287)

Related to Oak
From Service Pack 13 and above, the following error log has begun to appear which affects the persistence cache:

org.h2.mvstore.MVStoreException: The write format 1 is smaller than the supported format 2 [2.0.202/5]
at org.h2.mvstore.DataUtils.newMVStoreException(DataUtils.java:1004)
    at org.h2.mvstore.MVStore.getUnsupportedWriteFormatException(MVStore.java:1059)
    at org.h2.mvstore.MVStore.readStoreHeader(MVStore.java:878)
    at org.h2.mvstore.MVStore.<init>(MVStore.java:455)
    at org.h2.mvstore.MVStore$Builder.open(MVStore.java:4052)
    at org.h2.mvstore.db.Store.<init>(Store.java:129)

Or

org.h2.mvstore.MVStoreException: The write format 1 is smaller than the supported format 2 [2.1.214/5].

To resolve this exception, do the following:

1. Delete the following two folders from crx-quickstart/repository/

   • cache
   • diff-cache

2. Install the Service Pack, or restart Experience Manager as a Cloud Service.
   New folders of cache and diff-cache are automatically created and you no longer experience an exception related to mvstore in the error.log.

Update your GraphQL queries that may have used a custom API name for your content model to use the default name of the content model instead.

A GraphQL query may use the damAssetLucene index instead of the fragments index. This action might result in GraphQL queries that fail, or take a long time to run.

To correct the problem, damAssetLucene has to be configured to include the following two properties under /indexRules/dam:Asset/properties:

• contentFragment

  • jcr:primaryType="nt:unstructured"
  • name="jcr:content/contentFragment"
  • propertyIndex="{Boolean}true"
  • type="Boolean"

• model

  • jcr:primaryType="nt:unstructured"
  • name="jcr:content/data/cq:model"
  • ordered="{Boolean}true"
  • propertyIndex="{Boolean}true"
  • type="String"

After the index definition is changed, a reindexing is required (reindex = true).

After these steps, the GraphQL queries should perform faster.

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

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

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.

The following errors and warning messages may be displayed 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.
• The hotspot in a Dynamic Media interactive image is not visible when previewing the asset through the 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 register change to complete unregistered.

Starting with AEM 6.5.15, the Rhino JavaScript Engine provided by the org.apache.servicemix.bundles.rhino bundle has a new hoisting behavior. Scripts that use the strict mode (use strict;) have to declare their correct variables. Otherwise, they do not get run, and end up throwing a runtime error.

Installing tagging related out-of-the-box content by way of an official update package resets the languages property of the /content/cq:tags node to default. This action is true for Service Packs, Security Service Packs, Extended Feature Packs, Cumulative Feature Packs, patches, and so on. Therefore, it is necessary to add it from the properties before installation.

After installing AEM Forms JEE Service Pack 21 (6.5.21.0), if you find duplicate entries of Geode jars (geode-*-1.15.1.jar and geode-*-1.15.1.2.jar) under the <AEM_Forms_Installation>/lib/caching/lib folder (FORMS-14926), perform the following steps to resolve the issue:

1. Stop the locators, if they are running.
2. Stop the AEM Server.
3. Go to the <AEM_Forms_Installation>/lib/caching/lib.
4. Remove all the Geode patch files except geode-*-1.15.1.2.jar. Confirm that only the Geode jars with version 1.15.1.2 are present.
5. Open the command prompt in administrator mode.
6. Install the Geode patch using the geode-*-1.15.1.2.jar file.

If a user tries to preview a draft letter with saved XML data, it gets stuck in Loading state for some specific letters. To download and install the hotfix, refer to the Adobe Experience Manager Forms Hotfixes article. (FORMS-14521)

After upgrading to AEM Forms Service Pack 6.5.21.0, the PaperCapture service fails to perform OCR (Optical Character Recognition) operations on PDFs. The service does not generate output in the form of a PDF or a log file. To download and install the hotfix, refer to the Adobe Experience Manager Forms Hotfixes article. (CQDOC-21680)

When users upgraded from AEM 6.5 Forms Service Pack 18 or 19 to Service Pack 20 or 21, they encountered a JSP compilation error. This error prevented them from opening or creating adaptive forms. It also caused issues with other AEM interfaces. Those interfaces included the page editor, AEM Forms UI, Workflow editor, and System Overview UI. (FORMS-15256)

If you face such an issue, perform the following steps to resolve it:

1. Navigate to the directory /libs/fd/aemforms/install/ in CRXDE.
2. Delete the bundle with the name com.adobe.granite.ui.commons-5.10.26.jar.
3. Restart your AEM Server.

After updating to AEM Forms Service Pack 20 (6.5.20.0) with the Forms Add-On, configurations relying on the legacy Adobe Analytics Cloud Service using credential-based authentication stop working. This issue prevented analytics rules from executing correctly. To download and install the hotfix, refer to the Adobe Experience Manager Forms Hotfixes article. (FORMS-15428)

When a user updates to AEM Forms Service Pack 20 (6.5.20.0) on the JEE server and generates PDFs using output services, the PDFs render with accessibility issues. To download and install the hotfix, refer to the Adobe Experience Manager Forms Hotfixes article. (LC-3922112)

When a user generates Tagged PDFs using the output service on JEE, it shows “Inappropriate structure warning.” To download and install the hotfix, refer to the Adobe Experience Manager Forms Hotfixes article. (LC-3922038)

When a form is submitted on AEM Forms JEE, the instances of a repeating XML element are removed from the data. To download and install the hotfix, refer to the Adobe Experience Manager Forms Hotfixes article. (LC-3922017)

When a user in a Linux® environment renders an adaptive form (on JEE) in HTML, it fails to render properly. To download and install the hotfix, refer to the Adobe Experience Manager Forms Hotfixes article. (LC-3921957)

When a user converts an XTG file to PostScript format using the Output Service on AEM Forms JEE, it fails with the error: AEM_OUT_001_003: Unexpected Exception: PAExecute Failure: XFA_RENDER_FAILURE. To download and install the hotfix, refer to the Adobe Experience Manager Forms Hotfixes article. (LC-3921720)

After upgrading to AEM Forms Service Pack 18 (6.5.18.0) on JEE server, when a user submits a form, it fails to render HTML5 or PDF Forms and XMLFM crashes. To download and install the hotfix, refer to the Adobe Experience Manager Forms Hotfixes article. (LC-3921718)

In the Print Preview of the Interactive Communications Agent UI, the currency symbol (such as the dollar sign $) is inconsistently displayed for all field values. It appears for values up to 999 but is missing for values of 1000 and above. (FORMS-16557)

Any modifications to nested layout fragments’ XDP in an Interactive Communication are not reflected in the IC editor. (FORMS-16575)

In the Print Preview of the Interactive Communications Agent UI, some calculated values are not displayed correctly. (FORMS-16603)

When the letter is viewed in Print Preview, the content is changed. That is, some spaces disappear, and certain letters are replaced with ‘x’ (FORMS-15681)