Build better products with our product team
Request for Feature Enhancement (RFE) Summary: Implement PSAs so that they can appear in all of the AEM UIs Use-case: The content operations team is looking to create a PSA or Alert bar/popup that would appear for all/some users on the platform when they log in. Current/Experienced Behavior: Adobe proposed this solution: https://adobe-consulting-services.github.io/acs-aem-commons/features/system-notifications/index.html Results research: I have researched and tried out the ACS Commons System Notifications in the past already. Those only work in the "old" AEM UI, not in the "new" CF Admin/Editor or Universal Editor. So any author directly going into those UIs would never see the notifications. And even authors accessing the old UI might be confused since it disappears on the new UIs. They might think only the old UI is affected by whatever the notification says. Improved/Expected Behavior: 1- it would stay up as long as we need it (if we posted a message about an outage or major incident, we'd want to disable it once the situation was resolved)2- it would be an informative message related to an outage or major incident - example: We’re currently aware of an issue affecting all pre-owned inventory, including Certified Pre-Owned (CPO) pages, on oADD live sites where inventory is not rendering as expected. Our team is actively engaged with our development team to work towards a solution. 3- Permissions: Only admins can create (we need to centralize it and restrict it to one decision making group). 4-This PSA should NOT require developer involvement to create 5- Ability to show it to only specific user groups. For example, we want to show a specific message to French content authors in Canada Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Audi Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: AEMaaCS - CloudManager - Track disk usage Use-case: Ensure that AEMaaCS clients are aware of their disk usage. Especially in times of performance issues, a transparently available monitoring of disk usage would help AEMaaCS projects to improve their setup. Current/Experienced Behavior: There is no disk usage monitoring available in AEMaaCS (in the CloudManager or elsewhere). Without Adobe Support input, a customer doesn't know this parameter. Alternatives via ACS AEM Commons reports are too time-consuming (XLSX work afterwards) or limited in scope (Asset reports only, no other content or full OS). VW's Adobe Ultimate Support recommended I open a ticket here when they couldn't find a suitable functionality in AEMaaCS (E-001835519) Improved/Expected Behavior: In AEM 6.x Cloud Manager, such a feature already exists: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-manager/content/using/monitoring-environments - but there is no similar functionality for AEMaaCS. Expected data (copied from AEM 6.x) Disk Space: The used disk space (in megabytes) for each mount point on the host. There are different metrics for each mount point. At a minimum, there are metrics for / and /mnt, but additional mount point metrics may be available depending on the specific instance configuration. Folder Size AEM Segment Store: The used disk space (in gigabytes) for the AEM Segment Store. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: Volkswagen Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Introduce a visual indicator and count display for hidden components within containers, sections, and background elements in AEM’s page editor interface. Use-case: Content managers need to easily identify and manage hidden components on a page during editing. This visibility is crucial for maintaining content accuracy, avoiding duplication, and ensuring that hidden elements are not unintentionally overlooked. Current/Experienced Behavior: Hidden components are not clearly distinguishable in the AEM page editor. There is no count or visual cue indicating how many components are hidden within a container or section. Additionally, the content tree does not reflect hidden components, making it difficult to locate and manage them across different device views (desktop, tablet, mobile). Improved/Expected Behavior: Display the number of hidden components within each container, section, or background element directly in the edit mode. Show hidden components explicitly in the content tree structure. Ensure this functionality works independently across all responsive views (desktop, tablet, mobile). Provide a toggle or filter to highlight hidden components for quick access and editing. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.22 Customer-name/Organization name: Veeam Software Screenshot (if applicable): Code package (if applicable):
機能改善要求（RFE）概要： Show each item's path in the CF console list ユースケース： We live-copy the master CF to multiple paths. We need a way to find live-copy items other than the master item and to edit or unpublish items only in selected paths. 現在／体験した動作： Even after filtering, numerous items with the same title and identical folder names are shown, making it impossible to identify the item's path. We spend a lot of time each day managing CF. 改善／期待される動作： Show an item's path in the search results, or reveal the path when you hover over the item. 環境の詳細（AEM バージョン／サービスパック、もしあればその他の詳細）： AEM as a Cloud Services 顧客名／組織名 - スクリーンショット（ある場合） コードパッケージ（ある場合）
Request for Feature Enhancement (RFE) Summary: Implement consistent error state styling and behavior for "aem-content" fields in Universal Editor, following the example of "text" fields Use-case: Required "aem-content" field validation in Universal Editor Current/Experienced Behavior: "aem-content" fields lack a red outline, a "red triangle with exclamation mark" icon on the right side of the input box and an aria-invalid="true" attribute. Improved/Expected Behavior: "aem-content" fields have a red outline, a "red triangle with exclamation mark" icon on the right side of the input box and an aria-invalid="true" attribute. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS v2025.8.21994.20250818T175115Z-250700 Universal Editor Service v20250828133131 Customer-name/Organization name: AVIS BUDGET CAR RENTAL LLC Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Display complete configuration values in Cloud Manager. There is no need to truncate the values with (...). Better to wrap at line endings (as is done on the keys). I want to be able to validate/share/document the configuration at one glance without having to open each individual variable. Use-case: Sharing / Documenting Environment configuration Current/Experienced Behavior: Values of environment variables are truncated after n characters Improved/Expected Behavior: Values are displayed in full and wrapped if table width exceeded Environment Details (AEM version/service pack, any other specifics if applicable): Cloud Manager Sep. 22th 2025 Customer-name/Organization name: all Screenshot (if applicable): Code package (if applicable): n/a
Request for Feature Enhancement (RFE) Summary: When the number of configuration variables grows, it could help to order them alphabetically to easily spot if sth. is missing. Also, when a setup contains of multiple modules, ordering would keep items clustered, when prefixed: LOGIN_BAR=..LOGIN_FOO=..WORKFLOW_XX=..WORKFLOW_YY=.. Use-case: Validate environment configuration Current/Experienced Behavior: Variables are mixed randomly, variables with the same prefix are not clustered Improved/Expected Behavior: Variables are ordered by key. Environment Details (AEM version/service pack, any other specifics if applicable): Cloud Manager Sep. 22 2025 Customer-name/Organization name: all Screenshot (if applicable): Code package (if applicable): n/a
Request for Feature Enhancement (RFE) Summary: Keep Side Panel Functional After Page Selection Use-case: AEM Author GUI speed Current/Experienced Behavior: In Sites view, the side panel (Filters, Timeline, References, etc.) can only be used before selecting a page. Once a page is selected, the panel becomes not clickable/useable. Keeping it functional after selection would allow authors to filter, check references, or review details without deselecting the page. Improved/Expected Behavior: Side panel remains interactive after a page is selected Functions such as Filters, Timeline, and References are fully usable while a page is selected Applies in Sites view and similar contexts where the side panel is available Environment Details (AEM version/service pack, any other specifics if applicable): AEM Cloud Customer-name/Organization name: Sanitas Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Enable Side Panel in Image Component Dialog Use-case: AEM Author work speed Current/Experienced Behavior: When editing the Image component, the side panel for browsing and selecting DAM assets cannot be opened. Improved/Expected Behavior: Allowing the side panel to be accessed without closing the dialog would make it easier to choose or replace images directly from the DAM. Environment Details (AEM version/service pack, any other specifics if applicable): AEM Cloud Customer-name/Organization name: Sanitas Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Use-case: In AEM, a proper preview can be generated, but this functionality is missing in Content Hub. Current/Experienced Behavior: Many assets are stored in ZIP file formats, but Content Hub currently displays them as blank folders or icons. Improved/Expected Behavior: need for a feature to generate previews for ZIP files automatically to avoid manual effort Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
To improve clarity for content editors in AEM, consider adding a visual indicator at the top of the page being edited to highlight that the page has been modified post-publication. This would help address the ambiguity that arises over time with the current "last published" and "last modified" dates shown in months in the page properties dropdown. This would make it easier to spot discrepancies—such as when the page was published on the 5th but last modified on the 23rd—without needing to dig into metadata. See screen capture attached.
Request for Feature Enhancement (RFE) Summary: In Cloud Manager, sort Pipelines alphabetically Use-case: In Cloud Manager, sort Pipelines alphabetically to more easily find the pipeline one wants to work on and also prevent from accidentally starting the wrong one (after all, they are usually called similarly, and sorting them top to bottom would make it more apparent, that e.g. lower envs are further up).Example00 - dev - Dispatcher01 - dev - Config 02 - dev - AEM 03 - stage - ... Current/Experienced Behavior: Pipelines are order randomly Improved/Expected Behavior: Pipelines are order alphabetically Environment Details (AEM version/service pack, any other specifics if applicable): latest CM Customer-name/Organization name: any Screenshot (if applicable): Code package (if applicable): n/a
Request for Feature Enhancement (RFE) Summary: In AEM, when creating a translation job via References -> select page, the dialog shows the checkbox “Select all subpages” at the bottom. Currently it’s pre-selected by default. This should be disabled. The checkbox should be unchecked. Use-case: Current/Experienced Behavior: Checkbox “Select all subpages” is checked by default. Improved/Expected Behavior: Checkbox “Select all subpages” is unchecked by default. User can manually check it if they want to include subpages. Environment Details (AEM version/service pack, any other specifics if applicable): AEM Cloud Customer-name/Organization name: Sanitas Screenshot (if applicable): Code package (if applicable):
機能改善要求（RFE）概要： Allow users to set the default editor for opening Content Fragments from Assets ユースケース： Editing Content Fragment 現在／体験した動作： The editing behavior for Content Fragments differs between the New Editor and the Legacy Editor.For example, in the New Editor, you cannot disable inheritance from the live copy source, and you cannot enter external links. However, when editing a Content Fragment from Assets, the New Editor always opens. And you always have to switch editors manually. 改善／期待される動作： Allow users to set which editor opens by default. 環境の詳細（AEM バージョン／サービスパック、もしあればその他の詳細）： AEM as a Cloud Service 顧客名／組織名 スクリーンショット（ある場合） コードパッケージ（ある場合）
Request for Feature Enhancement (RFE) Summary: Our accessibility audit shows WCAG 2.1 AA violations when using placeholders alongside ARIA labelling on Core Form Fields Use-case: Using Adobe Core Form Fields, with ootb configuration "Display help message as placeholder” Example: on page https://www.sunstargum.com/gb-en/about-us/contact-us.html Current/Experienced Behavior: 1. **Accessible name vs description conflict**- Inputs with `placeholder` + `aria-describedby` or visible `<label>` lead to inconsistent accessible name computation. Placeholder either doesn’t get announced (e.g., JAWS, NVDA), or is dropped in favor of description text, making it unreliable :contentReference[oaicite:1]{index=1}.- Relying on placeholder as label fails WCAG 2.1 AA: contrast (1.4.3), persistent visible labels (2.4.6, 3.3.2), Name, Role, Value (4.1.2) :contentReference[oaicite:2]{index=2}.2. **Placeholder distractions**- Placeholder text disappears once typing starts—users lose helpful context :contentReference[oaicite:3]{index=3}.- Placeholder is low‑contrast by default, often failing 4.5:1 contrast ratios :contentReference[oaicite:4]{index=4}.3. **ARIA mismatch with core component settings**- Enabling “Display help message as placeholder” fails to update `aria-describedby` reference, pointing at nonexistent elements and breaking description linkage :contentReference[oaicite:5]{index=5}. Improved/Expected Behavior: Required compliance behaviour:• Inputs need clear programmatically associated `<label>` and persistently visible title.• Use `aria-describedby` for help text only—description must remain tied to a valid element.• Placeholders can provide examples, *never* replace labels, and should not disrupt ARIA structure. Environment Details (AEM version/service pack, any other specifics if applicable): AEM Release 2025.9.22450.20250911T131210Z Customer-name/Organization name: Sunstar Suisse SA Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: In the participant step of workflow. Some use cases where we need to double confirm with warning message. to avoid human error. it is not supported out of the box. By adding another step to confirm it becoming a user experience nightmareMay be a checkbox to ask only for specific participant steps in a workflow Use-case: For example: if approving or publishing we need to double confirm. we need to cancel a workflow and revert to previous version. if user chooses that as the next step by mistake it will revert it and loose the work. Current/Experienced Behavior: it takes the input and moves along. Improved/Expected Behavior: it will would give popup and ask the author to confirm encase of a condition Environment Details (AEM version/service pack, any other specifics if applicable): aem cloud Customer-name/Organization name: jnj Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Automatic Redirects for URL Changes If a page’s URL changes while it is live (due to a title change, page move, or unpublication), could AEM automatically generate a redirect to the new location? Ideally, authors should also have the ability to specify which URL to redirect to (e.g., another page or a 404 page). Use-case: If a page’s URL changes while it is live (due to a title change, page move, or unpublication), could AEM automatically generate a redirect to the new location Current/Experienced Behavior: A page url is changed, we will have to manually use ACS Common Tools to add in a redirect url. Improved/Expected Behavior: Have a list of all redirects If a page’s URL changes while it is live (due to a title change, page move, or unpublication), could AEM automatically generate a redirect to the new location. Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: OneTrust Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Bulk Page Movement Right now, AEM only supports moving one page at a time. This makes taxonomy updates and bulk redirects very time-consuming. Could AEM allow authors to select and move multiple pages simultaneously to streamline these workflows and move it to another location? Use-case: Currently, Adobe Experience Manager (AEM) only allows authors to move one page at a time. This limitation makes it inefficient to perform large-scale site restructuring tasks—such as taxonomy updates, reorganization of content folders, or implementing bulk redirects—especially for enterprise-level websites with hundreds of pages. By introducing a Bulk Page Movement capability, authors could select and move multiple pages simultaneously within the AEM interface. This enhancement would streamline content management workflows, reduce manual effort, and minimize human error during site reorganizations. It would also improve overall authoring efficiency and help ensure faster delivery of structural updates across the website. Current/Experienced Behavior: Right now, AEM only supports moving one page at a time. This makes taxonomy updates and bulk redirects very time-consuming. Improved/Expected Behavior: AEM allow authors to select and move multiple pages simultaneously to streamline these workflows and move it to another location? Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: OneTrust Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Enable the ability to add custom fields to the Content Fragment GraphQL schema via code, SlingDataFetcher, or programmatic means, without requiring changes to the Content Fragment Model definition in AEM. Use-case: Developers and integrators need to expose computed, derived, or integration-specific fields in the Content Fragment GraphQL API for headless delivery, without modifying the underlying Content Fragment Model. Current/Experienced Behavior: The Content Fragment GraphQL schema is auto-generated from the Content Fragment Model and system fields. It is not possible to add custom fields via code, SlingDataFetcher, or other programmatic approaches. Business Impact Limits flexibility for headless integrations, increases maintenance overhead, and requires model changes for every new field, which may not be feasible or desirable in large organizations or for computed/integration fields. Improved/Expected Behavior: Ability to programmatically extend the Content Fragment GraphQL schema with custom fields (e.g., via SlingDataFetcher or similar mechanism), allowing dynamic, computed, or integration fields to be exposed without model changes. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 LTS; Content Fragment Models and GraphQL API; persisted queries; endpoints as described above. Customer-name/Organization name: JPMorgan Chase Code package (if applicable): https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-to-expose-a-custom-resolver-field-in-content-fragments-for/m-p/776485 . I have added the code here
Currently, report prompts are only available at the individual report level. There are many times when team members have wanted to change the filtering/report prompts across all the reports in the dashboard. Adding this feature would be huge. Otherwise, team members are stuck updating the report prompt for each individual report within the dashboard and it is too time consuming to do so.
1) Dimension Value Highlight Visualization DescriptionIt would be great to have a new visualization in Adobe Analytics / Customer Journey Analytics that highlights dimension values. For example, showing which product has the highest conversion rate or which page is the most viewed. The visualization would be similar to a Summary Number or Summary Change, but focused on what rather than how much. Why is this feature important?Currently, summary visualizations are excellent for showcasing key metrics, but they don’t emphasize the specific dimension value driving those results. Having a way to visually highlight the top-performing dimension item would make dashboards more insightful and storytelling more effective. How would you like the feature to work?Users could select a metric and a dimension, and the visualization would automatically display the top (or bottom) dimension value according to the chosen metric. Ideally, it would also support conditional formatting (e.g., color-coding by performance) and allow display of secondary metrics for context. Current BehaviourFreeform tables are useful, but not quite visual. Additionally, there are limitations to create something a bit custom.2) Sentiment Analysis–Style VisualizationDescriptionAnother interesting visualization could be one inspired by Sentiment Analysis — designed to highlight dimension values in relation to a specific metric. It would resemble a scatter plot but use text labels instead of points, making it easier to identify and interpret key drivers at a glance. Why is this feature important?This would provide an intuitive way to analyze performance or perception differences among dimension values (e.g., campaigns, products, or pages) in a single, visually engaging chart. It’s especially useful for understanding “how each dimension feels” relative to a metric. How would you like the feature to workThe visualization could plot dimension values (as text) along two axes — for example, performance vs. volume — and apply color or font size to indicate sentiment, change, or relative importance (or even font size). Hovering over text could show detailed metrics or trends.
We recently found some of our users who have the Workfront App installed within Slack were not able to get any of the backslash Workfront commands to Work. Here are the process steps to solve that problem. Current experience league information advises the user to uninstall the app. What we found to work for us was to revoke their access to the Workfront app within slack. Here are the process steps we followed. Go to slack, under “Apps” click on the “more actions” (go to the right side of the bar, you will see three vertical dots)Select “Manage”Select “Browse apps”In the search bar enter WorkfrontIn the search results select “Adobe Workfront” (it is the second choice)Click on the three vertical dots that appear next to the field labeled ‘VIP’ Select ‘configuration’Enter ‘Workfront in the search bar’, then select ‘Adobe Workfront’Click on ‘Configuration’ Click on “Revoke” Completely close out of Slack Re-open slack and enter any of the standard commands such as /wf help
Our team depends on knowing the priority of a task to know which task to complete first. We use the task priority field to indicate if a task has a hard, soft or urgent deadline. That priority needs to be visible as a column in the My Tasks widget.
In previous "Home" versions, there was this amazing option to undo if you hit "work on it". We send tasks back to "work requests" a lot because priorities shifted and they because "not ready to start" again. It would be so amazing if this came back!We keep having to completely wipe off assignments to force it back. Used to be so quick 😞
We need some sort of warning flag/indicator when a resource is on PTO.When a resource is tagged on a task for a date that is marked as PTO, there needs to be a flag/indicator.When another resources tags a resource in an update/comment when that person is marked PTO, there needs to be a flag/indicator.The fact that workfront does not have that continues to be a major problem for all.You cannot expect someone to check the calendar each and every time. yes we have the ability to auto-assign via Fusion. we do get a warning comment/update but not all of our assignments happen through Fusion. Sometimes we manually assign. Or tasks in current projects are delayed therefore tasks need to be pushed out. And project managers or other resources may tag an assigned resource with information or needing information, we need a flag/indicator that the person is out. It is a CONSTANT MISS in Workfront without this indicator. IT IS A COMPLETELY FAIL ON WORKFRONT as a project management tool.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
