Adobe Experience Manager

Request for Feature Enhancement (RFE) Summary: Determining the content of zip files solely from their title or file name can be challenging. It would be beneficial if marketers could attach images to the zip files (for thumbnails), as this would enable quicker visual identification. Use-case: Visually identifying the content of a ZIP via a thumbnail Current/Experienced Behavior: All zip files has same generic thumbnail. Thus, marketers need to check read through Titles/names. Improved/Expected Behavior: Associate Image with a ZIP to identify contents by looking at the thumbnail Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5/Cloud Customer-name/Organization name: Mondelez Screenshot (if applicable):   Code package (if applicable):  

We are on AEMaaCS, we are working on introducing msm in our experience fragment hierarchy, we have created an xf in language masters in /content/experience-fragments/myProject/language-masters/en/header, now as it happens in site pages when we roll out a page from language masters, it automatically creates a live copy in /content/myProject/en/en_US, but in case of xf we have to manually create a live copy using create button, is there a way to automate this like it is there in sites pages.

Cloud Manager’s Content Sync capability is an important tool for keeping lower environments aligned with production. However, in its current form, the process can feel unnecessarily broad in scope and operationally inefficient. I believe there are several enhancements that could make the feature significantly more effective, flexible and performant.Intelligent indexing and comparison A valuable improvement would be the introduction of an indexing or comparison mechanism during content sync execution. At present, the process appears to operate as a full content copy. In scenarios where Production and Pre-Production both contain large volumes of content — for example, 10,000 files in each environment — it would be far more efficient to compare the target environment against the source before initiating the transfer. Such a mechanism could assess whether each file already exists in the target environment in an identical state. Where no difference is detected, the file could be excluded fr

Hi Everyone,Recently, Adobe shipped a feature (SITES-33594) that enables out-of-the-box OIDC support, removing the need for custom authentication handlers. While this works well for standard flows, we’ve encountered a limitation when integrated with Identity Providers like Okta.The Issue:When implementing RP-initiated logout, Okta (and similar providers) requires the id_token_hint=<id_token> request parameter to successfully terminate the session on the IDP side.Technical Gap:Currently, org.apache.sling.auth.oauth_client.impl.SlingUserInfoProcessor is only designed to store the access_token and refresh_token on the user node. Since the ID token is not persisted, we cannot retrieve it to complete the logout handshake OOTB.Requirement:We need a standardized process within the OIDC implementation to store and access ID tokens on the user node, similar to how access and refresh tokens are handled.Thanks,Martin

In the AEM Assets Omnisearch UI, when a user opens the filter rail and selects any filter (file type, date range, tags, etc.), a search is automatically triggered on every single filter interaction. This causes: Multiple overlapping HTTP search requests fired in rapid succession Server-side query timeouts under normal DAM load UI freezing while waiting for responses Users unable to combine multiple filters before seeing results Required behavior: User selects multiple filters freely without any search firing A custom "Execute Search" button is visible in the filter rail Search only fires when the user explicitly clicks "Execute Search" This is a production workflow issue affecting all DAM users performing filtered asset searches.

Packaging design plays a crucial role in shaping customer perception and influencing buying decisions. A well-designed package not only attracts attention but also communicates the brand’s identity effectively.Here are a few important benefits of strong packaging design:Enhances product visibility on shelves Builds brand recognition and trust Creates a memorable unboxing experience Helps differentiate from competitorsAt Design Concepts Creative, we focus on creating packaging that not only looks appealing but also drives real business results.You can explore some of our recent packaging design projects here:👉 our packaging design portfolio

Request for Feature Enhancement (RFE) Summary: Standardize the time zone display for workflow-related “Start Time / Start Date” across all AEM as a Cloud Service authoring UIs (Workflow console and Inbox) so that they are consistent and user-friendly for business users. Use-case: Business users frequently monitor and operate workflow instances (e.g., publication approval flows) from the AEM author UI. Currently, the “Start Time / Start Date” of the same workflow event is displayed in different time zones depending on the screen: • Workflow instance list vs. workflow instance history • Inbox list vs. Inbox item detail This inconsistency causes confusion for operators, makes it difficult to correlate events between screens, and increases the risk of miscommunication when discussing schedules (e.g., “when was this request actually started?”) with non-technical users. This affects daily operational work for multiple business users who coordinate publicat

