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

Authors can add, move, and remove components using only the keyboard. The drag-and-drop interaction required a pointer, so it failed the WCAG 2.1.1 Keyboard criterion. The editor now provides the Insert component pop-up, Cut and Paste, and Delete as keyboard-operable equivalents. (SITES-25359)

Authors can now see the active Format (“T”) button in the Text component inline menu. After authors applied bold or italic formatting, the button icon stayed dark against a dark-grey background and missed the WCAG 2.1 AA minimum contrast ratio of 4.5:1. The updated CSS lightens the icon, which restores the contrast that earlier service packs provided. (SITES-51864)

The Assets tab in the Page Editor now displays a translated string in the Select Components drop-down after you choose Paragraphs from the Images dropdown. Previously, the string “OTHER” appeared in English because the localization resources lacked it. The updated dictionary supplies the translation in all locales. (SITES-24525)

The ContextHub iframe in the Page Editor now has a descriptive title attribute. Previously, the contexthub-ui-iframe element had no title, so screen reader users failed to identify it when focus moved to it. The title now appears on every Editor page and view, including Canvas, Side Rail, and Layout Preview. (SITES-24650)

The Filters button in the Sites console Filter Rail doesn’t add visible labels above the Saved Searches and Select Search Directory fields. An audit reported that labels appeared when focus left the button, when a key was pressed, or when the button was clicked. Testing failed to reproduce the behavior, so no change was necessary. (SITES-24706)

Links in the Sites console App Navigation now stand out more clearly. The link text met the 4.5:1 contrast ratio, but the thin font weight and small size made the links hard to see. A greater font weight and larger size make the text easier to read for users with visual impairments. (SITES-24723)

Screen readers no longer announce “blank” before the tooltip content in the User Preferences modal. Previously, the info icon used role="tooltip" with an aria-labelledby reference, so NVDA read an empty label first. The icon now uses role="button" and an aria-label of “information,” and the change applies to the Coral form components that share the pattern. (SITES-24732)

The Delete button in the Delete modal now meets the WCAG 1.4.3 contrast requirement of 4.5:1. Previously, white text on a red background gave a ratio of 3.9:1 after authors selected an item and clicked Delete in the Action Toolbar. The darker button color makes the label readable for authors with visual impairments. (SITES-24772)

The References heading in the Sites console References rail now uses a heading element instead of a div. Previously, screen readers failed to announce the text as a heading, so users failed to navigate by headings. The heading also appears at the top of the initial References view. (SITES-24967)

The focus indicator for accordion buttons in the Sites console Filter Rail now meets the WCAG 1.4.11 contrast requirement of 3:1. Previously, the blue indicator showed a ratio of 2.3:1 against the background, which made the Tags accordion button hard to find for keyboard users. The updated color gives keyboard users a clear focus cue. (SITES-24986)

The focus indicator for radio buttons in the Sites console Filter Rail now meets the WCAG 1.4.11 contrast requirement of 3:1. Previously, the light blue indicator showed a ratio of 1.7:1 against the background. Keyboard users can now track their position in the Modified date accordion. (SITES-24987)

The Select button beside the Path and Tags fields in the Page Editor side rail no longer uses a checkbox icon. Previously, the icon suggested a toggle, but activating the button opened a modal that contains the Tree Directory. The Select button now communicates its function correctly, and the same applies to the Image and Teaser modals. (SITES-25210)

Screen readers now skip the thumbnail images of assets in the Page Editor side rail. Previously, each image carried alt text that duplicated the visible asset name, so users heard the same text twice. An empty alt attribute marks the image as decorative and keeps the name in the card title. (SITES-25213)

Screen readers recognize the side rail Components list as a list. An audit reported the items as unrelated elements, but testing confirmed the markup uses a list element and list items. No code change was necessary. (SITES-25214)

The info icons for components in the Page Editor side rail are larger and easier to see. Previously, the icons used the extra small size of about 12 px, which users with visual impairments found hard to see. The icons now use the medium size.(SITES-25217)

The focus indicator on the Swatch button in the Annotation modal now stands out from the button. Previously, the indicator matched the swatch color. This made it hard for keyboard users to see which button had focus. An offset gives the indicator enough contrast against the background and keeps it clearly visible. (SITES-25253)

The Date field in the Timewarp modal no longer carries aria-haspopup="dialog". Previously, screen readers announced that the field opens a dialog box, even though it doesn’t. Removing the attribute gives screen reader users accurate information. (SITES-25263)

Text labels in the Demographics toolbar, such as “Recommended,” now meet the WCAG 1.4.3 contrast requirement of 4.5:1. Previously, grey text on a dark grey background gave a ratio of 2.8:1 in Preview mode. Darker or lighter text, depending on the background, makes every label readable. (SITES-25307)

The focus indicator on the Commerce, Persona, and Device buttons in the Demographics toolbar now meets the WCAG 1.4.11 contrast requirement of 3:1. Previously, the indicator showed a ratio of 1.9:1 against the toolbar background. Keyboard users can now track their position. (SITES-25308)

Text that authors type in the Demographics toolbar text fields now meets the WCAG 1.4.3 contrast requirement of 4.5:1. Previously, white text on a grey background produced a ratio of 2.9:1 in fields, such as the Profile drop-down displayName field in Preview mode. The updated colors make typed values readable for authors with visual impairments. (SITES-25318)

Screen readers now read the description tooltip when focus reaches checkboxes in the Teaser, Image, and Carousel dialog boxes. Previously, the text lacked programmatic association with the checkbox, so users failed to hear the instruction. An aria-describedby attribute now links each checkbox to its description. (SITES-25364)

Screen readers now announce which Paragraph formats button is active in the Rich Text Editor. Previously, selecting an option from the list gave assistive technology no indication of the current choice. The active button now carries aria-current="true", and the active Hyperlink Target option carries aria-selected="true". (SITES-25367)

The Sort buttons in the table header of the Sites console List View now meet the WCAG 1.4.11 contrast requirement of 3:1. Previously, the light grey icons showed a ratio of 1.5:1 against the header background. The darker icon color makes the buttons visible to authors with visual impairments. (SITES-25372)

The Assets tab in the Page Editor side rail no longer reloads when focus moves to the Filter field. Previously, tabbing into the empty field triggered a reload, and screen readers announced a loading message each time. The tab now reloads only after you change the filter value and press Enter. (SITES-25377)

The selected swatch icon in the Annotation modal now meets the WCAG 1.4.11 contrast requirement of 3:1. Previously, the white check mark showed a ratio as low as 1.58:1 against yellow, orange, and green swatches. The updated icon gives authors with visual impairments a clear indicator. (SITES-25523)

The Components list in the Page Editor side panel no longer takes keyboard focus. Keyboard users select and move components with the controls in the content window, so the side panel list repeated the function. A note under the component filter informs keyboard users where to find the controls. (SITES-40752)

The Edit Content Fragment button appears immediately for each multifield reference in the Content Fragment editor. Previously, the button stayed hidden until authors saved the parent fragment, and it did nothing after they opened the Path Browser. The editor now builds the action list on first render, so authors open referenced fragments without extra steps. (SITES-43733)

Chinese, Japanese, and Korean characters no longer display in italics in the Create Content Fragment dialog box placeholder. Previously, the italic style applied to CJK characters under Assets > Files, which made the text hard to read. The updated styles skip italics for CJK languages. (SITES-43548)

The Content Fragment editor validates fields correctly after the Granite UI update. A recent Granite UI change caused a regression, so the editor client libraries no longer matched the new validation behavior. The adapted libraries and tests resolve the mismatch. (SITES-46650)

GraphQL queries on content fragments now recognize RemoteRef references to Dynamic Media with OpenAPI Assets. Previously, queries failed with a “Persisted Query Validation Error” and returned no asset data when AEM 6.5 Sites consumed AEM as a Cloud Service Assets. Responses now include the repository ID and asset ID, so clients can build delivery URLs. (SITES-48507)

