Adobe Experience Manager 6.5 Latest Service Pack Release Notes

Release information

What is included in Experience Manager 6.5.16.0

Experience Manager 6.5.16.0 includes new features, key customer-requested enhancements, bug fixes, and performance, stability, and security improvements, that are released since the initial availability of 6.5 in April 2019. Install this service pack on Experience Manager 6.5.

A key improvement in Dynamic Media is the following:

New protocol DASH (Dynamic Adaptive Streaming over HTTP) support launched for adaptive bitrate streaming in Dynamic Media video delivery (with CMAF [Common Media Application Format] enabled).

• Adaptive streaming (DASH/HLS) ensures better end user viewing experience for videos.
• DASH is the international standard protocol for adaptive video streaming and is widely adopted in the industry.
• Available now in North America (to be enabled via support ticket), coming soon in Asia-Pacific and Europe-Middle East-Africa.

See Enable DASH on your account.

Assets

• Connected Assets: When you enable the Smart Crop options for images on remote DAM, upload images to a folder, and sync the folder to local sites, the folder does not open on the local Sites deployment. (NPR-39912)
• While sorting a collection by name, the list view is not working appropriately (ASSETS-19401)
• When a large media file (JPEG) is uploaded to Collections, Experience Manager stops responding. (ASSETS-19387)
• In the content tree pane, the displayed asset name is incorrect as the location of the asset is not rendered appropriately. (ASSETS-18870)
• While sharing a Collection using a link, the data in the URL mismatches between the shuffle of card view and list view. (ASSETS-18758)
• When you perform an omnisearch by using a filter on the folder type, the search results are inconsistent. (ASSETS-18227)
• The dam:size property is not updated after XMP writeback, which results in incorrect information being returned from the /platform/path/to/asset.jpg;resource=metadata API. (ASSETS-17631)
• Unclosed resource resolver on all Experience Manager instances. (ASSETS-16904)
• Unable to create a version for an asset even if you are assigned the create and modify permissions. (ASSETS-15956)
• The move button is disabled randomly while moving an asset from one point to another. (ASSETS-14889)
• Screen readers are unable to identify headings, as the text is not defined inside heading tags but as the general text. (ASSETS-6924)
• The alternative text under the image is not mandatory but the text displayed under the image is repetitive with a Type attribute. (ASSETS-6915)

Assets - Dynamic Media

• 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 (Common Media Application Format) 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)

Forms

Forms Key Features

• 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)

Forms Fixes

• 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)

Integrations

• Remove Adobe Search&Promote code and dependency from Experience Manager 6.5. Adobe Search&Promote reached end-of-service September 2022. See Adobe Search&Promote End-of-Service Announcement. (NPR-39706)

Sites

• Current cq-wcm-core artifactory release does not have the POM. (SITES-10983)
• The rollout preview action should not list the page to be created. (SITES-10355, CQ-4266213)
• Rollout after MSM detach recreates the detached page. (SITES-9841)
• Creating a launch is timing out; user must wait many minutes on a loading screen before the request times out. (SITES-9051)
• The Rollout Page user interface is displaying non-existent parent page paths. You can roll out the page with a success message, but the child page is not rolled out due to the parent page never getting rolled out in the first place. (SITES-8621)

Sites - Core Components

• Centralize the link processing on e-mail pages so that model customizations are not needed anymore. (SITES-9002)

Sites - Admin User Interface

• CSV Export is not exporting all the pages under the selected page. (SITES-9390)

Sites - Content Fragments

• Unable to print a content fragment’s JSON. The reason is because the GraphQL query cannot be generated when you open the content fragment’s Preview page. (SITES-8619)
• When reopening the Content Fragment Model Editor, all Date and Time fields are defaulting to Date & Time type. (SITES-8401)

Sites - Experience Fragments

• You are unable to move an Experience Fragment to another folder even if the template is listed under allowed templates. (SITES-8601)
• (SITES-7989)

Sites - Page Editor

• Update dependencies for the resource resolver improvement made in SITES-8464 in which page rendering in Authoring mode created a high number of TemplatedResourceImpl objects. (SITES-9350)

Sling

• Experience Manager is deadlocked on startup. (NPR-39832)
• When many vanity paths are present in Experience Manager’s version storage, Experience Manager fails to start. (NPR-38955)

