DocumentationAEM 6.5User Guide

General Release Notes for Adobe Experience Manager 6.5 general-release-notes-for-adobe-experience-manager

Last update: Thu Aug 15 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • User
  • Admin
  • Developer

Release Information release-information

Product
Adobe Experience Manager
Version
6.5
Type
Major release
General availability date
April 8, 2019
Recommended Updates
See AEM recent updates.

Trivia trivia

The release cycle for this version of Adobe Experience Manager started April 4, 2018, went through 23 iterations of quality assurance and bug fixing, and ended on March 28, 2019. The total number of customer-related issues including enhancements and new features fixed in this release is 1345.

Adobe Experience Manager 6.5 is generally available since April 8, 2019.

AEM 6.5 Login Screen

What’s New what-s-new

Adobe Experience Manager 6.5 is an upgrade release to the Adobe Experience Manager 6.4 code base. It provides new and enhanced functionality, key customer fixes, high priority customer enhancements, and general bug fixes oriented toward product stabilization. It also includes Adobe Experience Manager 6.4 Service Pack releases up to SP4.

The list below provides an overview - while the subsequent pages list the full details.

Experience Manager Foundation experience-manager-foundation

The platform of Adobe Experience Manager 6.5 build on top of updated versions of the OSGi-based framework (Apache Sling and Apache Felix) and the Java™ Content Repository: Apache Jackrabbit Oak 1.10.2.

The Quickstart uses Eclipse Jetty 9.4.15 as servlet engine.

Java™ Support java-support

  • New support for Java™ 11, and the already supported Java™ 8.
  • For optimal performance, override default GC values with other values. For more information, see the install and update section.
  • Java™ 11 and Java™ 8 maintenance updates are distributed by Adobe for customer usage in AEM-related projects, when not publicly available from Oracle.

Java™ Development java-development

  • There are now two versions of the Uberjar, a recommended version with public interfaces that are not marked for deprecation, and a version that includes interfaces marked for deprecation.

User Interface user-interface

Various enhancements have been made to the UI to make it more productive and easier to use.

  • New Permissions Management UI for Users and Groups.
  • Column Views now also only load entries that are visible on the screen and only loads more when the user is starting to scroll. List and Card view already did that since 6.0 (improved in 6.4).
  • Column Views now include the workflow status for pages/assets when applicable.
  • The Select All action is a quick way to execute an action with all pages/assets in the same folder.
  • The Select All action attempts to perform the action to all pages/assets, not just what has been loaded. A warning dialog is displayed if the action is not upgraded to handle Bulk Actions.
CAUTION
Adobe does not plan to make further enhancements to the Classic UI. AEM 6.5 has the Classic UI included, and customers upgrading from earlier releases can keep using it as is. Classic UI remains fully supported while being deprecated. Read more.
  • Search in Oak now supports dynamic facets. For example, the filter rail in assets search shows the estimated number of results.
  • QueryBuilder was extended to provide results with dynamic facets.

Upgrade upgrade

  • Direct in-place upgrade to AEM 6.5 is supported for customers running AEM 6.2, 6.3 and 6.4. Customers using 5.x or 6.0/6.1 that want to use in-place upgrade need to upgrade to 6.4 first. Then, upgrade to 6.5, or upgrade by way of transfer of the content between the instances directly to AEM 6.5.
  • The upgrade procedure largely remains the same in 6.5.
  • We continue to support the Backward Compatibility , Upgrade Complexity Assessment and Sustainable Upgrades features introduced in 6.4. There have been version-specific updates made to these areas where needed.
  • The Pattern Detector packaging is now simplified. There is one package that assesses upgrades to 6.5 for the available source versions.
  • For details about upgrade procedure, see the upgrade documentation.

Projects and Workflows projects-and-workflows

  • New Workflow Model editor introduced in 6.4 has been improved to include more operations like Copy and Publish, Variable support in Workflow steps and enhanced OR and AND splits.

Repository repository

CAUTION
The new version of the Oak Segment Tar, present since AEM 6.3, requires a repository migration. This step is mandatory if you are upgrading from an older version of TarMK or want to switch the new Segment Tar from another type of persistence. For more information on what the benefits of the new Segment Tar are, see the Migrating to Oak Segment Tar FAQ.

OSGI osgi

  • Added OSGi Promises and Converter utility libraries.

Security security

  • Added Password expiration for admin user.

Web Server web-server

  • The Quickstart distribution uses Eclipse Jetty 9.4.15 as servlet engine (AEM 6.4 shipped with 9.3.22).

