Adobe Experience Manager 6.5 Service Packs provide new features, customer-requested enhancements, and performance, stability, and security improvements at quarterly intervals. The quarterly availability makes it easy to access and adopt new features and innovations.
This article highlights the features included in the latest Service Pack key features included in the previous 6.5 Service Packs, and the key releases since the last Service Pack release.
Auto-generation of sitemap for SEO purposes is possible using the SEO index package. It supports sitemaps, alternate URLs, robot meta tags, and more in the Core Components.
Added multifield support for multiline text data type.
Enhancement to make users aware of the asynchronous job currently running in the background to prevent them from triggering multiple asynchronous operations on same path.
A user experience enhancements displays the number of assets present in a folder. For more than 1000 assets in a folder, Assets displays 1000+.
The following accessibility enhancements are available:
Tabkey to move focus to the first item that opens Quick Actions on focus, the screen reader announces the name of the focused item.
You can now use Dynamic Media to configure General Settings instead of having to go through the Dynamic Media Classic desktop application. See Configure Dynamic Media General Settings.
You can now use Dynamic Media to configure Publish Setup instead of having to go through the Dynamic Media Classic desktop application. See Configure Dynamic Media Publish Setup.
Enhanced Content Fragment Models and Editor: You can now create complex and custom models for structured content using nested Content Fragment models. Content structures are modularized into basic elements that are modeled as sub-fragments. Higher-level fragments reference these sub-fragments. More data type enhancements such as advanced validation rules further enhance the flexibility of content modeling with Content Fragments. The Experience Manager Content Fragment editor supports nested fragment structures in a common editor session, with enhancements such as structure tree view and tabbed breadcrumb navigation through fragment hierarchies.
GraphQL API for Content Fragments: The new GraphQL API is the standard method to deliver structured content in JSON format. GraphQL queries let clients request only the relevant content items to render an experience. Such a selection eliminates content over-delivery (possibility with HTTP REST APIs) that requires content parsing on the client side. GraphQL schemas are derived from Content Fragment models, and API responses are made in JSON format. In Experience Manager as a Cloud Service, GraphQL queries persist and process cache friendly GET requests. It is not yet possible in Experience Manager 6.5.
Hierarchy management and future preview: Users now have an interface to access the content structures of their Experience Manager launches, including the ability to add and remove pages in a launch. This feature enhances the flexibility of Experience Manager launches to author content versions targeted for future publishing. Time-warp feature lets users preview launches as future content states.
Experience Manager directly displays a list of all the content models under a folder without content authors having to navigate through the file structure. The functionality now requires fewer clicks and improves authoring efficiency.
Pathfield in Sites editor allows authors to drag assets from Content Finder.
Platform provides a few accessibility enhancements. See Platform updates.
You can now restore the deleted pages and the entire tree view on an Experience Manager Sites page.
You can now sort the Live Copy pages available for rollout using the Name, Last modified date, and Last rollout date properties. The Last rollout date for a page is a new property introduced in this release.
You can now perform the page moves and MSM rollouts as asynchronous operations to reduce their impact on runtime performance. You can schedule the operations for immediate or later execution. The status of associated jobs and process steps is displayed in a console, which is helpful for monitoring large-scale MSM rollouts.
Page Move operation is now available in asynchronous mode. In addition to immediate execution, you can also schedule the Page Move operation for later execution.
Improved error reporting by adding text information.
Improved user interface focus during keyboard navigation.
Improved contrast ratio for various user interface elements.
Improved consistency of alt attributes for page images.
Improved consistency of Accessible Rich Internet Applications (ARIA) labels.
Improved Non-Visual Desktop Access (NVDA) capabilities.
Improved screen reader support.
Anonymous access to CRXDE Lite is disallowed to enhance security. Instead, the users are directed to the login screen. See Developing with CRXDE Lite.
When copying or pasting a page tree, you now have the option of either pasting the root page or pasting the root page with the subpages of the tree.
Adobe Experience Manager Experience Fragments exported to Adobe Target workspaces now appear as unique offer types and offer sources in Target.
Multi Site Manager - The Publish trigger now deletes a component from the published page if a component is deleted from the source page.
Multi Site Manager - When the name of a local component in a Live Copy is identical to the name of a component in the blueprint and the component is rolled out from the blueprint, then the term
_msm_moved is now added to the name of the local component.
You can now select styles within the component dialog using the enhanced Style System.
Reduced the time to load and initialize ContextHub within a site (
contexthub.kernel.js). It results in faster page loads during a site visit.
Reduced the time to refresh a page after dragging Experience Fragments to Sites Page Editor.
Shortened the load time for entries on a Sites page with more than 200 live copies in Live Copy Overview.
Improved handling of incomplete or invalid URLs. Such URLs can slow the Template Editor.
Experience Manager extends the Connected Assets functionality to the use of Dynamic Media images in the applicable core components. See use Connected Assets.
When sharing individual assets and Collections as a link (using Link Sharing dialog), users can choose whether to let the receiver download original assets, or their renditions, or both. See Share assets via link.
When users download assets shared with them as a link, they can choose to download the original assets, the renditions, or both.
Limit sub-assets generated:
Administrators can limit the number of sub-assets that Experience Manager generates for compound assets such as PDF, PowerPoint, InDesign, and Keynote files.
A new Camera Raw package is available that supports Adobe Camera Raw v10.4. See process images using Camera Raw.
Updated the naming of Chinese locales and regions relating to Hong Kong, Macau, and Taiwan, to make them consistent with Chinese social and political views (22.214.171.124).
An optional configuration is introduced to change casing in the email IDs in ACP API response from Adobe Experience Manager (126.96.36.199).
Contrast of text and icons against the background is enhanced for various features. This implementation of Web Content Accessibility Guidelines (WCAG) guidelines makes Assets more accessible for users with limited vision and perception of color. See accessibility enhancements in Assets (188.8.131.52).
When using Connected Assets functionality, you can now view a list of all the Sites pages that use the asset. These references to an asset are available in an asset’s Properties page. This allows administrators, marketers, and librarians a complete view of assets usage, allowing for better tracking, management, and brand consistency (184.108.40.206).
When deleting an asset that is referenced in a web page, Experience Manager displays a warning. You can force delete a referenced asset or check and modify the references that are displayed in the Properties page of the asset. Clicking the references opens the local and remote Sites pages (220.127.116.11).
Assets and Dynamic Media provide multiple accessibility enhancements. The enhancements are related to keyboard navigation, use of screen readers, similar enhancements to enable use of assistive technologies (AT). See Assets enhancements and Dynamic Media enhancements (18.104.22.168)
Users can sort digital assets in Card and Column views (22.214.171.124).
Enhanced user interface focus during keyboard navigation, for example focus on:
x icon in Version Preview dialog of an asset in Timeline.
Actionable user interface options.
Email field on the Share Link dialog, and field to add closed user group in Permission tab of folder Properties.
Enhanced functionality using keyboard keys
Users can use keyboard keys to drag controls in Metadata Schema Form editor in browse mode of screen reader.
Enhanced usability for screen reader users, due to the following:
Screen readers announce the purpose of video and audio players.
Screen readers announce the purpose of the user interface options to remove the tags selected using Tags selection dialog on asset Properties.
Screen readers announce the row headers and row items of tables, so users know which entries belong to the same row.
Descriptive and meaningful page title of search page.
Screen readers announce the options in search filter panel as expandable accordions.
Experience Manager Assets is now more accessible in compliance with Web Content Accessibility Guidelines (WCAG). The accessibility has improved because of the following enhancements:
Many user interface elements, controls, pages, and dialogs are screen reader friendly.
Many user interface elements, controls, and input form fields are accessible using keyboard.
Color and contrast of some user interface elements are updated so that users with limited vision or users without perception of color can distinguish these user interface elements. For example, the color of star rating icons (such as in Rating section of Advanced tab in asset Properties or in card view) is changed for appropriate contrast.
Assets user interface flow has better exception handling. If an asset does not have a type for its dimension, the observed exception is recorded in the log files.
The authorization channel between Experience Manager Assets and Brand Portal is changed. Earlier, Brand Portal was configured in Classic UI via Legacy OAuth Gateway, which uses the JWT token exchange to obtain an IMS Access token for authorization. Experience Manager Assets is now configured with Brand Portal through Adobe I/O, which procures an IMS token for authorization of your Brand Portal tenant.
The steps to configure Experience Manager Assets with Brand Portal are different depending on your Experience Manager version, and whether you are configuring for the first time, or upgrading the existing configurations. See Configure Experience Manager Assets with Brand Portal for details.
Experience Manager Assets includes the following accessibility enhancements:
Arrow keys on keyboard can be used to move and pan areas within zoomed images. For more information, see preview assets using keyboard keys only.
The mixed state checkboxes (in which unless you select all the nested predicates the first-level checkboxes are not selected and are stricken through) in Filters panel are readable by screen readers.
Date and time format constraints are provided in field labels of date fields, to enable the users to enter the date in correct format using keyboard.
On Time (MM-DD-YYYY HH:mm). Here MM is month in two-digit format, YYYY is year, DD is day in two-digit format, HH is hour in 24-hour military format, and mm is minute.
Screen readers announce the option to remove selected tags (
X symbol) and the number of the selected tags.
A new sortable column for created date of assets is added in DAM list view and on asset search results in list view.
Assets users can search visually similar images. Experience Manager displays the smart tagged images from the DAM repository that are similar to a user-selected image. See Visual search.
Many accessibility enhancements are done in Dynamic Media client so that a screen reader can present a more appropriate and useful description of the action or user interface. See Dynamic Media updates (126.96.36.199).
Dynamic Media is more accessible in terms of:
Deliver best quality images efficiently on devices with high-resolution displays and constrained network bandwidth, with Smart Imaging DPR (Device Pixel Ratio) and network bandwidth optimization. See Smart imaging FAQs (188.8.131.52).
Dynamic Media delivery (
fmt URL modifier) now supports next-generation image format AVIF (AV1 Image format). For more details and timeline, see image serving and rendering API fmt (184.108.40.206).
Support for 3D images in Dynamic Media enables customers to publish and add 3D content to web pages and applications. The support includes:
Publish common 3D asset formats and generate an asset URL that can be used in web pages and other applications.
A 3D Web Viewer, powered by Adobe Dimension, to interactively view the published 3D assets.
Publish and view common 3D assets on Experience Manager Sites pages using the Sites WCM component.
You can now use the Dynamic Media user interface to invalidate Content Delivery Network (CDN) cached content. As a result, the updated assets are available instantly instead of waiting for the cache to expire. You can invalidate CDN by:
Creating a CDN invalidation template: Selecting assets and form associated template-based URLs
Selecting assets and associated presets through asset picker
Adding complete asset URLs
You can now choose to selectively publish or unpublish assets to either Experience Manager or Dynamic Media using Quick Publish or Manage Publication wizard. You can also set the
Unpublish mode at folder level.
Smart imaging uses each user’s unique viewing characteristics to automatically serve the right images optimized for their experience, resulting in better performance and engagement. Smart imaging works with your existing image presets and uses intelligence at the last millisecond of delivery to further reduce image file size based on browser or network connection speed. See Smart Imaging.
Smart crop for video – an optional feature available in Video Profiles – uses Adobe Sensei to automatically detect and crop the focal point in any adaptive video or progressive video, regardless of size. See about using smart crop in video profiles.
The add-on package of Experience Manager Forms is made available a week after the scheduled Experience Manager Service Pack release.
You can now use Automated Forms Conversion service to convert PDF Forms in French, German, Spanish, Italian, and Portuguese languages to adaptive forms.
Error messages in Properties browser: Added error messages for each property in the Adaptive Forms Properties browser. These messages help understand allowed values for a field.
Support to use the literal option to set value for a JSON type variable: You can use literal option to set value for a JSON type variable in the set variable step of an AEM Workflow. The literal option allows you to specify a JSON in the form of a string.
Platform Updates: Adobe Experience Manager Forms on JEE has added support for the following platforms:
Added support for
GuideBridge#getGuidePath API in AEM Forms.
You can now develop and operate applications with Azul Zulu builds of OpenJDK for Experience Manager Forms on OSGi deployments. For more information, see Experience Manager 6.5 Service Pack 9 Release Notes and Technical Requirements.
You can now send a notification email to a group email address using the Assign Task workflow step.
You can now retrieve an interactive communication saved as a draft after you change the source Interactive Communication.
reCAPTCHA service uses
https://www.recaptcha.net/ as the default domain. You can now modify the settings to set
https://www.google.com/ or any custom domain name to load, render, and validate the reCAPTCHA service.
When you select a form data model and a service in Invoke Form Data Model Service workflow step, you specify service arguments for input data.
If you select Relative to Payload option to attach a file as a service argument, you can now specify the folder path that contains the file instead of the actual file name. Defining the folder name, instead of the file attachment name, enables you to reuse workflow models. You do not limit the workflow model to a single file attachment name.
You can now use multiple master pages in a Document of Record template. As a result, you can now have different header, footer, fonts, logo information on the title page and other pages of the template.
You can now add page breaks to a Document of Record. As a result, if a panel breaks within pages, you can add a page break to move the panel to a new page in a Document of Record.
You can now validate CAPTCHA either on adaptive form submission or on user action. You can also add conditions to validate CAPTCHA on a user action and show or hide the CAPTCHA component in an adaptive form based on rules.
Experience Manager Forms provides out of the box support to use Google reCAPTCHA (A separate license of Google reCAPTCHA APIs is required) as a CAPTCHA validation service. You can also use a custom CAPTCHA service to validate CAPTCHAs.
Improved accessibility of the Experience Manager Forms Date Picker component.
Added support to generate an Interactive Communication in PCL format using the PrintChannel API.
When performing a PDFG conversion, you can now enable or disable the Experience Manager Forms registry changes for custom bookmark generation.
Experience Manager 6.5 Service Pack 7 Forms improves the performance for:
Validating the field values on the server when you submit an adaptive form.
Converting a PDF form to an adaptive form using the Automated Forms Conversion service.
Experience Manager Forms now supports Microsoft SQL Server 2016 Always On availability groups for High Availability for OSGi deployments.
Experience Manager Forms form data model when integrating with RESTful web services as the data source now includes HTTP client configurations for performance optimization. See Configure data sources.
You can now use the reset option for each component in Layout mode of an adaptive form. When you define a multicolumn layout for a panel, you can use this feature to reset individual components within the panel. See Use layout mode to resize components.
When you prefill an adaptive form, the Experience Manager Forms server merges data with an adaptive form and delivers the filled form to you. By default, the data merge action takes place at the server.
You can now configure the Experience Manager Forms server to perform the data merge action at the client instead of the server. It significantly reduces the time required to prefill and render adaptive forms.
Experience Manager Forms form data model can now integrate with RESTful APIs on a server that has a two-way SSL implemented on it.
If an AcroForm includes Adobe Sign Text Tags, those fields are now recognized and represented as Adobe Sign fields in the adaptive form converted using Automated Forms Conversion service. A signer can fill such fields while signing the adaptive form.
You can use Automated Forms Conversion service to convert colored PDF forms to adaptive forms.
Experience Manager Forms now supports SMB 2 and SMB 3 protocols.
You can now specify locale as a selector in the adaptive form URL instead of an argument in adaptive form URL. It helps cache translated adaptive forms on Experience Manager Dispatcher. Caching translated adaptive form was not possible in previous versions. For detailed information about configuring caching for using locale as a selector in the adaptive form URL, see Configure adaptive form cache at dispatcher.
Form data model allows you to save output of a form data model service to a variable. Experience Manager Forms now automatically maps the type of the form data model service to the type of variable.
You can now attach multiple files to the File Attachment component of adaptive forms.
You can customize an Experience Manager Inbox to change the default title of a column, reorder the position of a column, and display additional columns based on the data of a workflow. Members of
workflow-administrators group can customize the columns. For more information, see Admin Control.
You can use the Agent UI to save one or more drafts for each Interactive Communication and retrieve the draft later to continue working on it. You can specify a different name for each draft to identify it. For more information, see Save Interactive Communications as a draft.
Adobe Experience Manager Forms has added support for Oracle WebLogic 12 for Adobe Experience Manager Forms on JEE. You can upgrade from a previous version or set up a new Experience Manager 6.5 Forms on JEE server on Oracle WebLogic 220.127.116.11 and later. Later corresponds to the minor version changes, where x in 12.2.1.x is replaced with a version number.
Adobe Experience Manager Forms includes the following accessibility enhancements:
When a user previews an adaptive form as an HTML form, the Scribble Signature field retains the tab focus.
The error messages displayed on submitting an adaptive form now contain the
aria-describedBy attribute. The attribute is attached to the fields referred in the error message. The
aria-describedby attribute indicates IDs of the elements that describe the object. It helps establish a relationship between widgets or groups and text that described them.
If an adaptive form has some mandatory fields, the mandatory attribute is set to
True for such fields in ARIA accessibility schema.
Form data model now supports X-509 certificate-based authentication while using SOAP web services as the data source. For more information, see Configure SOAP web services.
Experience Manager 6.5 Forms on JEE Document Security is now based on Apache Struts 2.
Added support for Oracle Real Applications Cluster (RAC) 19c.
The Generate Printable Output workflow step enables you to integrate a source template file with a data file. This integration enables you to print or save different copies of the template file. The step generates a PCL, PostScript, ZPL, IPL, TPCL, or DPL output. For more information on this feature, see Forms-centric workflow on OSGi - Step Reference.
You can now define the number of columns for a panel in adaptive forms and interactive communications. Switch to layout mode to use the new multi-column option. For more information, see Use Layout mode to resize components.
The new Admin Control option enables the administrators to:
Customize header text and logo.
Control the display of navigation links available in the header.
The Admin Control option is visible only to the members of the
workflow-administrators group. For more information on this feature, see Your Inbox.
Convert a text field in an XFA form to a rich text field in an HTML5 form. For more information, see Designing form templates for HTML5 forms.
Experience Manager Forms includes the following accessibility enhancements:
Screen readers announce checkboxes, links, Date Picker, and Date Input fields correctly in an adaptive form.
Each page of an adaptive form now includes one title and one main landmark label.
You can share your Inbox items with another user. Once another user gains access to your Inbox items, the user can claim and take appropriate action on shared items. Similarly, you can request access to Inbox items from other users. See Share and request access to Inbox items of a user.
If you plan to be out of the office, you can specify what happens to items that are assigned to you for that period.
You have the option of specifying a start date and time and an end date and time for your out-of-office settings to be in effect. You can set a default person to whom all of your items are sent. See Configure Out of Office settings.
You can use the Batch API to produce multiple interactive communications from a template. The template is an interactive communication without any data. The Batch API combines data with a template to produce an interactive communication. The API is useful in the mass production of interactive communications. For example, telephone bills, credit card statements for multiple customers. See Generate multiple interactive communications using Batch API.
Between August 26, 2021, and November 25, 2021, Adobe released the following, in addition to the Service Packs: