蜜豆视频

Transaction Reporting in AEM Forms on JEE: Transaction reporting capability has been introduced for AEM Forms on JEE, enabling comprehensive recording of document transactions such as Conversions, Renditions, and Submissions. This enhancement boosts efficiency and facilitates better record-keeping. The feature is disabled by default. You can enable it from the Admin UI.

Enhanced Security with ECDSA Support: AEM Forms now offer robust support for the Elliptic Curve Digital Signature Algorithm (ECDSA) across both JEE and OSGi stacks. Users can now Sign, Certify, and Verify PDF documents with heightened security. Supported EC curve algorithms include:

• ECDSA elliptic curve P256 with SHA256 digest algorithm
• ECDSA elliptic curve P384 with SHA384 digest algorithm
• ECDSA elliptic curve P512 with SHA512 digest algorithm

Seamless Compatibility with Windows 11 for Forms Designer: AEM Forms Designer now supports Windows 11, ensuring smooth installation and operation. Users can confidently upgrade to Windows 11 without the hassle of reinstalling Forms Designer or worrying about compatibility issues, ensuring uninterrupted workflow.

Enhanced Accessibility with Custom 鈥淐aption鈥� Role in AEM Forms Designer: AEM Forms Designer now includes a custom accessibility role called 鈥淐aption,鈥� empowering users to create XDPs with personalized captioning elements. This feature enhances accessibility by letting users integrate custom captions into their document designs so they can improve inclusivity and user experience.

Effective May 1, 2024, 蜜豆视频 Dynamic Media is ending 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

See also Dynamic Media Limitations.

When an asset is uploaded to AEM, the Update_asset workflow is triggered. However, the workflow never finishes. The workflow only completes up to the product upload step. The next step is the Scene7 batch upload, but that process is not getting pulled into AEM. (ASSETS-30443)

Need a better way to handle non-Dynamic Media videos gracefully in the Dynamic Media component. This issue was giving an exception instantiating dynamicmedia_sly.js. (ASSETS-31301)

Preview works for all assets, adaptive video sets, and videos. However, it throws a 403 error for .m3u8 files (which, incidentally, still work by way of public links). (ASSETS-31882)

The scene7SmartCropProcessingStatus status corrected. Smart Crop video metadata used to show failure even when it was successful. (ASSETS-31255)

When a user tries to integrate AEM Forms to a mailing platform with an AEM published URL, AEM Forms does not add method=post while rendering the page. This issue occurs even though POST is set in the submit action with the URL. It causes the mailing platform to not recognize this as a form. (FORMS-12614)

When a user selects the date field having a display pattern on AEM Form Service Pack 6.5.18.0, the user is not able to select the current date using the keyboard. (FORMS-12736)

On AEM Forms Service Pack 6.5.17.0 and Service Pack 6.5.18.0, when a user switches between months in the calendar widget, the date picker component shows an extra row. (FORMS-11869)

When a user clicks an image using the 鈥淭ake a photo鈥� in the Attachment component on an iOS device, all images are added to the folder with the same name. (FORMS-12224)

When a user updates an existing option in a Radio button group, incorrect translation values are published. (FORMS-12575)

When a user adds characters to an Adaptive Form on an Android鈩� device, the user can type more than the defined maximum number of characters in the Text field on focus out, on Android鈩� devices. However, it works when a user selects the HTML5 input type. (FORMS-12748)

Due to matching labels Arial庐 labelledby and Arial庐 label, the screen readers are not able to distinguish between these two. To resolve the issue 鈥� the label 鈥渁ria-labelledby鈥� is replaced with 鈥渁ria-describedby鈥� for the form fields. (FORMS-12436)

An author uses the 鈥淎daptive Forms - Embed (v2)鈥� component to embed an Adaptive Form in their Sites page. When the embedded form contains a CAPTCHA component on it (CAPTCHA Service > reCAPTCHA, Settings > reCAPTCHA-v2), the site page does not render. This occurs when the user tries to view the Site Page using 鈥淰iew as Published鈥� on the author instance. The following error is shown as (FORMS-11859):
Failed to construct 'URL': Invalid base URL at Object.renderRecaptcha

When a user tries to select the date using the date picker component, the value is not updated and shows NULL. (FORMS-12742, FORMS-12736)

When a user upgrades to AEM Form Service Pack 6.5.19.0, after updating a new language to the existing dictionary it does not get merged with the 鈥済uideContainer鈥� rows to add a locale to a form. (FORMS-12947)

On AEM Forms Service Pack 6.5.19.0, the invoked webservice operation on Java鈩� 11 fails with the error (FORMS-12329):
java.lang.NoClassDefFoundError message:sun/misc/BASE64Decoder

When a user invokes 鈥渞eceive鈥� operation for 鈥淓mailService鈥� on AEM Forms Service Pack 6.5.18.0, an exception is thrown (FORMS-12050):
java.util.ServiceConfigurationError: javax.mail.Provider: Provider com.sun.mail.imap.IMAPProvider not a subtype

When FIPS mode is enabled on AEM Forms Service Pack 6.5.18.0, creating a user under default DOM fails with the error (FORMS-11857):
com.adobe.idp.cx.a: error seeding random number generator