Translation projects

• In MicrosoftTranslationServiceImpl, the query string parameter Category is incorrect. (NPR-39828)
• Creating a translation project displays the error Master page resource does not exist; the translation project is not created. (NPR-39762)
• Unable to set a due date on a translation project that uses a human translation connector. (NPR-39593)

User interface

• When changing to a smaller resolution, the DatePicker does not display, and the AM/PM select does not display or change visibly. (NPR-39948)
• When minify js (minimization of JavaScript) is used, it does not process the minification due to a parsing error. (NPR-39650)
• Tag field (/libs/cq/gui/components/coral/common/form/tagfield) conflicts with timeline. (CQ-4350751)

WCM

• The rollout preview action should not list the page to be created. (CQ-4266213, SITES-10355)

Workflow

• Manually deleting the editable workflow model from /conf leaves a lingering runtime model instance without an editable model. (CQ-4349365)

Install Experience Manager 6.5.16.0

• Experience Manager 6.5.16.0 requires Experience Manager 6.5. See upgrade documentation for detailed instructions.
• The service pack download is available on Adobe Software Distribution.
• On a deployment with MongoDB and multiple instances, install Experience Manager 6.5.16.0 on one of the Author instances using the Package Manager.

Install the service pack on Experience Manager 6.5

1. Restart the instance before installation if the instance is in update mode (when the instance was updated from an earlier version). Adobe recommends a restart if the current uptime for an instance is high.

2. Before installing, take a snapshot or a fresh backup of your Experience Manager instance.

3. Download the service pack from Software Distribution.

4. Open Package Manager, then select Upload Package to upload the package. To know more, see Package Manager.

5. Select the package, then select Install.

6. To update the S3 connector, stop the instance after installation of the Service Pack, replace the existing connector with a new binary file provided in the install folder, and restart the instance. See Amazon S3 Data Store.

Automatic installation

There are two different methods that you can use to automatically install Experience Manager 6.5.16.0.

• Place the package into ../crx-quickstart/install folder when the server is available online. The package is automatically installed.
• Use the HTTP API from Package Manager. Use cmd=install&recursive=true so that the nested packages are installed.

Validate the installation

To know the platforms that are certified to work with this release, see the technical requirements.

1. The product information page (/system/console/productinfo) displays the updated version string Adobe Experience Manager (6.5.16.0) under Installed Products.

2. All OSGi bundles are either ACTIVE or FRAGMENT in the OSGi Console (Use Web Console: /system/console/bundles).

3. The OSGi bundle org.apache.jackrabbit.oak-core is version 1.22.14 or later (Use Web Console: /system/console/bundles).

Install Service Pack for Experience Manager Forms

For instructions to install the service pack on AEM Forms, see AEM Forms Service Pack installation instructions.

UberJar

The UberJar for Experience Manager 6.5.16.0 is available in the Maven Central repository.

To use UberJar in a Maven project, see how to use UberJar and include the following dependency in your project POM:

<dependency>
     <groupId>com.adobe.aem</groupId>
     <artifactId>uber-jar</artifactId>
     <version>6.5.15</version>
     <scope>provided</scope>
</dependency>

Deprecated features

Below is a list of features and capabilities that are marked as deprecated with Experience Manager 6.5.7.0. Features are marked deprecated initially and later removed in a future release. An alternate option is provided.

Review if you use a feature or a capability in a deployment. Also, plan to change the implementation to use an alternate option.

Known issues

• AEM Content Fragment with GraphQL Index Package 1.0.5
  This package is needed for customers using GraphQL; this enables them to add the required index definition based on the features they actually use.

• Please 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.

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

• 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; i.e. 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
  

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

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

OSGi bundles and content packages included

The following text documents list the OSGi bundles and Content Packages included in Experience Manager 6.5.16.0:

• List of OSGi bundles included in Experience Manager 6.5.16.0
• List of Content Packages included in Experience Manager 6.5.16.0

Restricted websites

These websites are only available to customers. If you are a customer and need access, contact your Adobe account manager.

• Product download at licensing.adobe.com
• Contact Adobe Customer Support.

Business.Adobe.com resources

Automated Onboarding Personalized Experiences Content Intelligence Mobile Forms Dynamic Media Dynamic Forms