Experience Manager Sites experience-manager-sites

Managed Single-page Apps managed-single-page-apps

The Page Editor adds the ability to in-context edit content and compose/layout within client-side rendered experiences (also known as SPA Editor). Existing single-page apps build with JavaScript framework React or Angular can be extended with the AEM SJ SDK to be made editable for practitioners.

First shipped as part of AEM 6.4 SP2, with AEM 6.5 the SPA support gains following capabilities:

  • Use Template Editor to edit and configure the AEM editable parts of the SPA
  • Use Multi-site Management to create country, franchise, or white-labeled SPA experiences

Headless Content Management headless-content-management

AEM can serve the content in various formats and from various levels of the stack. Some have been around since 2008 with the Sling GET and POST Servlet. Content Services (Sling Model Exporter) was introduced in AEM 6.3 and is the method used by the AEM SJ SDK to hydrate single-page apps. The HTTP API for Assets is a CRUD API, that was extended for AEM 6.5.

New HTTP API capabilities:

Screens Add-on screens-add-on

Efficiently design, deliver, and optimize experiences on all digital displays from interactive kiosks to digital signage.

  • Unify experiences and content across digital and in-store with improved content reuse
  • Streamlined authoring and approval/publishing workflows with support for Launches
  • Edit and deliver rich interactive experiences using SPA Editor
  • Using Launches to plan future content changes for signage content
  • Metered playback in a sequence channel
  • Auto create project structure using a source file such as an Excel sheet
  • Expanded media player support with robust on-line and offline operation (Smart Sync) able to scale to even the largest signage networks.
  • Personalize by location or configuration of data triggered content by using dynamic placeholders.
  • Unified insights driven by Adobe Analytics integration into the AEM Screens Player

For more details on changes to AEM Screens - see the Release Notes in the AEM Screens User Guide.

Component & Template Development component-amp-template-development

  • Maven Project Archetype 18+ for new projects, see GitHub for release notes.

  • Single-page App Maven Project Archetype 1.0.6+ for new projects, see GitHub for release notes.

  • HTL version 1.4, see GitHub for release notes.

    • “in” operator for strings, arrays, and objects:

      code language-html 
      ${'a' in 'abc'}
${100 in myArray}
${'a' in myObject}

    • Variable declarations with data-sly-set :
      <sly data-sly-set.title="${currentPage.title}"/>${title}

    • List and repeat control parameters: begin, step, end:
      <h2 data-sly-repeat="${currentPage.listChildren @ begin = 1, step=2}">${item.title}</h2>

    • Identifiers for data-sly-unwrap:

      code language-html 
      <div data-sly-unwrap.isUnwrapped="${myCondition || myOtherCondition}">
text <span data-sly-test="${isUnwrapped}>is unwrapped</code>
</div>

    • Support for negative numbers

  • Core Components 2.3.2+, see GitHub for release notes.

  • Grid System for Layout Container, see GitHub.

  • Clientlib Manager: made Google Closure Compiler default to minification of JavaScript clientlibs (old default was Yahoo YUI) and updated Google Closure Compiler to version v20190121

  • Template Editor and Policies

    • Create and edit templates for single-page apps that are using the JS SDK (also called SPA Editor)

  • Reference Site We.Retail 4.0, see GitHub for release notes.

  • Toolkit to upgrade existing sites to use the latest editor capabilities, see GitHub repository

CAUTION
AEM includes version 1.12.4 of the jQuery library to provide maximum compatibility with existing custom code. Modifications have been done by Adobe to address known security issues.

Site Administration site-administration

  • The Reference rail has a new section to list internal links that are pointing to the page selected. This is useful when planning to take a page offline or delete - to see what pages need to be adjusted before taking them offline.
  • The list view has a new workflow column that shows the status when the page is in a workflow.
  • In the page properties, it is now possible to browse for existing assets when assigning a Thumbnail to the page (Thumbnail tab).

Page Editor page-editor

  • Allow in-context editing and composition of single-page app experiences build with React and Angular client-side components that are using the JS SDK (also called SPA Editor)
  • Scaffolding Mode is only shown if the page has a scaffolding page configured.

Content Fragments & Editor content-fragments-amp-editor

  • New Annotations rail in Content Fragment Editor to make general comments and see comments made within the text (also show up in Timeline rail)
  • Ability to set the default content type of a multi-line text element in a Content Fragment model to simple text, rich text, or markdown
  • Add comment/annotations by selecting text in the RTE (full-screen view)
  • Compare versions of a Content Fragment side-by-side via Reference rail
  • The assets Download Report now shows Content Fragments accordingly
  • Add Content Fragment support to Assets HTTP API via /api.json. There are APIs for create, update, read, and delete of Content Fragments.