When a user selects fonts in ADMINUI under the path Home>Services>PDF Generator>蜜豆视频 PDF Settings, it does not get selected. Moreover, in a standard or personalized profile, the list box of Fonts available is empty. As such, it is not possible to personalize the sublist of Always embed or Never embed. The user is unable to configure the font for their PDFs with PDF Generator. The logs do not show any relevant error messages. (FORMS-12095)

On AEM Forms Service Pack 6.5.18.0, the user is unable to create security settings, it shows no error or server logs, but a pop-up error message is shown on the screen. (FORMS-12212)

When a user on AEM Forms Service Pack 6.5.18.0 submits an Adaptive Form on the JEE workflow, the attachment in the Adaptive Form is not sent to the JEE process which causes application failure. (FORMS-12232, FORMS-12228)

When a user converts PDF to PDF/A-2b or PDF/A-3B, it fails to convert, the error is shown as: (FORMS-12790)

OCCD contains Order key that does not reference all layers.
-> Optional content configuration dictionary has no Name entry.
-> Font not embedded (and text rendering mode not 3).
obj(65, 0)
Page: 1
-> Font not embedded (and text rendering mode not 3).
obj(67, 0)
Page: 1
-> PDF/A entry missing.
-> PDF/A entry missing.

On AEM Forms 6.5.18.0, 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 鈥淢icrosoft庐 SharePoint鈥� while running the configuration manager on AEM Forms 6.5.19.1 with JBoss庐 Turnkey setup, the LiveCycle JBoss庐 EAR installation fails, and it shows the following error: (FORMS-12463)

Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEE0031: Unable to process modules in application.xml for EAR ["/C:/AEM/jboss/bin/content/ adobe-livecycle-jboss.ear "], module file adobe-connectorformssharepoint-config-ejb.jar not found.

When a user creates a Document Fragment using the form data model in AEM Forms Service Pack 6.5.19.0, the variable names appear undefined on the side panel. However, the variable names are shown when dropped onto the form panel or when they are clicked. (FORMS-13238)

When a user upgrades to AEM Forms Service Pack 6.5.18.0, due to missing exception handling, XDPs passed through the output service with the tagged PDF option-enabled fail. (LC-3921757)

When a user generates a PDF using AEM Forms Designer, heading levels are tagged in the accessibility tree along with the graphical element, for example, a rectangle box. (LC-3921687)

On AEM Forms Designer installed via Workbench, the version information is not explicit in the Control Panel/Programs/Programs and Features. (LC-3921976)

When a user creates an XDP on AEM Forms Designer, On PDF output, the Button Form tag is not nested in the parent paragraph tag (p-tag). (LC-3921719)

When a user creates an XDP on AEM Forms Designer, On PDF output when a user navigates through the form tags, the background object is also tagged. (LC-3921687)

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

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 鈥淓xperience Fragment鈥�/source 鈥溍鄱故悠� Experience Manager,鈥� Target creates several offers with type 鈥淗TML鈥�/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 correctly declare their variables, otherwise they do not get run, instead throwing a runtime error.

Installing tagging related out-of-the-box content via an official update package (including Service Packs, Security Service Packs, Extended Feature Packs, Cumulative Feature Packs, patches and the like), resets the languages property of the /content/cq:tags node to default. Therefore, it is necessary to add it from the properties before installation.

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)

Form submissions are failing when trying to use the DOR (Document of Record) service in the backend. The error message encountered is: 鈥淪ubmit Action couldn鈥檛 complete because Form Resource isn鈥檛 correctly assigned.鈥� (FORMS-13798)

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)

On installing AEM 6.5 Forms Service Pack 20 package (AEM Forms add-on package for SP20),the AEM Sites user interface (UI) exhibits significant performance degradation. (FORMS-13791)

The prefill service fails with a null pointer exception in Interactive Communications. (CQDOC-21355)

Adaptive Forms let you use custom functions with ECMAScript version 5 or earlier. When a custom function uses ECMAScript version 6 or later, like 鈥榣et鈥�, 鈥榗onst鈥�, or arrow functions, the rule editor might not open properly.

Users are unable to create a Correspondence Management letter. When a user creates a letter, an error with description 鈥�Object Object鈥� appears and the letter is not created. Thumbnails for layouts also fail to load on the letter creation screen. You can install the latest AEM 6.5 Form Service Pack 20 (6.5.20.0) to resolve the issue. (FORMS-13496)

The interactive communications service creates the PDF document, but the user鈥檚 data is not automatically populated in the form fields. The prefill service is not working as expected. You can install the latest AEM 6.5 Form Service Pack 20 (6.5.20.0) to resolve the issue. (FORMS-13413, FORMS-13493)

The Review and Correct (RnC) editor of automated forms conversion service fails to load. You can install the latest AEM 6.5 Form Service Pack 20 (6.5.20.0) to resolve the issue. (FORMS-13491)

After updating 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), users encounter a JSP compilation error. They cannot open or create adaptive forms and they鈥檙e running into errors with other AEM interfaces like the page editor, AEM Forms UI, and AEM Workflow editor. You can install the latest AEM 6.5 Form Service Pack 20 (6.5.20.0) to resolve the issue. (FORMS-13492)

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)

Form submissions are failing when trying to use the DOR (Document of Record) service in the backend. The error message encountered is: 鈥淪ubmit Action couldn鈥檛 complete because Form Resource isn鈥檛 correctly assigned.鈥� (FORMS-13798)

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, and AEM Workflow editor. (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.

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 鈥榵鈥�. (FORMS-15681)