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

Form element does not contain label. With screen readers such as NVDA and JAWS, Form label information is not announcing properly. (CQ-4344078)

Drop-downs are not getting closed when the Escape key is used on a keyboard. (CQ-4344077)

The Information icon (the letter “i”) that appears for the inline error suggestion after an invalid input is given, is not accessible using a keyboard. (CQ-4344076)

getManifestURI returns null due to a JCR property being read as toString instead of getString. (ASSETS-18674)

SmartCrop video component is not behaving correctly. The component is carrying-out playback instead of streaming, and VTT calls are failing, giving a 404 error. (ASSETS-18468)

Selecting Properties on an asset’s Viewer page causes a null pointer exception. (ASSETS-18420)

Experience Manager user interface changes for DASH streaming that includes the following:

• having a visible CMAF field in the Video Profile editor.
• having the video upload process send a CMAF flag.
• the options auto, hls, and dash are now available in the playback drop-down list in the Viewer Preset editor’s Behavior tab.
  (ASSETS-17428)

In Navigation, when you select Assets > Files > Create > Carousel Set, the picture icon is overlapped with “Slide 1” text string. (ASSETS-18578)

Unpublished assets are published again. (ASSETS-16428)

Experience Manager Author goes down due to a load issue, prompting the creation of a synthetic alert. (ASSETS-15937)

In the Dynamic Media General Settings page, an untranslated error message Failed to fetch data appears. (ASSETS-15617)

Headless Adaptive Forms enable your developers to create, publish, and manage interactive forms that can be accessed and interacted with through APIs, rather than through a traditional graphical user interface.

Adaptive Forms Core Components are a set of 24 open-source, BEM-compliant components that are built on the foundation of the Adobe Experience Manager WCM Core Components. These components are open-source and provide developers the ability to easily customize and extend these components to match the specific needs of their organization. Anyone with existing skills to customize WCM Core components can easily customize and style these components.

The Reader Extension service on OSGi now provides separate options to enable import and export usage rights on a PDF to import or export data in Adobe Acrobat Reader. (NPR-39909)

When using an Assign task step to send a notification for an assigned task, two emails are sent instead of one to the assigned individual. (NPR-40078)

When a user hides the table headers, it causes the previously set column width to be unset, and all columns retain the same width. (NPR-40063)

In case you change the default password of the admin user from admin, while performing the Prepare Adobe Experience Manager Server For DSC deployment check on the AEM Forms JEE service pack it fails. (NPR-40062), (NPR-39387)

The OutputService and AssemblerService APIs, fail to convert PDF Form to PDF/A. (NPR-39990)

The AssemblerService not able to convert PDF to PDF/A. When a user converts PDF to PDF/A, the following error occurs: PDFAConformance isCompliant="false" compliance="PDF/A-1b" resultLevel="Summary" ignoreUnusedResources="true" allowCertificationSignatures="true"> <Violation count="6" key="PDFA_CS_001_NOT_DEVICE_INDEPENDENT" description="ColorSpace is not device independent. (NPR-39956)

When server-side validation fails for a GuideSubmitServlet API call, the errors are not returned in the response sent to the client. (NPR-39925)

After upgrading to AEM 6.5.15.0 Service Pack on Windows server, the user encounters multiple error messages, and the email service is not working. (NPR-39919)

When you upgrade to AEM 6.5.14.0 and use importData service to merge PDFs with XML, the following error occurs: Caused by: java.lang.NoSuchMethodError: com.adobe.xfa.form.FormModel.isXFABarcode(Lcom/adobe/xfa/Node;)Ljava/lang/Boolean. (NPR-39807)

When user installs Document Security Office extension, following issues occur:

• Microsoft® Excel crashes frequently.
• While opening a secured document, the Document security office extension is not detected as installed on a machine. Instructs the user to download and install the security extension. (NPR-39768)

After a user upgrades to AEM 6.5.15.0 Service Pack, the PostScript-to-Pdf conversion is not working. (NPR-39765), (NPR-39764)

When user tries to open the tour screen after opening an Adaptive Form, it fails with a NullPointer exception:[172.17.0.1[1662032923933]GET/libs/fd/af/content/editors/form/tour/content.htmlHTTP/1.1]com.day.cq.wcm.core.impl.WCMDebugFilterException:org.apache.sling.api.scripting.ScriptEvaluationException:" (NPR-39654)

In Windows, when user enables high contrast black settings, the HTML5 Forms content become unclear when rendered as an HTML preview in the browser. (NPR-39018)

When the user attempts to add metadata, the Save button becomes non-functional for both the Draft and Submission components. (CQ-4349601)

After upgrading to AEM 6.5.15.0 Service Pack, the redirection of relative URLs no longer works in the Visual Editor. (NPR-39947)

When a user upgrades to AEM 6.5.15.0 Service Pack, the redirection stops working with Internet Explorer. (CQ-4351745)

After a user upgrades to AEM 6.5.15.0 Service Pack, HTML heading tag is not recognized. HTML code for the heading tag is displayed as text in the HTML form. (NPR-39915)

When the user tries to submit an Adaptive Form, a typecast error occurs: ERROR [10.207.64.167 [1668589530607] POST /app/LS4/content/forms/af/revalidate/jcr:content/guideContainer.af.submit.jsp HTTP/1.1]( NPR-39809)

When a user previews a Document of Record using the Send Email submit action, it is not displayed correctly. The mail template embeds in the preview of the Document of Record. (CQ-4352155)

When a user previews an Adaptive Form as an HTML on Microsoft® Edge browser with IE compatibility mode, it is not displayed correctly. (CQ-4352216)

The dictionary must include new locales with special characters, such as underscores or hyphens, to enable translation. (NPR-40088)

Update your GraphQL queries that may have used a custom API name for your content model to using 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/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 must add the following properties to the index definition node /oak:index/damAssetLucene (no reindexing 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 register change to complete unregistered.

In AEM Forms, POP3 protocol does not work with email endpoints for Microsoft® Office 365.

On JBoss® 7.1.4 platform, when a user installs AEM 6.5.16.0 service pack, adobe-livecycle-jboss.ear deployment fails.

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 will not get executed, instead throwing a runtime error.