�۶���Ƶ

Support for Oauth Credentials: A new and easier to use credential for server-to-server authentication, replacing the existing Service Account (JWT) credential. (NPR-41994)

Rule Editor enhancements in AEM Forms:

• Support for implementing nested conditions with When-then-else functionality.
• Validate or reset panels and forms, including fields.
• Support for modern JavaScript features such as let and arrow functions (ES10 support) within the Custom Functions.

AutoTag API for PDF Accessibility: AEM Forms on OSGi now support the new AutoTag API to enhance PDF for accessibility standards by adding tags: paragraphs, and lists. It makes PDFs more accessible for users with assistive technology.

16-bit PNG support: PDF Generator’s ImageToPdf service now supports conversion of PNGs with 16-bit color depth.

Apply artifacts to individual text blocks in XDPs: Forms Designer now lets users configure settings on individual text blocks in XDP files. This ability lets you control the elements that are treated as artifacts in the resulting PDFs. These elements, such as headers and footers, are made accessible for assistive technologies. The key features include marking text blocks as artifacts, and embedding these settings in the XDP metadata. The Forms Output service applies these settings during PDF generation, ensuring proper PDF / UA tagging.

AEM Forms Designer is certified with GB18030:2022 standard: With the GB18030:2022 certification, now Forms Designer supports the Chinese Unicode character set that lets you input Chinese characters into all editable fields and dialog boxes.

Support for WebToPDF route in JEE Server using the PDF Generator service now supports the WebToPDF route for converting HTML files to PDF documents on JEE, in addition to the existing Webkit and WebCapture (Windows only) routes. While the WebToPDF route is already available on OSGi and extended to JEE. Now, on both JEE and OSGi platforms, the PDF Generator service supports the following routes across different operating systems:

• Windows: Webkit, WebCapture, WebToPDF
• �����Գܳ�®: Webkit, WebToPDF

In AEM 6.5.18, it does not show all the hotspots added to an asset when you edit the hotspots. However, all the hotspots work in a published asset, but you cannot edit them later if you needed to. (ASSETS-33609)

The latest EPS files that get uploaded are not generating thumbnails after reprocessing. (ASSETS-32617)

In Tools > Assets > Dynamic Media Publish Setup > Request Attributes tab, the inputs Width(px) and Height(px) look different in Spanish, Italian, and Portuguese. They are not aligned with each other for these locations. (ASSETS-31896)

Effective May 01, 2024, �۶���Ƶ Dynamic Media ended support for the following:

• SSL (Secure Socket Layer) 2.0

• SSL 3.0

• TLS (Transport Layer Security) 1.0 and 1.1

• The following weak ciphers in TLS 1.2:

  • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
  • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
  • TLS_RSA_WITH_AES_256_GCM_SHA384
  • TLS_RSA_WITH_AES_256_CBC_SHA256
  • TLS_RSA_WITH_AES_256_CBC_SHA
  • TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
  • TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
  • TLS_RSA_WITH_AES_128_GCM_SHA256
  • TLS_RSA_WITH_AES_128_CBC_SHA256
  • TLS_RSA_WITH_AES_128_CBC_SHA
  • TLS_RSA_WITH_CAMELLIA_256_CBC_SHA
  • TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
  • TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
  • TLS_RSA_WITH_SDES_EDE_CBC_SHA

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

When a user clicks Print to PDF on AEM Forms Service Pack 15 (6.5.15.0) on OSGi, the Client-side validation fails, it is evident by the error messages shown in the Developer Tools Console window. (FORMS-14029)

When a user submits a form on AEM 6.5 Forms Service Pack 17 (6.5.17.0), or Service Pack 18 (6.5.18.0), Service Pack 19 (6.5.19.0), the translation of “Thank-You” messages does not function correctly. However, the messages are correctly translated in the dictionary. (FORMS-13846)

When a user previews a form having a Date-Picker component, the date-picker field misaligns with the other form fields. (FORMS-13763)

When a user on the environment AEM Forms Service Pack 19 (6.5.19.0) calls the API to format numbers, the formatted numbers are not aligned with the respective Locales. As a result, the currency signs are not displayed correctly. The issue persists regardless of the Locale parameter set to “de_DE” or “en_US.” (FORMS-13759)

When a user on the environment AEM Forms Service Pack 19 (6.5.19.0) converts 16-bit PNGs to PDFs using Img2Pdf PDFG service, it fails and is unable to “Use Acrobat Image conversion” service. (FORMS-13754)

On AEM Forms Service Pack 19 (6.5.19.1), when a user uploads an existing JobOptions file in the Services / PDF Generator / �۶���Ƶ PDF Settings section of the adminui of AEM forms JEE, the upload fails. It also shows the following error message (FORMS-13597):
"An error has occurred while processing your request. Please use the breadcrumb links to navigate to another page."

