Adobe Experience Manager 6.5.10.0 experience-manager-65100

Adobe Experience Manager 6.5.10.0 includes new features, key customer-requested enhancements, and performance, stability, and security improvements, that are released since the availability of 6.5 release in April 2019. The service pack is installed on Adobe Experience Manager 6.5.

The key features and enhancements introduced in Adobe Experience Manager 6.5.10.0 are:

  • Enhanced Content Fragment Models and Editor: You can now create complex and custom models for structured content using nested Content Fragment models. Content structures are modularized into basic elements that are modeled as sub-fragments. Higher-level fragments reference these sub-fragments. More data type enhancements such as advanced validation rules further enhance the flexibility of content modeling with Content Fragments. The Experience Manager Content Fragment editor supports nested fragment structures in a common editor session, with enhancements such as structure tree view and tabbed breadcrumb navigation through fragment hierarchies.

  • GraphQL API for Content Fragments: The new GraphQL API is the standard method to deliver structured content in JSON format. GraphQL queries let clients request only the relevant content items to render an experience. Such a selection eliminates content over-delivery (possibility with HTTP REST APIs) that requires content parsing on the client side. GraphQL schemas are derived from Content Fragment models, and API responses are made in JSON format.

  • GraphQL API for Content Fragments: To support GraphQL API, hyphens are no longer allowed in the Content Fragment Model Property Field. GraphQL queries might return unwanted results if a hyphen is present in any of the Content Fragment Model property names.
    Only the following characters are allowed for property name: A-Za-z0-9_. A digit cannot be in the first position.

  • Hierarchy management and future preview: Users now have an interface to access the content structures of their Experience Manager launches, including the ability to add and remove pages in a launch. This feature enhances the flexibility of Experience Manager launches to author content versions targeted for future publishing. Time-warp feature lets users preview launches as future content states.

  • Connected Assets: Experience Manager extends the Connected Assets functionality to the use of Dynamic Media images in the applicable core components. See use Connected Assets.

  • Link share options to download assets or renditions: When sharing assets and Collections as link, users can choose whether to allow the download of original assets, or their renditions, or both using the shared link. Also, the users who download the assets shared with them through link get the option to download only the original assets, only the renditions, or both. See Share assets via link.

    option to allow download only original assets, only the renditions, or both

  • Limit sub-assets generated: Administrators can limit the number of sub-assets that Experience Manager generates for compound assets such as PDF, PowerPoint, InDesign, and Keynote files. See Manage compound assets.

    limit the sub-asset generation

  • Camera Raw support: A new Camera Raw package is available that supports Adobe Camera Raw v10.4. See process images using Camera Raw.

  • The built-in repository (Apache Jackrabbit Oak) is updated to 1.22.8.

  • Accessibility enhancements:

  • User experience enhancements:

    • Experience Manager directly displays a list of all the content models under a folder without content authors having to navigate through the file structure. The feature now requires fewer clicks and improves authoring efficiency.

    • Pathfield in Sites editor allows authors to drag assets from Content Finder.

  • Added support for GuideBridge#getGuidePath API in AEM Forms.

  • You can now use Automated Forms Conversion service to convert PDF Forms in French, German, Spanish, Italian, and Portuguese languages to adaptive forms.

  • Error messages in Properties browser: Added error messages for each property in the Adaptive Forms Properties browser. These messages help understand allowed values for a field.

  • Support to use the literal option to set value for a JSON type variable: You can use literal option to set value for a JSON type variable in the set variable step of an AEM Workflow. The literal option lets you specify a JSON in the form of a string.

  • Platform Updates: Adobe Experience Manager Forms on JEE has added support for the following platforms:

    • Adobe Acrobat 2020
    • Ubuntu 20.04
    • Open Office 4.1.10
    • Microsoft Office 2019
    • Microsoft Windows Server 2019
    • RHEL8

The following is the list of fixes provided in Experience Manager 6.5.10.0 release.

Sites sites-65100

  • The focus shift to another field when typing in the Default Value field under the Properties tab of the Content Fragment Editor (NPR-36992).

  • While filtering Content Fragment models under a specified path, Experience Manager search returns all nodes with cq:Template instead of returning paths and nodes only for the Content Fragment model (SITES-1453).

  • Content Fragments return null as the status of folders (SITES-1157).

  • Experience Manager does not let users disable and enable Content Fragment Models (SITES-1088).

  • When a user moves, rename, or deletes Content Fragments or media assets, the referenced Content Fragments are not automatically updated (SITES-196).

  • Pasting components from one page to another produces JavaScript errors (NPR-37030).

  • When page properties are viewed quickly, Page Properties for a different page are opened (NPR-37025).

  • The Content Fragment allows the Content Fragment to reference itself. The picker does not support the operation (NPR-36993).

  • After upgrading to service pack 9, some users cannot move folders in Experience Manager and see errors in the logs (SITES-1481).

  • While adjusting the width of the component in the layout container on edit mode, a flicker is observed (NPR-36961).

  • On promoting a launch, the changes in the promoted launch are double rolled out to the other launches. If a user promotes the double rolled out launch, the doubled contents is reflected on the source page (NPR-36893).

  • Experience Manager adds a gray border to some PNG images with transparency if you add the images to a page using the Image Core Component or if you resize using the Foundation Image component (NPR-36879).

  • Experience Manager Sites Admin UI with a high number of templates results in slow navigation (NPR-36870).

