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

Accessible Hyperlinks with mixed text styling in Static PDFs: Hyperlinks containing mixed text styles in static PDFs are now tagged as a single accessible element. This enhancement simplifies the tag tree structure, improves screen reader navigation, and supports better accessibility compliance.

Updated Supported Platform Matrix

The latest version introduces updates to the supported platform matrix, ensuring compatibility with newer technologies.

• IBM® Content Manager Client 8.7

• MongoDB Enterprise 7.0

• MySQL 8.4

• Microsoft® SQL Server 2022

• Microsoft® SQL Server JDBC Driver 12.8

• Red Hat® Enterprise Linux® 9 (Kernel 4.x, 64-bit)

Hardened file attachment component: As a security measure, the component now prevents submission of files with modified extensions that attempt to bypass allowed file type checks. Such files are blocked during submission to ensure that only valid file types are accepted.

FORMS-20533, FORMS-20532: AEM Forms now includes an upgrade of Struts version from 2.5.33 to 6.x. The support was added via a Hotfix that you can download and install to add support for the latest version of Struts.

LC-3922769: Certain AEM Forms features now require OpenSSL 3 to function correctly. The system must have OpenSSL 3 installed, along with the libraries libcrypto.so.3 and libssl.so.3. Since security updates are only available in versions 3.0.14 and above, and SafeLogic support ends in February 2025, BSAFE has been removed and OpenSSL 3 is now used for security compliance. For platform compatibility and detailed requirements, see Supported Platforms for AEM Forms on JEE and Technical Requirements.

To verify OpenSSL 3 installation:

• RHEL/CentOS/Fedora-based systems: rpm -qa | grep openssl3
• Ubuntu/Debian-based systems: dpkg -l | grep openssl3
• Alternative verification: ldd /path/to/XMLForm | grep -E 'libcrypto.so.3|libssl.so.3' (if libraries are in LD_LIBRARY_PATH)

The following issues occur on AEM On-Premise (6.5.22.0) Navigation page after selecting Assets, navigating to Search Adobe Stock folder, and selecting a stock image:

• The selected stock image cannot be licensed and saved as clicking License & Save displays an empty dropdown.
• Selecting the Stock image or re-entering the stock page URL redirects to the AEM homepage, preventing access to the Adobe Stock image. (ASSETS-48687)

Issues while managing folders if the name of the folder includes a / in its name on the AEM On-Premise (6.5.22.0) Navigation page. (ASSETS-46740)

On AEM 6.5, the asset details page does not load from Collections view due to high memory usage. (ASSETS-46738)

Integration issues with InDesign as Day CQ DAM Mime Type OSGI Service incorrectly identifies InDesign files as x-adobe-indesign instead of x-indesign. (ASSETS-45953)

AEM 6.5.21 session leak traced to the out-of-the-box Scheduled publish to Brand Portal workflow step. (ASSETS-44104)

Out of Memory (OOM) errors display in AEM when processing and publishing images. This issue was due to deprecated methods in workflows, such as Dam Asset update and Dynamic Media: Reprocess assets. (ASSETS-43343)

After you make a minor change, such as updating the title, you reopen and resave the Connected Assets configuration on the local Sites instance. The remote instance then loses its connection to the local instance. As a result, it cannot establish communication with the local Sites instance. (ASSETS-44484)

In AEM 6.5.21, when an asset upload in list view is canceled and a second upload is performed, AEM displays a 0 of NaN assets uploaded error. (ASSETS-44124)

When a user exports the data for an XFA-based PDF using the exportDataAPI, the resulting XML shows discrepancies when compared with the XML data exported manually using Acrobat Reader. Values of some fields were missing in the output compared to the output generated from Acrobat Reader. (LC-3922791)

In AEM Forms 6.5.22.0, generating a tagged PDF with the Output Service in Workbench adds an unexpected label tag under the reference tag in a table of contents item. (LC-3922756)

When a user places field captions with bottom or right alignment in AEM Forms Designer, the tag tree includes only the caption without the corresponding value, leading to incomplete accessibility tagging. (LC-3922619)

On upgrading from AEM Forms 6.5 Service Pack 6 to AEM Forms Service Pack 20, the QR codes in generated PDFs become unreadable. The alternative text for the QR codes also fails accessibility testing, affecting screen reader compatibility. (LC-3922551)

When a user renders a letter in Agent UI on AEM Forms Service Pack 18, the content fails to display correctly due to the FormService.render() API. (LC-3922461)

In AEM Forms, enabling “Allow Rich Text for Title” on the root panel causes “Exclude Title from Document of Record” on a nested panel to hide the root panel’s title incorrectly. It does so in the generated Document of Record. (FORMS-19696)

The system ignores the custom sling:resourceType assigned through aem:afProperties in a JSON schema on AEM 6.5. The custom resource type is ignored during rendering. (FORMS-19691)

