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

Assets, Dynamic Media - Multi-subtitle and multi-audio track support for videos in Dynamic Media—You can now easily add multiple subtitles and multiple audio tracks to a primary video. This capability means that your videos are accessible across a global audience. You can customize a single, published primary video to a global audience in multiple languages and adhere with accessibility guidelines for different geographical regions. Authors can also manage the subtitles and audio tracks from a single tab in the user interface.

Assets - From Search results, you can now navigate to the folder location that contains an asset to let you perform various asset management tasks. (ASSETS-23182)

Sites Polaris Picker in Content Fragments has improved performance. (SITES-14092)

Enabled Sites Page Editor/Image Component user to reference assets from the remote Assets Cloud Service. (SITES-13448, SITES-13433)

To quickly find a project in List view, where you may have many projects in your system, Adobe now supports server-side sorting. Project nodes are sorted on the backend based on the column selected by the user before rendering them in the user interface. (NPR-41027)

AEM 6.5.18.0 supports MongoDB 5.0 to 6.0.

Enhanced error handling with custom error handlers in the rule editor – You can now invoke a custom function (using Client Library) in response to an error returned by an external service. And, you can provide a tailored response to end users. Or, you can take specific actions for errors returned by a service. For example, you can invoke a custom workflow in the backend for specific error codes or inform the customer that the service is down

Enhanced Adobe Sign Workflow step – Adobe Sign workflow step in AEM Workflows is available with the following enhancements.

• Enhanced Security with Government ID-Based Authentication for Adobe Sign – Adobe Acrobat Sign’s Government ID-Based Authentication offers an additional layer of verification. It enables users to authenticate their identity using government-issued IDs (driver’s license, national ID, passport). By using trusted identification documents, this enhancement adds an extra level of confidence to the signing process, making it ideal for scenarios that require heightened security, compliance, and user validation.

• Enhanced Transparency with Audit Trail for Adobe Sign Documents – Use the Audit Trail feature for detailed insights into the lifecycle of your Adobe Sign documents. With the Audit Trail, you can now maintain a comprehensive record of all actions and interactions related to your documents. This includes details such as who viewed, edited, or signed the document, along with timestamps for each event. This enhancement is crucial for maintaining compliance, resolving disputes, and ensuring the integrity of your digital agreements.

• Expanded the roles for Agreement recipients beyond just the Signer – Adobe Acrobat Sign lets you expand the roles for Agreement recipients beyond just the Signer to better match their workflow requirements. When enabled, each recipient in an Agreement has their role individually configurable, with Signer being the default.

AEM Forms on JEE full installer – The service pack brings a full installer for AEM Forms on JEE that brings support for multiple new software combinations, including:

• Microsoft® Windows Server 2022
• Microsoft® Active Directory 2022
• Oracle WebLogic 14C on Windows Server 2022
• Red Hat® JBoss® 7.4.10
• MongoDB 6.0
• MySQL JDBC Connector 8

Document Services

• When a user uses a transformPDF service, it fails with an exception: java.lang.ClassNotFoundException: default task-158Class name com.adobe.internal.afml.AFMLExceptionInvalidParameter from package com.adobe.internal.afml (FORMS-9957)
• If the server is shut down during PDF document generation, post-server startup job processing errors are thrown. The argument -Dcom.adobe.livecycle.dsc.deferServiceStart=true must be added during server startup. (FORMS-9836)
• If a user tries to merge PDFs using the AssemblerService.Invoke method, the assembler fails to perform the task. (FORMS-9550)
• When you upgrade to AEM 6.5.15.0 Service Pack on OSGI and JEE environments, the Assembler service using a specific template stops working. (FORMS-9355, FORMS-9445, FORMS-9408)
• Java™ garbage collection is unable to clear old-gen heap on an AEM Forms OSGi server, as the Global Timeout for XMLFormService is not configured to a proper value. (FORMS-9384, FORMS-9035)
• While rendering the PDF preview of an Adaptive Form, the unwanted Java™ stack dumps appear in the error logs. (FORMS-8865)
• When a user reviews the document status for documents in the document details section, it is not displayed correctly. (FORMS-8946, FORMS-10424)
• When a user upgrades to AEM Forms and uses the sendToPrinter service, there is a continuous increase in heap utilization. (FORMS-10148)
• On JBoss® 7.4 EAP server, the email functionality fails with java.io.IOException. (FORMS-10138)
• When a user uses the transformPDF service, it fails with an error: java.lang.ClassNotFoundException: default task-158Class name com.adobe.internal.afml.AFMLExceptionInvalidParameter from package com.adobe.internal.afml(FORMS-9957)
• After upgrading to AEM Service Pack 6.5.14.0, the issue arises in the assembler service when using a specific template. (FORMS-9445, FORMS-9408)

Adaptive Forms

• When a user tries to call a custom function without modifying a field, such as setting the value of another field, it fails. (FORMS-9921)

• While working with the custom error function for the Rule Editor in an Adaptive Form, the following errors occur:

  • When a user tries to use @param{boolean} with a function, the rule editor does not allow Boolean values to pass to a function.
  • When a user tries to use @param{string} with a function, the rule editor fails to pass the optional values and warns of incomplete rules. (FORMS-9816, FORMS-9815)

• The forms-user group fails to call the Rule Editor twice in an Adaptive Form. (FORMS-9051)

• In a visual editor, when a user selects a Form object then whole field instance object is passed to the custom function instead of just the value of the field. (FORMS-10015)

• When a user creates a core component-based Adaptive Form and adds a text input component, Is Empty and Is Not Empty do not work in the Rule editor. (FORMS-10098)

• If a field is marked as invalid in a core component based Adaptive Form, it starts a change event on the field. (FORMS-10087)