Forms forms-65100

NOTE
  • Experience Manager Forms releases the add-on packages one week after the scheduled Experience Manager Service Pack release date.

AEM 6.5.10.0 Forms includes the following bug fixes:

  • When you install AEM 6.5 Forms, the following third-party libraries are installed automatically (CQDOC-18373):

    • Microsoft Visual C++ 2008 Service Pack 1 (x86)
    • Microsoft Visual C++ 2010 Service Pack 1 (x86)

Adaptive Forms

  • If the validations performed on the field values in an adaptive form are successful, AEM Forms fails to invoke the Form Data Model (CQ-4325491).

  • When you add a language dictionary to a translation project and then open the project, AEM Forms displays an error message (CQ-4324933):

    code language-txt
    Uncaught TypeError: Cannot read property 'PROJECT_LISTING_PATH' of undefined
    at openButtonClickHandler (clientlibs.js:245)
    at HTMLButtonElement.onclick (clientlibs.js:258)
    
  • Performance issues after installing AEM Forms Service Pack 7 (CQ-4326828).

Correspondence Management

  • Delay in the display of characters in the Data tab and in the HTML letter preview (NPR-37020).

  • When you are editing a text document fragment, the new words display as HTML tags after saving the fragment (NPR-36837).

  • Unable to view the letters that are saved as drafts (NPR-36816).

  • When you edit a text document fragment and then preview the letter, AEM Forms displays the expression language in the HTML letter preview (CQ-4322331).

  • Issues while rendering data with a self-service letter template (NPR-37161).

Interactive Communications

  • A tab character duplicates between two words each time you print preview an Interactive Communication after editing a text document fragment (NPR-37021).

  • AEM Forms displays an error when you save a text document fragment that exceeds the maximum size limit (NPR-36874).

  • When you add an image to an Interactive Communication, an additional empty block displays after the image (NPR-36659).

  • When you select all text in an editor, you cannot change the font text to Arial (NPR-36646).

  • When you create a URL in an editor and preview the changes, a black background displays instead of the URL text (NPR-36640).

  • When you copy and paste text to an editor, there are issues while changing the font to Arial for bullets available in the document (NPR-36628).

  • Indentation issues for bullets in the text editor (NPR-36513).

Designer

  • Screen Reader fails to read floating field data placed inside text label on the Master page or on Subform pages in a dynamic PDF (CQ-4321587).

Document Services

  • When you convert XDP files to PDF files and then assemble the resultant PDF, the PDF generations fails and displays the following error message:

    code language-txt
    Caused by: com.adobe.fd.assembler.client.AssemblerException$ClientException: Document is in a disposed state!
    

Forms Workflow

  • Unable to submit a form to a Workbench process after upgrading to AEM Forms Service Pack 8 (CQ-4325846).

HTML5 Forms

  • When you set the value for the mfAllowAttachments property as True in the CRX DE repository, the dataXml gets corrupted on submitting the HTML5 form (NPR-37035).

  • When you render an XDP as HTML using dataXml, AEM Forms displays a Page Unresponsive error (NPR-36631).

Commerce commerce-65100

  • The value in the Published By field displayed is incorrect in the Column view (NPR-36902).
  • When a Catalog is rolled out, new products are incorrectly marked as modified products (NPR-36666).
  • When you recreate a deleted product, the product page is not recreated (NPR-36665).
  • Modified pages are updated but the corresponding linked products are not updated on Catalog rollout (CQ-4321409, NPR-36422).
  • The Publish later and Unpublish later workflows do not work (CQ-4327679).

For information on security updates, see Experience Manager security bulletins page.

UberJar uber-jar

The UberJar for Experience Manager 6.5.10.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.10</version>
     <scope>provided</scope>
</dependency>
NOTE
UberJar and the other related artifacts are available on Maven Central Repository instead of Adobe Public Maven repository (repo.maven.apache.org). The main UberJar file is renamed to uber-jar-<version>.jar. So, there is no classifier, with apis as the value, for the dependency tag.

Known issues in Experience Manager 6.5.10.0 known-issues

  • 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 are upgrading your Experience Manager instance from 6.5 to 6.5.10.0 version, you can view RRD4JReporter exceptions in the error.log file. To resolve the issue, restart the instance.

  • 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 reg change to complete unregistered.
recommendation-more-help
19ffd973-7af2-44d0-84b5-d547b0dffee2