Experience Fragments experience-fragments

  • Improved the indexing of Experience Fragments, so their content is found in search for pages where they are being used.
  • The Export to Target option now lets you send the Experience Fragment as JSON (default is HTML) or both.

Translation translation

  • Simplify creating Translation Projects by using Project Masters.
  • Simplify executing Translation Projects by setting translation jobs to approved status by default.
  • Allow updating translated pages with changes in 3rd-party Translation Memory.
  • Allow exporting translation jobs in JSON format.
  • Update Microsoft® Translation integration to use V3 API.

Multi-Site Management (MSM) multi-site-management-msm

  • For roll-out configs that use PushOnModify, better handling of page move operation to avoid inconsistent state.
  • Creating a page inside the livecopy structure creates a standalone page by default.
  • Use MSM features in single-page apps that are using the JS SDK (also called SPA Editor)

Launches launches

Content Targeting & Simulation content-targeting-simulation

  • ContextHub data layer and client-side rules engine JavaScript has been updated to use jQuery 3 by default.

AEM and Adobe Target aem-amp-adobe-target

CAUTION
Currently:

  • Only at.js 1.x is supported if you are using Adobe Target as your targeting engine within AEM’s Activities console.

  • Both at.js. 1.x and at.js 2.x are supported if you are using Experience Fragment export to Target and running Activities within Target’s console.

  • Adobe Target integration now uses the Target Standard API. Earlier versions of AEM use the Target Classic HTTP API which is now deprecated.
  • Adobe Target mbox.js version 63 is included. Adobe strongly recommends that you switch the implementation to at.js v1.x.
  • at.js version 1.5.0 is now included. Adobe recommends that you use Adobe Experience Platform Launch to provision at.js v1.x into the site.

AEM and Adobe Analytics aem-amp-adobe-analytics

  • s_code.js H.27.5 is included. Adobe recommends that you switch implementation to AppMeasurement.js
  • AppMeasurement.js v1.8.0 is included. Adobe recommends that you use Adobe Experience Platform Launch to provision AppMeasurement.js into the site.

AEM and Commerce aem-commerce

Improvements to the Commerce Integration Framework are on a faster release cycle since AEM 6.4. Learn more from AEM and Adobe Commerce Integration Using Commerce Integration Framework.

Communities Add-On communities-add-on

To obtain the latest release, see the Deploying Communities section of the documentation.

Enhancements to community engagement enhancements-to-community-engagement

@Mentions support
AEM Communities now allows registered users to tag (mention) other registered members to elicit their attention, in User Generated Content. The tagged (mentioned) members are then notified, with deep link to the corresponding User Generated Content. Users can, however, opt to disable/enable the web and email notifications.

At mentions support

Community users do not need to search for their first name, last name, or user name to see if anyone has reached out to them or needs their attention. Moreover, it allows the UGC authors to seek response from specific registered users who can best address the issue and add inputs.

The community administrators need to Enable Mention on community components to allow registered users use the functionality on those components.

Group messaging

Registered community members can now send direct messages in bulk to groups through a single email composition, instead of sending the same message individually to group members. To allow group messaging, enable both the instances of Messaging Operations Service.

Group message

Enhancements to Bulk Moderation enhancements-to-bulk-moderation

Custom filters in Bulk Moderation

Custom filters can now be developed and added to Bulk Moderation UI.

A sample project that demonstrates filtering through tags is available in GitHub. This project can be used as a base to develop analogous custom filters.

Custom filters

List View in Bulk Moderation

New List View with improved UI has been provided in bulk moderation to display User Generated Content entries.

Bulk moderation in list view

Enhancements to Site and Group Management enhancements-to-site-and-group-management

Author side site and group administrators

Communities, AEM 6.5 onwards, allows decentralized administration (and management) of different community sites and groups/ nested groups. Organizations hosting multiple community sites and nested groups can now select members for administrator roles on Author side at the time of site (and group) creation.

Site administrator

Site Administrators can create a group at any level of hierarchy and become the default administrators. These administrators can later be removed by other group administrators. Group administrators can manage their group G1 and create a subgroup nested under G1.

Enhancements to enablement enhancements-to-enablement

SCORM 2017.1 support