When a user submits an Adaptive Form with prefilled attachments using URIs, the form submission fails with a NullPointerException due to missing binary data. (FORMS-19371) (FORMS-19486)

When a user uploads a PDF under the ‘Forms and Documents’ section in AEM 6.5 Forms, the timeline feature stops functioning. (FORMS-19407)(FORMS-19234)

When a user uploads files using the out-of-the-box (OOTB) file attachment component in AEM Forms, security vulnerabilities are identified. This issue leads to potential interception of the submission process by unauthorized entities. (FORMS-19271)

When a user configures an out-of-the-box Adaptive Form in AEM Forms to generate a Document of Record (DoR) automatically, the “Title” field in Acrobat Reader’s Document Properties does not display the captured DoR title. By default, the form title does not appear in place of the filename. (FORMS-19263)

When a user opens an Interactive Communication in Agent UI, the prefilled data cannot be completely erased; upon removal, it automatically refills with the same data. (FORMS-19151)

When a user previews a date field in the Agent UI, the date unexpectedly changes. This issue occurs due to time zone discrepancies between the VM’s UTC setting and the system’s interpretation of the date. (FORMS-19115)

When a user submits a form, file attachments may duplicate, leading to multiple uploads of the same file. (FORMS-19045)(FORMS-19051)

Adding coordinators to policy sets in AEM 6.5 Document Security fails across both production and lower environments. (FORMS-18603, FORMS-18212, FORMS-19697)

When a user clicks the “datepicker-calendar-icon” in desktop mode with an empty field in AEM Forms Service Pack 22, an error occurs due to the undefined _$focusedDate variable, disrupting associated custom scripts. (FORMS-18483)(FORMS-18268)

On AEM Forms Service Pack 19 (6.5.19.0), when a customer previews a letter, the ‘Amount in words’ field fails to display or update number values incorrectly, leading to misalignment and missing spaces in the content. (FORMS-18437, FORMS-17330, FORMS-18209, FORMS-18557, CTG-4150848,FORMS-19614, LC-3922004)

When a customer previews a saved letter in AEM Forms 6.5 SP19 on RHEL, the content misaligns, spaces are missing, and unexpected characters like ‘x’ appear. (FORMS-18422)(FORMS-17641)

When a user navigates between tabs in AEM Forms, selecting components on the first tab becomes unresponsive. (FORMS-18345)

In AEM Forms 6.5.21.0, when a user converts an HTML file to PDF using the WebToPDF option, the output PDF is missing the header section, including metadata and title tags. (FORMS-18223, FORMS-17835, FORMS-19642, FORMS-18224)

In the AEM JEE Process Manager SDK, when a user invokes the retryAction(long actionOid) method, the system incorrectly retries the first action found in the tb_action_instance table. This workflow occurs even when a specific action ID is provided or when the ID is null, resulting in unintended behavior. (FORMS-18187)

After updating to SP22, a user encounters issues where the saved draft and submission functionalities fail without displaying any error message. (FORMS-18069)

In AEM 6.5.21.0, transitioning from XSD-based foundation components to core components prevents the implementation of cross-file references in JSON schemas, impacting Adaptive Forms migration. (FORMS-18065)

When a user previews a letter in the Agent UI, the date field shows an incorrect value due to IC time conversion issues. These discrepancies arise from time zone differences between the VM environment and the system’s interpretation of time (UTC versus local time). (FORMS-17988) (FORMS-17248)

When a user previews letters using Notice IC templates in AEM Forms, PDF generation times vary significantly, from 1.5 seconds to more than 10 seconds, even on the same server. This inconsistency affects business critical workflows. (FORMS-17951)

When a user binds a Scribble Signature object in an Adaptive Form to an XDP using the ‘Data Sources’ option, changes cannot be saved. The reason is due to persistent aspect ratio validation errors, even when using valid values. (FORMS-17587)

When a user uses a specific XDP with many hidden fields for document fragments, AEM creates CRX nodes with the cm:optional property set to false, which causes the Interactive Communication (IC) submission to fail. (FORMS-17538)

On AEM Forms 6.5.19.0, when a customer previews a letter, the numeric box field fails to handle negative values correctly when digit limits for Lead and Frac are defined. This issue occurs due to the use of parseFloat, which treats the minus sign as part of the number. (FORMS-17451)

On AEM Forms 6.5, when a letter is previewed, the use of the “*” wildcard in the Adobe.json file is noticed, raising a concern about its purpose and potential modification. (FORMS-17317)

When a user uses a screen reader on the Apply for a Fixed Rate Saver joint account the headings are incorrectly announced as clickable, causing accessibility issues. (FORMS-17038)

When a form is embedded, the generated iframe is missing a title attribute, leading to an accessibility compliance issue. (FORMS-17010)

Downloading a form using the Forms Manager UI always includes associated dependencies, such as themes and fragments. (FORMS-15811)