When a user migrates from AEM Forms Service Pack 15 (6.5.15.0) to AEM Forms Service Pack (6.5.17.0) or AEM Forms Service Pack (6.5.19.0), the FD key duplicates, which cause the forms not to translate correctly. (FORMS-13461)

When a user puts dispatchers in front of the authors supported by the deployment topology on AMS, the Assign Task submission hangs or fails. (FORMS-8010)

Accessibility Related Fixes:

• Icons on the “formsanddocuments” page are now accessible as per the ANDI standard. (FORMS-13094)
• Users can access the tool bar by way of the keyboard to save or edit content on the edit page, the tool bar is enhanced as per the ANDI standard. (FORMS-13102)
• “Required or Mandatory” form fields are accessible as per the ANDI standard. (FORMS-13097)

When a user tries to view a form on the page load, it fails to render. (FORMS-13594)

The date input field component does not function correctly on Microsoft Edge in Internet Explorer compatibility mode. (FORMS-13170)

Stalled email Notification with attachment failed to be sent when the fix for additional steps to use email with attachments is performed on the server. (FORMS-14227)

On AEM Forms Workspace on Service Pack 18 (6.5.18.0), When a user comments on any uploaded document, it causes the document file to corrupt. (FORMS-13735)

On AEM Forms Service Pack 18 (6.5.18.0), or Service Pack 19 (6.5.19.0), or Service Pack 20 (6.5.20.0), when a user tries to search for an Adaptive Form from the side panel, the search fails. (FORMS-14117)

When a user edits a form created in German and translated into English, it results in inconsistent language displays between the ‘Preview’ and ‘Edit’ modes. This causes RadioButton and Checkbox components to display in English during ‘Edit’ mode while correctly appearing in German during ‘Preview’ mode. (FORMS-13910)

Process purge process tool fails with the error NoClassDefFoundError: org/omg/CORBA/UserException. (FORMS-13751)

When a user tries to embed an Adaptive Form (AF) inside a webpage, either external or on AEM Sites, using an embed container, the Adaptive Form guide container introduces an ARIA LABEL. The label has the role=“main” for the embedded form. According to ARIA guidelines, there should only be one role=“main” per page. Therefore, when a user adds another role=“main” for their page’s main content, it is flagged as an accessibility issue. (FORMS-13538)

On AEM Forms Service Pack 19 (6.5.19.0), when using the drop-down in an Adaptive Form, the drop-downs with placeholder text retain the value of id="emptyValue". As such, if a form has multiple drop-down components, each has id="emptyValue" that is not correct as per the ARIA guidelines. (FORMS-13370).

When a user reloads an Interactive Communication after the data is submitted through XML, a blank space between the text block occurs in the generated PDF. (FORMS-13481)

Missing IPH for “Prepare for DSC Deployment step” screen while running ConfigurationManager. (FORMS-10699)

When a user adds a new dictionary to translate a form with existing dictionaries, the old translations become invalidated. The following issues arise: (FORMS-13576)

• Some fields fail to populate the translated data.
• Some fields are not translated into the new language, even though the data is successfully saved to the dictionary.

When a user adds a new table to an existing form using AEM Forms Designer on the environment AEM Forms Service Pack 19 (6.5.19.0), it crashes. (LC-3921978)

When a user renders an Adaptive Form on �����Գܳ�® environment, an extra space between the field components occurs. (LC-3921957)

When a user converts an XTG file to PostScript format using the Output Service, it fails with the error: (AEM_OUT_001_003:Unexpected Exception: PAExecute Failure: XFA_RENDER_FAILURE). (LC-3921720)

To resolve the issue:
Check if the data contains special characters like Zero Width Space (0x200b). If yes, then use the flag by adding the tag <behaviorOverride>patch-LC3921720:1</behaviorOverride> in the XCI file as given in custom_xfa.xci file.

When using AEM Forms Service Pack 18 (6.5.18.0) within a �����Գܳ�® environment, XMLFM crashes on CPUs not supporting AVX / AVX2 instruction featuring AMD® processors. (LC-3921718)

When a user creates a PDF from XDP using the Forms Output service, the user is not able to configure “settings” on “individual text blocks” in the XDP to control what is “artifacted.” (LC-3921954)

AEM 6.5 Service Pack 15 is producing continuous error logs with significant entries. The following issues were reported:

• 404 INFO error for missing resource at path /libs/granite/ui/content/shell/start.html
• Error log entry for an uncaught SlingException due to NullPointerException at CampaignsDataSourceServlet.java:147

Error logs should not be filled with frequent and voluminous error entries, and the AEM instance should function without issues related to missing resources or exceptions. (CQ-4357064)

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. 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 �۶���Ƶ 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 “�۶���Ƶ Experience Manager,” Target creates several offers with type “HTML”/source “�۶���Ƶ 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 declare their correct variables. Otherwise, they do not get run, and end up throwing a runtime error.