The enablement functionality of AEM 6.5 Communities support Shareable Content Object Reference Model (SCORM) 2017.1 engine.

  • Keyboard navigation support on enablement components
  • Enablement components (for example, Catalog and Course Playing, Assignments, File Library) in AEM Communities support keyboard navigation for improved accessibility.
Other enhancements other-enhancements
  • Solr 7 support
  • AEM 6.5 Communities support Apache Solr 7.0 version of the search platform while setting up MSRP and DSRP.

Experience Manager Assets experience-manager-assets

AEM 6.5 introduces the following capabilities and enhancements to boost productivity of AEM users, DAM roles, and associated creative and marketing roles.

Integration with Adobe Creative Cloud and creative workflows integration-with-adobe-creative-cloud-and-creative-workflows

Adobe Experience Manager offers various ways to integrate with Adobe Creative Cloud and share assets for use in workflows where the creative and marketing or business teams collaborate closely. Experience Manager 6.5 continues to improve on the integration and streamlines it further to expose more opportunities and streamline the existing methods.

Read on to know the specific capabilities and integrations of Experience Manager 6.5 that you can use to best support your content velocity use cases.

Adobe Asset Link strengthens collaboration between creatives and marketers in the content creation process. Creatives can access content stored in Experience Manager Assets, without leaving the apps that they are most familiar with. Creatives can seamlessly browse, search, check out, and check in assets using the in-app panel in Adobe Photoshop, Adobe Illustrator, and Adobe InDesign apps.

Adobe Asset Link is a part of Creative Cloud for enterprise offering. For more information about it, including necessary configuration of your Experience Manager deployment, see Adobe Asset Link.

Search assets in Adobe Photoshop

Adobe Stock integration stock

Your organization can use its Adobe Stock enterprise plan within Experience Manager Assets to ensure that licensed assets are broadly available for your creative and marketing projects. You can quickly find, preview, and license Adobe Stock assets that are saved in Experience Manager, using the powerful DAM capabilities of Experience Manager.

Adobe Stock service provides designers and businesses with access to millions of high-quality, curated, royalty-free photos, vectors, illustrations, videos, templates, and 3D assets for all their creative projects.

For more info, see Use Adobe Stock assets in Experience Manager Assets.

Preview Adobe Stock image and license from within Experience Manager Assets

Figure: Preview Adobe Stock image and license from within Experience Manager Assets.

Search and filter the licensed Adobe Stock images in Experience Manager

Figure: Search and filter the licensed Adobe Stock images in Experience Manager.

Dynamic references in Adobe InDesign dynamic-references-in-indesign

Experience Manager Assets used in Adobe InDesign files are dynamic. The references update automatically if the referenced assets moves in the repository. For more information, see how to manage compound assets.

Brand Portal capabilities brand-portal-capabilities

Experience Manager Assets Brand Portal helps you easily acquire, effectively control, and securely distribute the approved assets to external vendors/agencies and internal business users across devices. It helps improve the efficiency of asset sharing, accelerates the time-to-market for assets, and eliminates the risk of non-compliant usage and unauthorized access.

For more information, see What’s new in Brand Portal.

Connected Assets connectedassets

In large enterprises the infrastructure required to create websites can be distributed. At times, the website creation capabilities and the required digital assets reside in different silos.

Experience Manager Sites offers capabilities to create web pages and Experience Manager Assets is the Digital Asset Management (DAM) system that supplies the required assets for websites. Experience Manager now supports the above use case by integrating Sites and Assets. See how to configure and use Connected Assets feature.

Drag an asset from an Experience Manager deployment on a Sites page of a different Experience Manager deployment

Figure: Drag an asset from an Experience Manager deployment on a Sites page on a different Experience Manager deployment.

Dynamic Media dynamic-media

Dynamic Media provides enhanced rich-media authoring and delivery in Experience Manager Assets to drive cutting-edge experiences that are immersive and personalized. By uploading a single high-quality primary asset and using Adobe’s advanced cloud rendering and viewers, you can deliver any combination of renditions on-the-fly to support your organization’s media strategy.

For more details on new Dynamic Media features, see Dynamic Media Release Notes.

360 video support video-support

Manage your 360-video files directly in Experience Manager using the cutting edge viewers to deliver VR-experiences to desktops, mobile, and VR-headsets. For more information, see Using 360 Video.

Custom video thumbnails custom-video-thumbnails

You can now customize the thumbnails for your video assets using frames from the video itself or other content stored in the DAM. For additional instructions, see About Video Thumbnails.

Accessibility enhancements accessibility-enhancements