When a user accesses the form on mobile devices (iOS and Android™), the ‘next’ and ‘previous’ buttons on the first page are disabled. However, the screen reader does not identify them as disabled. (FORMS-15773)

When a user saves a large form with fragments and lazy loading enabled, it fails to retrieve drafts, disrupting the workflow. (FORMS-19890, FORMS-19808)

When a user reconfigures the database in AEM Forms, the connection fails due to hardcoded parameters. (FORMS-19568, FORMS-17621)

When a user sets up AEM 6.5 with MySQL 8.4 using the partial turnkey method, the LiveCycle Configuration Manager (LCM) fails to recognize the required MySQL connector driver. This causes the database connection test and setup to fail. (FORMS-19442)

When a user runs LCM with JDBC 12.8.1 on JRE 11 in a JEE environment, the setup fails due to incompatibility issues. (FORMS-19276)

When a user opens a task in AEM On-Premise, the system executes the Workspace Start Action Profile instead of the AssignedUserProfile. (FORMS-19065)

When a user uses the retryAction(long actionOid) method in the AEM JEE Process Manager, unexpected behavior occurs. (FORMS-18357)(FORMS-18187)

On AEM Forms 6.5.21.0, the PDFG conversion fails with the following error: (FORMS-16851)(FORMS-14613)

Issue with JSP scripting bundle in AEM 6.5.21-6.5.23 and AEM 6.5 LTS GA
AEM 6.5.21, 6.5.22, 6.5.23, and AEM 6.5 LTS GA ship with the org.apache.sling.scripting.jsp:2.6.0 bundle, which contains a known issue. The issue typically occurs under high load when the AEM instance handles many concurrent requests.

When this issue occurs, one of the following exceptions may appear in the error logs alongside references to org.apache.sling.scripting.jsp:2.6.0:

• java.io.IOException: classFile.delete() failed
• java.io.IOException: tmpFile.renameTo(classFile) failed
• java.lang.ArrayIndexOutOfBoundsException: Index 0 out of bounds for length 0
• java.io.FileNotFoundException

When this error occurs, the only recovery method is to restart the AEM instance.

Contact Adobe Customer Support and reference this release note for a resolution.

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.

FORMS-20203: When a user upgrades the Struts framework from version 2.5.x to 6.x, the Policies UI in AEM Forms fails to display all configurations, such as the option to add a watermark.

FORMS-20360: After upgrading to AEM Forms Service Pack 6.5.23.0, the ImageToPDF conversion service fails with the error:
17:15:44,468 ERROR [com.adobe.pdfg.GeneratePDFImpl] (default task-49) ALC-PDG-001-000-ALC-PDG-011-028-Error occurred while converting the input image file to PDF. com/adobe/internal/pdftoolkit/core/encryption/EncryptionImp

FORMS-20478: When attempting to convert type 7/8 TIFF files to PDF, the conversion process fails with error “ALC-PDG-001-000-Image2Pdf conversion failed, caused by: com/sun/image/codec/jpeg/JPEGCodec” and “ALC-PDG-016-003-An unknown/unexpected error occurred during PDF post-processing.” The system attempts to retry using TM ImageIO TIFF decoder but ultimately fails to complete the job.

FORMS-14521: If a user tries to preview a draft letter with saved XML data, it gets stuck in Loading state for some specific letters.

AEM Forms now includes an upgrade of Struts version from 2.5.33 to 6.x for the forms component. This delivers previously missed Struts changes that were not included in SP23. The support was added via a Hotfix that you can download and install to add support for the latest version of Struts.

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.

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.

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)

FORMS-15428: 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.

When a user configures a WebLogic 14c instance, the PDFG service in AEM Forms Service Pack 21 (6.5.21.0) on JEE running on JBoss® fails due to classloader conflicts involving the SLF4J library. The error is displayed as follows (CQDOC-22178):

Caused by: java.lang.LinkageError: loader constraint violation: when resolving method "org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory;"
the class loader org.ungoverned.moduleloader.ModuleClassLoader @404a2f79 (instance of org.ungoverned.moduleloader.ModuleClassLoader, child of 'deployment.adobe-livecycle-jboss.ear'
@7e313f80 org.jboss.modules.ModuleClassLoader) of the current class, org/slf4j/LoggerFactory, and the class loader 'org.slf4j.impl@1.1.0.Final-redhat-00001' @506ab52
(instance of org.jboss.modules.ModuleClassLoader, child of 'app' jdk.internal.loader.ClassLoaders$AppClassLoader) for the method's defining class, org/slf4j/impl/StaticLoggerBinder,
have different Class objects for the type org/slf4j/ILoggerFactory used in the signature.

FORMS-21378: When Server-Side Validation (SSV) is enabled, form submissions may fail. If you encounter this issue, please contact Adobe Support for assistance.