Request for Feature Enhancement (RFE) Summary: Make it possible to hide the video download button. Use-case: If you embed a video directly instead of using a YouTube video Current/Experienced Behavior: The options menu will always be displayed. Improved/Expected Behavior: You can toggle the display of the options menu. Environment Details (AEM version/service pack, any other specifics if applicable): Experience Manager as a Cloud Service Customer-name/Organization name: asahi kasei Screenshot (if applicable):   Code package (if applicable):    

Request for Feature Enhancement (RFE) Summary: It will be possible to set links from the same domain to open in a new tab. Use-case: When setting up a link within the same domain Current/Experienced Behavior: It's not possible to determine whether the `target=_blank` setting is enabled or disabled, so transitions within the same domain always result in transitions to the same tab. Improved/Expected Behavior: You can toggle the setting of `target="_blank"` for each link. Environment Details (AEM version/service pack, any other specifics if applicable): Experience Manager as a Cloud Service Customer-name/Organization name: asahi kasei Screenshot (if applicable):   Code package (if applicable):    

When we add new assets into the DAM the system creates renditions of those assets for use by AEM. We also create custom renditions for use by our users. When users view and asset or click to download it they see all of our custom renditions PLUS the system renditions. Given that the system related renditions are soley for the use of the AEM platform, can we please hide those from our view so they are not noise for our end users?