Dynamic Media viewers now support enhanced accessibility features like Aria-support, screen-readers, and Alt-text. For additional details, see Viewers Reference Guide.

Search experience enhancement experience-enhancement-for-searching

Experience Manager 6.5 onwards, marketers can discover the desired assets faster from the search results page. The search facets are updated with the number of assets even before applying the search filter. Seeing the expected count against the filter helps users navigate through the search results efficiently. For more information, see Search assets in Experience Manager.

See the number of assets without filtering search results in search facets

Figure: See the number of assets without filtering search results in search facets.

Usability enhancement usability-enhancement

You can now select all the loaded assets within a folder or from a search result in one go. It helps you to manage multiple assets quickly. The check box selects all the assets that fit the scenario, say a search result, and not just the assets that are visible in the Experience Manager interface.

Use Select All option to select all the loaded assets in one click.

Figure: Use the Select All option to select all the loaded assets in one click.

Metadata enhancements metadata-enhancements

Assets let you create metadata schemas for asset folders, which define the layout and metadata displayed in folder properties pages. You can now assign a folder metadata schema to an existing folder or when creating a folder. For more information, see Folder metadata schema.

When specifying cascading metadata, the choices can be loaded from a JSON file at the run-time, say instead of typing manually in the form. For more information, see cascading metadata.

Reporting enhancements reporting-enhancements

The Content Fragments and link shares are included in the downloaded report now. For more information, see Assets reports.

Adobe Experience Manager Forms experience-manager-forms

AEM 6.5 Forms bring in several new features and enhancements. The highlights include:

  • Transaction reports to track the number of submitted forms, processed documents, and rendered documents
  • Usability improvements to interactive communications
  • Cloud-based digital signatures in adaptive forms
  • Embed adaptive forms and interactive communications in an AEM Sites single page application (SPA).
  • Support for variables in AEM Workflows
  • Data display pattern support in interactive communications
  • Sorting adaptive forms and interactive communication tables
  • Automated validation of input data in form data models

See the Summary of new features and enhancements in AEM 6.5 Forms for information about new and improved features and documentation resources.

Use Customer-focused Development use-customer-focused-development

Adobe is using a customer focused development model that allows customers to contribute to all stages of the development process, during specification, development, and testing. Our thanks go to all contributing customers and partners in this process.

Adobe has the procedures and processes in place to enable collection, prioritization, and tracking of customer-focused bug resolution and enhancement request development. The Experience Manager Support portal is integrated with the Adobe Enhancement and Defect Tracking System. Customer questions are identified and resolved by Customer Support team where possible. When escalated to R&D, all customer information is captured, and used for prioritization and reporting purposes. Priority is given in development to paid support, warrantee issues, and customer-paid enhancements.

This process of prioritization has yielded more than 750 customer focused changes fixed in AEM 6.5.

List of files that are part of the Release list-of-files-that-are-part-of-the-release

Foundation

Sites

Assets

  • Package to add enhanced PDF Rasterizer (read more)
  • Package to add extended RAW image support (read more)

Forms

Languages languages

The user interface is available in following languages:

  • English
  • German
  • French
  • Spanish
  • Italian
  • Brazilian Portuguese
  • Japanese
  • Simplified Chinese
  • Traditional Chinese (limited support)
  • Korean

Experience Manager 6.5 has been certified for GB18030-2005 CITS to use the Chinese Encoding Standard.

Install and Update install-update

For setup requirements, see installation instructions.

For detailed instructions, see upgrade documentation.

Supported Platforms supported-platforms

Find the complete matrix of supported platforms including support-level on AEM 6.5 technical requirements.

NOTE
Oracle has moved to a Long Term Support (LTS) model for Oracle Java™ SE products. Java™ 9 and 10 are non-LTS releases by Oracle. See Oracle Java™ SE support roadmap. Adobe supports LTS releases of Java™ to only run AEM in production. Java™ 11 is the recommended version to use with AEM 6.5.

Deprecated and Removed Features deprecated-and-removed-features

Adobe constantly evaluates capabilities in the product and over time plans to replace capabilities with more powerful versions, or decides to reimplemented selected parts to be better prepared for future expectations or extensions.

For Adobe Experience Manager 6.5, read the list of deprecated and removed capabilities. The page also contains pre-announcement of changes coming in the future and important notice for customers that update from prior releases.

Known Issues known-issues