Installing tagging related out-of-the-box content by way of an official update package resets the languages property of the /content/cq:tags node to default. This action is true for Service Packs, Security Service Packs, Extended Feature Packs, Cumulative Feature Packs, patches, and so on. Therefore, it is necessary to add it from the properties before installation.

After installing AEM Forms JEE Service Pack 21 (6.5.21.0), if you find duplicate entries of Geode jars (geode-*-1.15.1.jar and geode-*-1.15.1.2.jar) under the <AEM_Forms_Installation>/lib/caching/lib folder (FORMS-14926), perform the following steps to resolve the issue:

1. Stop the locators, if they are running.
2. Stop the AEM Server.
3. Go to the <AEM_Forms_Installation>/lib/caching/lib.
4. Remove all the Geode patch files except geode-*-1.15.1.2.jar. Confirm that only the Geode jars with version 1.15.1.2 are present.
5. Open the command prompt in administrator mode.
6. Install the Geode patch using the geode-*-1.15.1.2.jar file.

If a user tries to preview a draft letter with saved XML data, it gets stuck in Loading state for some specific letters. To download and install the hotfix, refer to the �۶���Ƶ Experience Manager Forms Hotfixes article. (FORMS-14521)

After upgrading to AEM Forms Service Pack 6.5.21.0, the PaperCapture service fails to perform OCR (Optical Character Recognition) operations on PDFs. The service does not generate output in the form of a PDF or a log file. To download and install the hotfix, refer to the �۶���Ƶ Experience Manager Forms Hotfixes article. (CQDOC-21680)

When users update from AEM 6.5 Forms Service Pack 18 (6.5.18.0) or AEM 6.5 Forms Service Pack 19 (6.5.19.0) to AEM 6.5 Forms Service Pack 20 (6.5.20.0) or AEM 6.5 Forms Service Pack 21 (6.5.21.0), users encounter a JSP compilation error, which prevents them from opening or creating adaptive forms and also causes errors with other AEM interfaces like the page editor, AEM Forms UI, AEM Workflow editor, and AEM System Overview UI. (FORMS-15256)

If you face such an issue, perform the following steps to resolve it:

1. Navigate to the directory /libs/fd/aemforms/install/ in CRXDE.
2. Delete the bundle with the name com.adobe.granite.ui.commons-5.10.26.jar.
3. Restart your AEM server.

When a user updates to AEM Forms Service Pack 20 (6.5.20.0) installed with the Forms Add-On, configurations using the legacy cloud service for �۶���Ƶ Analytics with user credential-based authentication, fail to function correctly, causing the failure of analytics rules to execute. To download and install the hotfix, refer to the �۶���Ƶ Experience Manager Forms Hotfixes article. (FORMS-15428)

When a user updates to AEM Forms Service Pack 20 (6.5.20.0) on JEE server and generates PDFs using output services, the PDFs render with accessibility issues. To download and install the hotfix, refer to the �۶���Ƶ Experience Manager Forms Hotfixes article. (LC-3922112)

When a user generates Tagged PDFs using output service on JEE, it shows “Inappropriate structure warning”. To download and install the hotfix, refer to the �۶���Ƶ Experience Manager Forms Hotfixes article. (LC-3922038)

When a form is submitted on AEM Forms JEE, the instances of a repeating XML element are removed from the data. To download and install the hotfix, refer to the �۶���Ƶ Experience Manager Forms Hotfixes article. (LC-3922017)

When a user on a Linux environment renders an adaptive form (on JEE) in HTML, it fails to render properly. To download and install the hotfix, refer to the �۶���Ƶ Experience Manager Forms Hotfixes article. (LC-3921957)

When a user converts an XTG file to PostScript format using the Output Service on AEM Forms JEE, it fails with the error: AEM_OUT_001_003: Unexpected Exception: PAExecute Failure: XFA_RENDER_FAILURE. To download and install the hotfix, refer to the �۶���Ƶ Experience Manager Forms Hotfixes article. (LC-3921720)

After upgrading to AEM Forms Service Pack 18 (6.5.18.0) on JEE server, when a user submits a form, it fails to render HTML5 or PDF Forms and XMLFM crashes. To download and install the hotfix, refer to the �۶���Ƶ Experience Manager Forms Hotfixes article. (LC-3921718)

In the Print Preview of the Interactive Communications Agent UI, the currency symbol (such as the dollar sign $) is inconsistently displayed for all field values. It appears for values up to 999 but is missing for values of 1000 and above. (FORMS-16557)

Any modifications to nested layout fragments’ XDP in an Interactive Communication are not reflected in the IC editor. (FORMS-16575)

In the Print Preview of the Interactive Communications Agent UI, some calculated values are not displayed correctly. (FORMS-16603)

When the letter is viewed in Print Preview, the content changes. Some spaces disappear, and certain letters are replaced with ‘x’. (FORMS-15681)