Commerce
- The creation of a store page failed, stopping the overall catalog rollout process. (CQ-4347181)
Forms
Key Features
- AEM Forms Designer is now available in Spanish locale. (LC-3920051)
- You can now use OAuth2 to authenticate with Microsoft® Office 365 mail server protocols (SMTP and IMAP). (NPR-35177)
- You can set Revalidate on server property to true to identify the hidden fields for exclusion from a Document of Record on server-side. (NPR-38149)
- AEM Forms Designer requires 32-bit version of Visual C++ 2019 Redistributable (x86). (NPR-36690)
Fixes
-
When the data-disabled property of an Adaptive Form is toggled, the appearance of radio button and checkbox groups does not change. (NPR-39368)
-
When an Adaptive Form is translated, some of the translations are missed and not shown correctly. (NPR-39367)
-
When the property of a page is set to hidden, the page is not removed from the formset. (NPR-39325)
-
In a Document of Record, the dynamic footnote section at the end of the page is not present. (NPR-39322)
-
When a Document of Record is generated for an Adaptive Form, only the vertical alignment is allowed for radio buttons and checkboxes. The user cannot set the horizontal alignment for radio buttons and checkboxes. (NPR-39321)
-
After deploying Correspondence Management, if multiple users try to access a form, org.apache.sling.i18n.impl.JcrResourceBundle.loadPotentialLanguageRoots becomes bottleneck and a majority of the threads gets struck. Various forms page requests often took more than 1 minute to load each even when the server has a very low load. (NPR-39176, CQ-4347710)
-
In an Adaptive Form, when you use a Rich Text field in a lazy loaded Adaptive Form fragment, some of the following errors are experienced:
- You cannot edit the content or append anything to the Rich Text field.
- The display pattern applied to the rich text is not honored.
- The error message for minimum field length is not displayed on submitting the form.
- The content of this rich-text field is included several times in the produced submit-XML. (NPR-39168)
-
When the Date picker option is used in an Adaptive Form, it fails to convert the value into the correct format. (NPR-39156)
-
While previewing an Adaptive Form as an HTML form, it is not rendered properly, as some of the sub forms overlap with the parent form. (NPR-39046)
-
If the panel has hidden table and adaptive form is rendered using tabular view, fields on the first tab are not displayed correctly. (NPR-39025)
-
The
Body
tag is missing for the out-of-the-box template. (NPR–39022) -
The Document of Record is not generated in the language of the Adaptive Form. It is always generated in English language. (NPR-39020)
-
When an Adaptive Form has multiple panels and some of the panels use the out-of-the-box File Attachment component, the
Error occurred while draft saving
error occurs . (NPR-38978) -
When
=
sign is used in the check box, drop-down list, or radio button fields of an Adaptive Form and the Document of Record is generated, then=
sign is not visible in the generated Document of Record.(NPR-38859) -
There is multifold increase in the number of the Notice Batch Processing errors after 6.5.11.0 service pack upgrade. (NPR-39636)
-
When you do not provide test data, Correspondence Management letters fail to load in the Agent UI. (CQ-4348702)
-
When user applies the AEM Forms Service Pack 14 (SP14) form AEM Forms deployed using IBM® WebSphere®, the bootstrapping fails while initializing a database and the
java.lang.NoClassDefFoundError:org/apache/log4j/Logger
error occurs.(NPR-39414) -
On an AEM Form on OSGi server, when you use Document Service API to certify PDF, it fails with error: com.adobe.fd.signatures.truststore.errors.exception.CredentialRetrievalException: AEM-DSS-311-003. (NPR-38855)
-
When user tries to use the wrapper service for rendering letters with AEM 6.3 Forms, the
java.lang.reflect.UndeclaredThrowableException
error occurs. (CQ-4347259) -
When an XDP is rendered as HTML5 form, the content of the master page is rendered first regardless of the placement of the objects in an Adaptive Form. (CQ-4345218)
-
The configuration of the application at the destination server changes to the settings defined at the source server even though the Overwrite configuration when import is complete option is not checked at the time of importing the application. (NPR-39044)
-
When a user tries to update connector configuration using Configuration Manager, it fails.(CQ-4347077)
-
When user tries to run an AEM Form on JEE patch after changing the default password of the administrator user, an exception
com.adobe.livecycle.lcm.core.LCMException[ALC-LCM-200-003]: Failed to whitelist the classes
occurs. (CQ-4348277) -
In AEM Designer, form fields without captions are placed in table cells including checkboxes.(LC-3920410)
-
When the user tries to open Help in the AEM Forms Designer, it is not displayed properly. (CQ-4341996)
-
Adaptive Forms with multiple locales are slow to load. (NPR-39176)
Sites
- Experience Manager Sites Launches console was coming up blank. (NPR-39188)
- References were not adjusted when the page that had the reference also needed to be activated during the page move. (NPR-39061)
- When a Layout container is unhidden using parent container, layout changes are not getting applied to all components inside the nested container. (NPR-39041)
- Content now no longer overlaps with other content at 320-pixel width. (SITES-8885)
- Added focus after closing a dialog box. (SITES-8885)
Accessibility
- The Annotation button is missing its accessibility name. (SITES-2892)
- The state of an ACTIVE user interface component (Cut, Copy, Paste, Insert Components, Group, and so on) does not have at least a three to one luminosity contrast ratio with either the inner or outer adjacent background. (SITES-8889, SITES-8756, SITES-8885)
- Status message not automatically announced. (SITES-8889, SITES-8756, SITES-8885)
- Text content lacks 4.5:1 contrast ratio. (SITES-8756, SITES-8885)
- Link or button text lacks 4.5:1 contrast ratio on hover or focus. (SITES-8756, SITES-8885)
Content Fragments
- GraphQL raises an exception. For example, you cannot get variation tags from a content fragment. There is no variation with the name ‘electric’. This issue is due to calling
getVariationTags
for a non-existing variation which raises an exception. (SITES-8898) - Sorting title orders in List view, both ascending and descending, how the titles with the order A, C, B. (SITES-7585)
- Added tagging support for content fragment variations. (SITES-8168)
- Identified and removed Odin-specific code from Experience Manager 6.5 that was unnecessary. (SITES-3574)
- When publishing a language copy fragment from the Content Fragment Editor user interface, the associated references were getting published under the English folder. (NPR-39182)
- Date fields are getting pre-populated with a date. (NPR-39124)
- Tags disappeared the second time that you select the radio button option. (NPR-39071)
Fluid XP
- Enable ES6 compilation support for the client library
/libs/cq/gui/components/siteadmin/admin/restoretree/clientlibs/restoretree.js
. (NPR-39067) - The Multifield in a Content Fragment Model cannot be emptied and saved because validation occurs even if Required is not selected. (NPR-39063)
- In either Copy or Livecopy tasks, the
cq:targetMetadata
information was incorrectly being duplicated. This functionality caused two or more Experience Fragments in Experience Manager to point to the same offer exported in target. (NPR-38970) - Following a Restore Tree action, the message
Un-publication pending. #0 in the queue
appears in the user interface for a page that was never published in the first place. (NPR-38847)
Page Editor
- Undo did not delete the last change made to text that was added into the component. Instead, when the page was refreshed, the entire component got deleted. (SITES-8597)
- Upgrading
jquery-ui
to the latest version resulted in the Page Editor not working correctly. (NPR-38596) - Content now no longer overlaps with other content at 320-pixel width. (SITES-8756)
- added focus after closing the Dialog (SITES-8756)
Sling
Repoinit
did not support the creation or management of groups with whitespace in the principal name because the group name was treated as a string, and it did not support being quoted. (SLING-10952)- Logs are inadvertently filled with error messages and exceptions. (NPR-39024)