• When a user tries to create an Adaptive Form using a complex JSON schema, it fails. The error occurs as:
  GET /content/forms/af/katezeroone/testaf1.html HTTP/1.1] com.adobe.aemds.guide.service.impl.JsonObjectCreatorImpl Could not emit JSON with context java.lang.ArrayIndexOutOfBoundsException:0. (FORMS-9639)

• In an Adaptive Form, when a user disables the “I agree to the terms & conditions” checkbox, it gets enabled again when the user scrolls down. (FORMS-9458)

• When a user opens an Adaptive Form on an Android™ device, using Google Chrome/Firefox, and enters the maximum allowed characters in a Textbox, the value in the textbox fails to clear. (FORMS-9354)

• When the label of the checkbox includes special characters like ‘,’, ‘/’, or ‘.’, clicking the text/label does not select the respective checkbox. (FORMS-9313)

• When a user tries to validate the Terms and Conditions component, it fails to validate if the component is not in focus while the other component gets validated. (FORMS-8725, FORMS-8913)

• If an Adaptive Form is reloaded after upgrading to AEM 6.5.16.0 Service Pack, the file attachment retrieval fails. (FORMS-8906)

• In an Adaptive Form based on an XDP, if a checkbox component includes a text title assigned a numeric value, the text title gets truncated and does not match the assigned value. (FORMS-8743)

• If a user tries to implement lazy loading on a fragment embedded in an Adaptive Form for the author environment, the rules/logic defined for the fragment are not reflected in the form. (FORMS-8554, FORMS-9182)

• When you try to open any Coral dialog in AEM 6.5.16.0 Service Pack, it generates the error.log: cannot render resource exception. (FORMS-8942)

• When a user tries to translate a checkbox with a single option in an Adaptive Form, it fails. (FORMS-10181)

• All Document of Record (DoR) templates fail to publish. Only English locale-based DoR templates and their associated Forms-based DoR templates get published. (FORMS-10535)

Accessibility

• When using the Scribble Signature component in an Adaptive Form, the following errors occur:

  • After the Scribble Signature component, when there are more components, pressing the Tab key does not traverse to the signature dialog box; instead, it moves to the next component. Only after traversing all components, it finally moves to the signature dialog box.
  • When a user signs in the signature dialog box using a brush or keyboard, pressing the Enter key does not close the dialog box.
  • The clear signature confirmation dialog cannot be accessed using a keyboard.
  • The screen reader fails to read information entered in a dialog box.
  • It is not possible to clear the signature without using a mouse. (FORMS-9317)

• When a user submits an Adaptive Form, the screen reader fails to read error messages for the mandatory fields. (FORMS-9316)

• When a screen reader reads an HTML form, the issue occurs while reading the text with kerning (spacing). (FORMS-9258)

• In an Adaptive Form, the references/footnotes linked to the text are not called out using the screen reader. (FORMS-8920)

• Accessibility tags are not recognized properly in the latest Designer. (FORMS-10139)

Interactive Communications

• In Correspondence Management, the localization is not working. (FORMS-8926)
• The draft letter fails to open when the publishAll service is used. (FORMS-8589)
• After Experience Manager, Service Pack 16 is installed on the servers, all the Interactive communication Letters starts to clock if they try to edit these letters. If they provide any sample payload to preview or view/edit the properties page, they work. However, they are not able to edit the letters. (FORMS-9067)

Page publishing not working in Page Editor after upgrading to Service Pack 18 (6.5.18.0)

After you upgrade an instance of AEM 6.5.0.0—6.5.17.0 to AEM 6.5.18.0, when you click Publish Page inside the Page Editor, you are redirected to a URL that does not exist.

To work around this issue, do one of the following:

• Remove the following “path” property.

  /libs/wcm/core/content/editor/jcr:content/content/items/content/header/items/headerbar/items/pageinfopopover/items/list/items/publish/granite:data

• Paste the correct URL directly into the browser.

  http://localhost:4504/editor.html/libs/wcm/core/content/sites/publishpagewizard.html?item=/content/we-retail/language-masters/en/about-us.html

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:

• contentFragment
• model

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, as 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 correctly declare their variables, otherwise they do not get run, instead throwing a runtime error.

On JBoss® 7.1.4 platform, when user installs Experience Manager 6.5.16.0 or later service pack, adobe-livecycle-jboss.ear deployment fails. (CQ-4351522, CQDOC-20159)

After upgrading to AEM Forms 6.5.18.0 JBoss Turnkey full installer environment on Windows Server 2022, when compiling Output client application code using Java 11, the following compilation error may occur:

error: error reading [AEM_Forms_Installation_dir]\sdk\client-libs\common\adobe-output-client.jar; java.net.URISyntaxException:
Illegal character in path at index 70: file:/[AEM_Forms_Installation_dir]/sdk/client-libs/common/${clover.jar.name} 1 error

To resolve the issue, perform the following steps:

1. Navigate to [AEM_Forms_Installation_dir]\sdk\client-libs\common\ and unzip adobe-output-client.jar to extract the Manifest.mf file.

2. Update the Manifest.mf file by removing the entry ${clover.jar.name} from the class-path attribute.

   note note
   NOTE
   You can also use an in-place editing tool, for example, 7-zip, to update the Manifest.mf file.

3. Save the updated the Manifest.mf in the adobe-output-client.jar archive.

4. Save the modified adobe-output-client.jar file and re-run the setup. (CQDOC-20878)

After installing AEM Service Pack 6.5.18.0 full installer, the EAR deployment fails on JEE using JBoss® Turnkey.
To resolve the issue, locate the <AEM_Forms_Installation_dir>\jboss\bin\standalone.bat file and update Adobe_Adobe_JAVA_HOME to Adobe_JAVA_HOME for all occurrences before running the configuration manager. (CQDOC-20803)