Platform platform

  • An issue is reported where the CRX-Quickstart, and its contents, are deleted.

    On each of these actions, ensure that the property htmllibmanager.fileSystemOutputCacheLocation is not an empty string:

    1. Calling /libs/granite/ui/content/dumplibs.rebuild.html?invalidate=true.
    2. Upgrading to AEM 6.5.
    3. Executing “lazy content migration” on AEM 6.5.

    A Knowledge Base article is available with further details and the workaround for this issue.

  • If you are using JDK 11 with AEM 6.5 instance, some of the pages might display as blank after deploying some packages. The following error message displays in the log file:

    code language-java 
    *ERROR* [OsgiInstallerImpl] org.apache.sling.scripting.sightly bundle org.apache.sling.scripting.sightly:1.1.2.1_4_0 (558)[org.apache.sling.scripting.sightly.impl.engine.extension.use.JavaUseProvider(3345)] : Error during instantiation of the implementation object (java.lang.NoClassDefFoundError: jdk/internal/reflect/ConstructorAccessorImpl)
java.lang.NoClassDefFoundError: jdk/internal/reflect/ConstructorAccessorImpl

To resolve this error:

  1. Stop the AEM instance. Go to <aem_server_path_on_server>crx-quickstart\conf and open the sling.properties file. Adobe recommends taking a backup of this file.

  2. Search for org.osgi.framework.bootdelegation=. Add jdk.internal.reflect,jdk.internal.reflect.* properties to display the result as.

org.osgi.framework.bootdelegation=sun.*,com.sun.*,jdk.internal.reflect,jdk.internal.reflect.*
  1. Save the file and restart the AEM instance.

Sites sites

Assets assets

  • Search: Search does not result any returns if the search string contains leading spaces (OAK-4786)
  • Folder Metadata Schema: After adding a choice button, the ID and Value field are not rendered as expected and the delete functionality does not work. (CQ-4261144)
  • When renaming an asset, it is not possible to use a whitespace in the asset name. (CQ-4266403)

Forms forms

  • When AEM Forms is installed on Linux® operating system, Digital Signature with Hardware Security Module do not work. (CQ-4266721)

  • (AEM Forms on WebSphere® only) The Forms Workflow > Task Search option does not return any result if you search for an Administrator with Username as the search criteria. (CQ-4266457)

  • AEM Forms fail to convert TIF and TIFF files with JPEG compression to PDF Documents. (CQ-4265972)

  • The AEM Forms Assets Scanner and Letter to Interactive Communication Migration options do not work on the AEM Forms Migration page. (CQ-4266572)

  • (JBoss® 7 only) When you upgrade from a previous version to AEM 6.5 Forms and the previous version had processes (.lca) that created and used a copy of the default submit or default render process, HTML5 Forms using such processes (.lca) fails to perform the required actions. (CQ-4243928)

  • In an adaptive from, when a form data model service is invoked from the rule editor to dynamically update values of the image choice component, values of the image choice component are not updated. (CQ-4254754)

  • AEM Forms Designer installer requires the 32-bit version of Visual C++ redistributable runtime package 2012 and Visual C++ redistributable runtime packages 2013. Ensure that the previously mentioned redistributable runtime packages are installed before starting the installation. (CQ-4265668)

  • PDF Generator does not support smart card-based authentication. When an administrator enables the Group Policy Interactive Logon: Require Smart card on a Windows server, all the existing PDF Generator users are invalidated.

  • When an adaptive form is configured to dynamically update values of a component and the publish instance that hosts the form is accessed through the Dispatcher, the functionality to dynamically update values of a field stop working. To resolve the issue, on the publish instance, open CRXDE, navigate to /libs/fd/af/runtime/clientlibs/guideChartReducer, and create the property listed in below.

    • Name: allowProxy
    • Type: Boolean
    • Value: true
    • Protected: False
    • Mandatory: False
    • Multiple: False
    • Auto Created: False

    The property enables the client libraries under the runtime folder to access proxies. (CQ-4268679)

  • When AEM Forms is started, the SAX Security Manager could not be setup warning appears.

  • When you open a PDF protected with AEM Forms Document Security on an Apple iOS or iPadOS running version 20.10.00 of Adobe Acrobat Reader

  • When you submit a form containing a standard HTML upload field from an Apple iOS device, sometimes, the content of the file is not sent and a 0-byte file is received at the other end. Apple iOS 15.1 provides a fix for the issue.

Product Download and Support (Restricted Sites) product-download-and-support-restricted-sites

The following sites are available only to customers. If you are a customer and need access, contact your Adobe account manager.

recommendation-more-help
19ffd973-7af2-44d0-84b5-d547b0dffee2