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

New Adaptive Form Core Components: Vertical tabs, Terms & Conditions, and Checkbox are added to enhance the scalability of forms.

• Checkbox component: Adaptive Forms based on Core Components can now include a checkbox component. It allows users to make binary choices, selecting or deselecting a particular option. It typically appears as a small box that can be clicked or tapped to toggle between two states: checked and unchecked. The checkbox is a common form element used to present a yes/no or true/false choice.

• Terms and Conditions component: Adaptive Forms based on Core Components can now include a Terms and Conditions component. It allows Forms authors to introduce a specific section within the form where users are presented with the terms, conditions, or legal agreements associated with the use of a service, product, or platform. This component is designed to inform users about the rules, regulations, and obligations they are agreeing to by submitting the form.

  

• Vertical tabs component: Adaptive Forms based on Core Components can now organize form content into a vertical list of tabs, providing a structured and navigable layout. The use of vertical tabs in a form can enhance the overall user experience by simplifying navigation and improving the organization of form content, especially in situations where a form contains multiple sections or complex information.

64-bit version of AEM Forms Designer: The 64-bit version of AEM Forms Designer brings enhanced performance, scalability, and memory management to empower your form creation experience. With the 64-bit architecture, you can tackle even larger and more complex projects with ease, ensuring seamless design workflows and optimized efficiency. Elevate your form design capabilities and embrace the future of AEM Forms Designer with this cutting-edge release.

Connect an Adaptive Forms with Microsoft® SharePoint List: AEM Forms provide an out-of-the-box integration to submit forms data directly to SharePoint List, letting you use SharePoint’s Lists capabilities. You can configure Microsoft® SharePoint List as a datasource for a Form Data Model and use the Submit using Form Data Model submit action to connect an Adaptive Form with SharePoint List.

Support to configure Document of Record properties for Adaptive Form Fragments: You can now easily customize your Adaptive Form fragments and its fields in Adaptive Form editor.

64-bit XMLFM: The 64-bit iteration of XMLFM introduces heightened performance, scalability, and refined memory management. It is the first 64-bit native service deployed on the server-side. By harnessing its inherent capability to access larger memory resources compared to its 32-bit counterpart, XMLFM 64-bit empowers seamless handling of larger rendering workloads. This milestone not only represents a leap in performance but also introduces key enhancements to the native service framework within the AEM Forms Server. This update equips AEM Forms Server to seamlessly support any 64-bit native service.

• OutputServiceException AEM_OUT_001_003:Unexpected Exception: 0 Out of Memory Caused by: org.omg.CORBA.COMM_FAILURE: null (LC-3921530)

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, 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

When executing a GraphQL query using optional variables, if a specific value is not provided for the optional variable, then the value for that variable will be considered an implicit null. This means that the filter will match only null values for the corresponding property.

For example, in the query below, where no value is specified for the property lastName:

query getAuthorsFilteredByLastName($authorLastName: String) {
authorList(filter:
  {
    lastName: {_expressions: {value: $authorLastName}
    }}) {
  items {
    lastName
    }
  }
}

Only authors with the lastName property set to null will be returned:

{
"data": {
  "authorList": {
    "items": [
      {
        "lastName": null
      }
    ]
  }
}
}

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.

When an Adaptive Form is published, all its dependencies, including policies, get republished, even if no modifications have been made to them. (FORMS-10454)

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.

When users perform the submit action, the submission fails with an error:
javax.servlet.ServletException: java.lang.NoSuchMethodError
To resolve the issue, recompile the Sling scripts such as JSP, Java™, and Sightly. (FORMS-8542)

After installing AEM Service Pack 6.5.14.0 and onwards, users are unable to select a font from the JEE Admin UI for PDF documents when navigating to Home > Services > PDF Generator > Adobe PDF Settings, as the font list appears empty. (FORMS-12095)

Adaptive Forms let you use custom functions with ECMAScript version 5 or earlier. When a custom function uses ECMAScript version 6 or later, like ‘let’, ‘const’, or arrow functions, the rule editor might not open properly.

When you submit an adaptive form, the checkbox stores the wrong value. It adds an extra “/” for each “,”. (FORMS-12093)

When you submit an Adaptive Form based on Core Components, the form fails to submit. Apply the feature toggle - ft-cq-4324864 to fix the issue. To apply a feature toggle:

1. Open the URL: http://[server]:[port]/system/console/configMgr
2. Search and open the com.adobe.granite.toggle.impl.dev.DynamicToggleProviderImpl configuration
3. Specify the feature toogle number. For example, ft-cq-4324864.
4. Save the configuration. The feature is now enabled. (FORMS-12789)

In an Adaptive Form based on an XDP with embedded scripts on checkboxes, the scripts are not executed for elements after such checkboxes. (FORMS-14244)

Rows in the date picker widget are truncated when traversing through months in the pop-up widget for fields with Edit/Display pattern. (FORMS-13620)

When an Adaptive Form is submitted from an Adobe Experience Manager Publish instance to an Adobe Experience Manager Workflow, the workflow fails to save the attachments. (FORMS-14209)

Critical security vulnerabilities have been reported for Struts 2 RCE, a popular and open-source web application framework for developing Java EE web applications. Adobe has released AEM 6.5 Service Pack 19.1 (6.5.19.1) to address the vulnerability in AEM Forms on JEE.

The PDF Generator service fails to enumerate the fonts available on the server. Consequently, the font selection panel on the Adobe PDF Settings page in the PDFG Admin UI remains empty, effectively preventing (un)embedding of chosen fonts. (FORMS-12095)