This is a Feature Enhancement request to add a collapsible Hamburger menu or similar for the various options for Asset Details in Assets UI. Currently a user has to hover over the button to figure out what the icon means. The same is applicable in order to view a datapoint quickly for example, Dynamic Media URL, for an approved asset.

  @tushargu@adobe.com @karmakar@adobe.com @carltonr@adobe.com Request for Feature Enhancement (RFE) Summary: Publish assets to the preview server Use-case: The requirement is to build an EDAM where all the assets reside. A key requirement for image management is the ability to expose an image for internal preview by other users/systems, without exposing the image publicly. Current/Experienced Behavior: Currently, there is no way to publish assets to the preview server for Assets customer. Improved/Expected Behavior: We would expect there to be an OOTB way to directly publish assets to the preview server. Environment Details (AEM version/service pack, any other specifics if applicable): Adobe Experience Manager as a Cloud Service Customer-name/Organization name: Starbucks Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: AEM Core components should have common and generic features, including accessibility. It appears that ARIA Attributes are not implemented in AEM Core ComponentsTeaser ComponentLooking at AEM's teaser component documentation, which showcases screenshots from author, the only accessibility field Adobe have is for the "alt" property.• Teaser Component (https://experienceleague.adobe.com/en/docs/experience-manager-core-components/using/wcm-components/teaser)When I look at Adobe example output (the Markup tabs under each section) and look at the sections with anchor links, I do not see any ARIA attributes either.• AEM Core Components - Example Output - Teaser Component (https://aemcomponents.dev/content/core-components-examples/library/core-content/teaser.html)Button ComponentOn the other hand, looking at AEM's button component documentation, Adobe DO provide an aria-label field for authoring.• Button Component (https://experienceleague.adob

Request for Feature Enhancement (RFE) Summary: Enable log collection from Adobe Experience Manager (AEM) in Dynatrace as part of the monitoring integration Use-case: We have successfully integrated Dynatrace with Adobe Experience Manager (AEM) for performance and application monitoring. However, the current integration does not support log collection from AEM servers. Having the ability to collect and analyze logs directly within Dynatrace would significantly enhance our monitoring and troubleshooting capabilities. Current/Experienced Behavior: Dynatrace is integrated with AEM for monitoring, but logs from AEM servers are not being collected, as this feature is not supported. We previously created a support ticket about this, and we were advised that currently, there is no solution for log collection through Dynatrace in AEM Improved/Expected Behavior: We expect Dynatrace to support log collection from AEM servers, in addition to the existing monitoring features. This would al

Today: In the web UI, to create a new version of an existing asset, the uploaded file must have the same filename in the same folder. If the filename is different, AEM treats it as a new, separate asset, not as a version.Desired behaviour:New versions of an asset can be added regardless of the file name, e.g. by selecting the asset and clicking “add new version”.Reasoning:Updated files often come with new names but should still be stored as versions of existing assets. E.g. if a legacy asset was uploaded (or migrated from our old DAM) with the file name: coporate-presentation-2022-v1.ppt, I want to be able to upload a new version that is called hbk-coporate-presentation-2026.ppt We are not starting a DAM from scratch or renaming 30,000 files. That means that even though we can update to newer versions in AEM Assets, any errors, bad naming or typos in old file names get carried over into the new version. When users download the updated file, it has the file name of the first version, e.

Currently only V8 is supported which don’t bring any advantage in compression/file-size compared to MP4/H.264Here are some requirements for Assets/Dynamic MediaDynamic Media accepts WebM/VP9 video files during the asset upload process  WebM/VP9 assets are automatically ingested into the Dynamic Media processing pipeline and appear in the DAM with correct metadata (resolution, frame rate, duration, codec). Video Profiles in Dynamic Media include WebM/VP9 as a transcoding output format with configurable bitrate, resolution, and quality settings. Dynamic Media delivers WebM/VP9 video via adaptive streaming to supported browsers, with automatic fallback to MP4/H.264 for non-compatible clients. Asset processing status (pending, processing, failed, ready) is correctly reflected in the AEM DAM interface for WebM/VP9 files. Published WebM/VP9 assets are delivered through the Dynamic Media CDN with proper cache headers and MIME type (video/webm).

Request for Feature Enhancement (RFE) Summary: Download Button for Sites page in AEMaaCS Use-case: This product enhancement request is to be able to download an image (pdf, gif, jpeg, etc.) from the preview page of a Sites page in AEMaaCS Sites. Current/Experienced Behavior: This is a requirement for larger multi-level organizations (in this case a large Adobe retail customer), which have Third Party & VPs/Executive leadership that do not normally access or do be granted access to go into AEMaaCS to view or approve a campaign. Thus, exporting the Site page from the preview page is a critical step in the approval process. Currently, there is no built-in functionality to download an image/PDG of a Sites page in AEMaaCS Sites. Improved/Expected Behavior: The scale of which the Adobe Retail customer plans to be creating emails and other marketing materials in AEMaaCS makes it unreasonable to go through a multi-step process in order download an image of a marketing component.

**This is an AEM Assets idea and is being temporarily moved to AEM Sites** We have a legal/compliance requirement to store all our iterations/versions of our documents. In addition to retaining them for an indefinite period, we need to be able to view the various iterations/versions & markups (created via Adobe Acrobat) that have been created during the document creation & approval process of the document. I loaded a couple iterations of a document that had 7 iterations/versions created in another content management tool (again, markups created via Adobe Acrobat) and tried to access the prior iterations in the timeline preview but do not see the markups in the preview. I double-clicked on the current document and do see there are markups, but you can’t select them or hover over them to see the actual markups. We need an easy way to view all iterations/versions of a document and be able to see the markups made from version to version. 

Field Content Request for Feature Enhancement (RFE) Summary: Allow defining custom 404 pages per specific page or directory (path) so that only the designated scopes show a tailored 404, different from the site-wide default. Use-case: When users access 404s under landing pages (LPs) or other special sections, the site owner needs to show a section-specific 404 that provides targeted guidance (e.g., relevant links, promotions, or contact paths) appropriate to that section. Current/Experienced Behavior: It is not possible to create a dedicated 404 page for a specific page or directory. All 404 responses fall back to the global default, which cannot convey section-appropriate guidance. Improved/Expected Behavior: Enable configuration to display a unique 404 page only for the specified page/directory scope, while keeping the default 404 for other areas of the site. Environment Details (AEM version/service pack, any other specifics if applicable): Experience Manager as a Cl

Field Content Request for Feature Enhancement (RFE) Summary: Provide a Page List block that allows filtering by a specific path × specific directory, and supports listing non-HTML items such as PDF files and external links. Use-case: Content authors need to easily create lists such as news, column, and article indexes based on specific directories, and include non-HTML items (PDF files, external URLs) within the list. Current/Experienced Behavior: 1. It is currently not possible to generate a page list filtered by a specific path × specific directory. 2. Authors cannot easily include PDF files or external links in lists such as news indexes without creating dummy pages and setting manual redirects. As a result, page lists cannot naturally contain mixed content such as pages, PDFs, and external URLs. Improved/Expected Behavior: 1. Enable authors to generate a page list by specifying a directory × tag (or equivalent filtering criteria). 2. Allow authors to add PDF files

Request for Feature Enhancement (RFE) Summary: Improve the Columns block so that (1) opening Column properties immediately after adding a Columns block does not cause errors, and (2) components inside Columns can be moved freely between Columns blocks or between Columns and Section containers. Use-case: During authoring, editors frequently add Columns blocks and adjust Column properties before placing content. They also often reorganize page layouts by moving components such as Text or Button between Columns, or between Columns and Section containers. Current/Experienced Behavior: 1. Immediately after adding a Columns block, opening the Column properties before adding any inner content results in an error. 2. Components placed inside a Columns block cannot be moved to another Columns block or to Section containers, limiting layout flexibility and forcing authors to recreate content manually. Improved/Expected Behavior: 1. Column properties should be accessible without error

Feature Request | Allow exporting DAM usage reports from Assets View and Admin interface so that users (end user or admin) can export DAM usage reports and are able to share, analyze, or archive reporting data offlineReports can be exported from: Assets View page Admin interface Export reflects: Selected time period Applied filters Upload and download metrics Supported export formats include: CSV (mandatory) XLSX (optional / nice-to-have) Export includes metadata such as: Report generation date Generated by user Exported data matches exactly what is displayed on screen.

Currently Asset reporting statistics available only in Asset View interface. Enable admin users to access DAM usage reports from the Admin interface without needing to switch views so that  they can analyze assets usage across teams, brands, and regions.Admin users can access reporting from the Admin interface. Admin can view the same metrics as end users: Uploads Downloads Admin can apply all supported filters: Time period Brand, Sub-brand, Geo/OU, Agency, Adaptations, Master, Experience Admin visibility supports broader organizational scope (subject to role configuration). Reports load within acceptable performance thresholds for large data sets.

Request for Feature Enhancement (RFE) Summary: We would appreciate a capability in the Image component (including Hero/Carousel) to configure different images for desktop and mobile. Use-case: Authors set key visuals per device so that content remains legible and complete on smaller screens. Current/Experienced Behavior: It is not possible to switch images between smartphone and desktop. As a result, text in images may become unreadable on small screens, and key content can be cropped or cut off on mobile. Improved/Expected Behavior: Allow configuration of separate images for desktop and mobile. If either is not set, fall back to a common image for both. This would directly improve UX and reduce operational work, which would be very helpful. Environment Details (AEM version/service pack, any other specifics if applicable): Experience Manager as a Cloud Service Customer-name/Organization name: asahi kasei Screenshot (if applicable):   Code package (if applicable):

Field Content Request for Feature Enhancement (RFE) Summary: We would be grateful for a feature to automatically retrieve the target file size and optionally display it in the link text (with an ON/OFF toggle). Use-case: When authors create links to files (e.g., PDFs), showing the file size in advance helps users make informed decisions (e.g., considering mobile data). Manual entry is time‑consuming and error‑prone. Current/Experienced Behavior: Automatic retrieval and display of file size is not available. Although displaying size improves usability (prevents unnecessary downloads and supports user decision‑making), maintaining sizes manually incurs operational cost and inconsistency risks. Improved/Expected Behavior: Automatically fetch the target file size and display it in the link text (with the ability to toggle display ON/OFF). This would stabilize operations and reduce effort—very helpful for large sites. Environment Details (AEM version/service pack, any other s