Publish instances remain responsive during heavy GraphQL traffic. Lock contention in GraphQLServiceImpl delayed request-processing threads at the schema methods, which slowed requests and required restarts. Improved synchronization resolves the performance constraint and maintains the availability of sites and mobile apps. (SITES-48699)

The message on the GraphQL Endpoints page remains localized after you reload the page. Previously, the “No endpoints were found” message appeared in your language when you created and deleted endpoints, but it reverted to English after a reload. The page now loads the translated string on every visit. (SITES-43586)

Thumbnails for content fragment models display in Tools > General > Content Fragment Models when the configuration name contains localized characters, such as “español テスト.” Previously, the uploaded thumbnail didn’t appear because the characters caused an error in the path. The updated handling encodes the name correctly. (SITES-39242)

The Field Label string on the Content Fragment Model Editor canvas now appears in the user’s language. Previously, the label stayed in English after authors dragged a component onto the canvas, and it translated only after they saved and reopened the model. The label now translates immediately, matching the Properties panel. (SITES-45383)

Scheduled page activation through On-Off-Time now runs only when needed. OnOffTriggerProcessor previously triggered replication and cache invalidation too often, which forced authors to republish content manually. The backported fix eliminates the unnecessary processing and restores reliable scheduled publishing. (SITES-48483)

File upload works for remote assets from Next-gen Asset Management in a multifield. Previously, the upload failed when authors picked a remote asset for a field inside a multifield. The Core Components update restores the upload flow, so the field accepts the asset. (SITES-44266)

The Remote Asset Picker keeps each multifield item’s image separate. Previously, selecting an image in one multifield item applied it to every other item, and the remote asset reference didn’t save. Each item now holds its own selection, and the reference persists after you save the dialog box. (SITES-42376)

This release includes backported fixes for Commerce, Core Components, Foundation Components (Legacy), Launches, and MSM Live Copies. The fixes address security vulnerabilities, cross-site scripting (XSS) violations, file upload behavior, and Live Copy behavior. The backports bring AEM 6.5 and AEM 6.5 LTS in line with fixes that shipped earlier in AEM as a Cloud Service. (SITES-43738)

Strings on the Health Reports pages under Tools > Operations now display in the user’s language. Previously, messages for Resource Search Path, Maintenance, Replication Queue, Log Errors, Active Bundles, and Request Performance remained in English. Updated i18n resources supply the translations, and a fallback file keeps the strings available. (NPR-44279)

The error message “Settings to ‘JSON Path’ are ignored when the ‘Add Manually’ option is checked” now displays in the user’s language in the Tools > Assets > Metadata Schemas console. Previously, the message remained in English after authors added a dropdown element, selected Add through JSON path, and switched to Add Manually. The updated resources provide the translations. (ASSETS-31575)

The “promoted” string in Assets > Manage tags now displays in the user’s language. Previously, the string remained in English when you hovered over a smart tag after you selected Promote. The updated resources supply the translation in all locales. (ASSETS-36070)

The Add button label no longer overlaps the button in Folder Properties > Asset Contribution. Previously, the text collided with the button in the German, Italian, and Brazilian Portuguese interfaces after you created a folder with the “Asset contribution” setting. Updated styles give the longer translated labels enough room. (ASSETS-36746)

Column titles in the Assets List View now display horizontally in the Japanese interface. Previously, the titles appeared vertically in List View under Assets > Files, and in the card view of the content fragment editor. The updated cq-dam-content package corrects the text direction.(ASSETS-43105)

The publication status “Scheduled for later” in the Assets column view now displays in the user’s language. Previously, the string remained in English after authors selected an asset, chose Manage Publication, selected the Later option, added a date, and published. The updated cq-dam-content package supplies the translations in all locales. (ASSETS-43307)

Strings in the Smart Tags Configuration tab now display in full for French and Brazilian Portuguese. Previously, the text was cut off after you clicked Create under Tools > Cloud Services > Smart Tag. To read the text without a tooltip, use the CSS update that provides enough space. (ASSETS-68045)

The “Multi Path Value Property Predicate” string in the Assets admin search rail now displays in the user’s language. Previously, the string remained in English when administrators edited the search form under Tools > General > Search forms and dragged the predicate onto the form. The updated cq-dam-content package supplies the translations.(CQ-4336103)

Aria labels in the Projects view now display in the user’s language. Previously, the Actions button on each project tile had no accessible name, and the Configure Tile action used a hard-coded English label while sibling labels were localized. The updated tile script supplies a localized label for both actions. (CQ-4352359)

Smart Collections with Chinese, Japanese, or Korean characters in the name now save correctly. Previously, saving a collection from Assets > Files > Filter failed with “Save Search Failed - Invalid request, duplicate collection not allowed” when the name contained CJK characters. The duplicate check now compares the collection titles rather than the node names, so collections with different CJK titles no longer conflict. (GRANITE-62592)

The Country/Region dropdown in Security > Users > Create now sorts names alphabetically in the user’s language. Previously, the list sorted names in English order while it displayed localized names, so countries appeared out of order in locales such as Japanese. The updated com.adobe.granite.security.content bundle sorts with locale-aware rules. (GRANITE-67789)

The disclaimer on the AuditLog Maintenance Task in Tools > Operations > Maintenance now displays in the user’s language. Previously, the warning about audit log purging and compliance requirements remained in English after users clicked the disclaimer icon in the Weekly Maintenance window. The updated resources supply the translation in all locales. (NPR-44189)

Permission names in Security > Permissions > Audit View now display in the user’s language. Previously, the names appeared in English because the translations were missing. The updated com.adobe.granite.platform.i18n bundle supplies them. (NPR-44477)

The Check Health dialog box in Security > Adobe IMS Configurations now displays in the user’s language. Previously, the dialog box showed English strings in localized interfaces because the translations were missing. The updated com.adobe.granite.platform.i18n bundle supplies them. (NPR-44479)

Strings in the User Sync Diagnostics tool under Tools > Operations > Diagnosis now display in the user’s language. Previously, the tool showed English text in localized interfaces. The updated com.adobe.granite.platform.i18n bundle supplies the translations. (NPR-44481)

Configuration flows now show user-friendly error messages in the user’s language. Previously, failures in AEM configuration pages produced technical or untranslated text. The updated com.adobe.granite.ui.content bundle handles the errors and supplies localized messages. (NPR-44840)

The error message that appears when you change properties of a deleted group in Security > Groups now displays in the user’s language. Previously, the message remained in English for localized interfaces. The updated com.adobe.granite.security.content bundle supplies the translations. (NPR-44841)

The error message “Something went wrong when saving the changes to the group!” now displays in the user’s language in the Security > Groups > Edit group console. Previously, the message stayed in English for localized interfaces. The updated com.adobe.granite.security.content bundle supplies the translations. (NPR-44842)

Chinese, Japanese, and Korean characters no longer display in italics in the Inbox icon error message. Previously, the italic style distorted the characters and made the text harder to read. The updated com.adobe.granite.ui.coralui3 bundle removes the style for those languages. (NPR-44843)

Numbers in Operations > Monitoring now follow the user’s locale format. Previously, the page showed numbers in a fixed format regardless of the interface language. The updated com.adobe.granite.monitoring.dashboard bundle applies the correct separators and format. (NPR-44844)

The Explain Query tab now shows the “Query Builder Debugger tool.” link in the user’s language. Previously, the link text was missing in localized interfaces because the string wasn’t externalized. The updated com.adobe.granite.monitoring.dashboard bundle restores it. (NPR-44845)

Text in the Query Builder Debugger tool dialog box now displays in the user’s language on the Explain Query tab. Previously, several strings stayed in English because they weren’t externalized. The updated cq-platform-content bundle supplies the translations. (NPR-44846)

Text in the Consistency Check Result page now displays in the user’s language. Previously, several strings appeared in English because they weren’t externalized. The updated com.adobe.granite.operations.ui.core bundle supplies the translations. (NPR-44847)

The Monitoring Chart now displays month and week labels in the user’s language. Previously, the labels were hard-coded in English, so the chart ignored the interface locale. The updated com.adobe.granite.monitoring.dashboard bundle externalizes the strings, and translations now appear. (NPR-44848)

The Country/Region dropdown in Security > Users > Create now sorts entries correctly. Previously, localized country names appeared in the wrong order for some languages. The updated com.adobe.granite.security.content bundle applies locale-aware sorting. (NPR-44942)

Tooltips in the Button component dialog box now display in the user’s language. Previously, the info text for the button text, link, icon, HTML ID, and aria-label fields remained in English even though the strings existed in the localization service. The updated dictionary supplies the translations in all supported locales. (SITES-7579)

Tooltips in the Properties section of the Content Fragment List component now display in the user’s language. Previously, the info text for the Content Fragment Model, Tags, Maximum number of items, Parent path, Sort order, and Order by fields remained in English. The updated dictionary provides translations for all supported locales. (SITES-14969)

The Help links for Core Components in the Template Editor now lead to localized documentation pages. Previously, selecting Help in the component configure dialog box opened the English page regardless of the interface language. Updated URLs now route users to the page for their locale. (SITES-15058)

The info tooltips in the Content Fragment dialog box now display in the user’s language. Previously, the tooltip text for the Single Text Element and Multiple Elements modes and for the Content Fragment path remained in English. An updated dictionary provides translations for all locales. (SITES-17333)

Error messages in the Template Editor Component Policy editor now appear in the user’s language. Previously, the messages “Resource {} is not modifiable” and “Unable to create node at” remained in English when authors edited a component policy or created a new one. The updated resources provide translations for all supported locales. (SITES-17475)

The Assets tab in the Page Editor now displays a translated string in the Select Components drop-down after you choose Paragraphs from the Images dropdown. Previously, the string “OTHER” appeared in English because the localization resources lacked it. The updated dictionary supplies the translation in all locales. (SITES-21481)

Info tooltips in the Page Editor Configure component dialog box no longer show an extra line break. Previously, tooltips for components, such as PDF Viewer and Progress Bar, wrapped awkwardly in several locales. The tooltips now wrap correctly, and word hyphenation works as expected. (SITES-38567)

The tooltip “to exit text editor press Esc key” now appears in the user’s language in the Text component configure dialog box. Previously, the string displayed in English because the localization resources lacked it. The tooltip now translates in all locales. (SITES-43186)

The STRUCTURE label in the Template Editor now appears in the user’s language. Previously, the label remained in English when authors opened an Adaptive Form template, because the string was missing from the localization resources. The label now translates in all locales. (SITES-43599)

The MSM Rollout dialog box loads the live copy list again after an upgrade. Previously, a NullPointerException in AsyncOperationServlet.doGet stopped the dialog box on a spinner, so authors failed to select target locales or start the rollout. An updated com.adobe.granite.jobs.async bundle handles the missing job data and finishes the request. (SITES-43116)

Rollout from the editable toolbar on a blueprint page works again. The toolbar action failed with “Cannot read properties of undefined (reading ‘doRollout’)” because the MSM.Rollout client library did not load. The updated page now loads the library, so the rollout job starts and changes reach the live copies. (SITES-46052)

Batch deactivation of a blueprint page and its child pages no longer sends duplicate rollout events. When you deactivated a parent and its children in one request, the replication system emitted five events instead of three, and each child page rolled out twice. Deduplication in the rollout manager now submits one rollout per page, so live copies receive no redundant packages. (SITES-44988)

The selected style remains highlighted in the Page Editor style selection dialog box after you scroll the list. Previously, a style highlighted when you chose it, but the highlight vanished when you clicked the scrollbar. This regression began after SP22, and the dialog box now keeps the selected state visible. (SITES-30874)

Authors can edit pages in Layout mode when parent and child components define different responsive breakpoints. The getResponsiveCssClasses function previously failed with a TypeError on components that omitted the cq:responsive/phone width. The function now falls back to available values and continues rendering. (SITES-46681)

Custom crop ratios now load in hybrid inline-editing mode for components with multiple image drop targets. Previously, the Image Editor initialized one generic ipeConfig for all drop targets, so the editor showed only the default ratios and ignored each target’s aspectRatios. The editor now reads the configuration for the selected drop target, and the crop applies in both inline and fullscreen views. (SITES-45771)

Pressing Backspace in the Rich Text Editor doesn’t add extra inline styles to the text. A customer reported that removing a line break after bold text added style=“font-size: 0.8125rem; background-color: transparent;” to the bold tag. Testing on the latest service pack failed to reproduce the behavior, so no change was necessary. (SITES-15883)

Enhancement: AEM Assets 6.5 includes support for Coalition for Content Provenance and Authenticity (C2PA) compliance for generative AI content. The Update Asset workflow detects C2PA credentials, extracts the metadata, and signs renditions that the workflow regenerates. Signing runs locally in each AEM instance, so customers don’t need dedicated signing infrastructure. (ASSETS-75868)

Documentation enhancement: New public documentation explains how to customize the asset processing pipeline while keeping C2PA compliance. The documentation covers how to position the Detect C2PA Credential step before rendition steps and how signing runs locally in each AEM instance. The documentation also states the limitation on dedicated or customer-owned signing infrastructure. (ASSETS-76100)

The Help drop-down in the shell header now remains open when you hover over its links in AEM 6.5 SP26 environments. Previously, the drop-down closed when the pointer entered the list, so authors failed to click Documentation, Community, or support links. The updated com.adobe.granite.ui.content bundle defers the focus check, so the menu closes only when focus truly leaves. (ASSETS-65676)

The Help link in the footer of the AEM login page now opens a working page. Previously, the link pointed to a marketing.adobe.com URL that no longer exists. The footer configuration now uses the Adobe Experience Manager documentation URL. (NPR-44388)

Enhancement: A customer request asked for the Microsoft Graph API as an alternative to SMTP when AEM sends email. The ticket resolved as a duplicate, because another ticket already implements the Graph API flow. SMTP with OAuth 2.0 remains available for customers who need to move away from SMTP basic authentication. (GRANITE-57478)

The strings in the Effective Permissions dialog now align correctly in Tools > General > Configuration Browser. Previously, one string displayed out of line after you selected a folder, clicked Properties, and clicked Effective Permissions. Updated layout rules restore the alignment. (CQ-4359166)

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 for 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 used a custom API name for your content model to use the default name of the content model instead.

A GraphQL query uses the damAssetLucene index instead of the fragments index. This action results 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 perform with improved speed.

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; 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 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 appear 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 declare their correct variables. Otherwise, they do not get run, and end up throwing a runtime error.

Installing tagging related standard 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 to the properties before installation.

When a form containing a File Attachment field that uses bindref is submitted to an AEM Workflow with an Assign Task step, the attachments are not displayed. As a result, they do not appear when the task is opened from the Inbox. The files are saved correctly to the repository but the Assign Task step UI fails to display the attachments. (FORMS-23722)

When a digitally signed PDF is attached to a task in AEM Forms JEE Workspace, the upload remains stuck in the uploading state or fails with an “Invalid File” error. As a result, larger, signed PDF attachments cannot be added to the task. This issue is fixed in a later version. For a hotfix on the version, contact Adobe Support. (FORMS-28517)

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, perform the following steps to resolve the issue (FORMS-14926):

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 admin mode.
6. Install the Geode patch using the geode-*-1.15.1.2.jar file.