Build better products with our product team
Dear Adobe Team,I hope this message finds you well. I would like to propose an enhancement for Adobe Acrobat Reader that I believe would significantly improve user experience and efficiency.Currently, when users open a PDF document, they need to reselect their frequently used tools each time. This can be time-consuming and disrupts the workflow, especially for users who rely on specific tools for their tasks.I suggest implementing a feature that retains the recently used tools when a user reopens a PDF. This would allow users to quickly access their preferred tools without having to navigate through the menu each time.Such a feature would not only enhance productivity but also provide a more personalized experience for users, making Adobe Acrobat Reader even more user-friendly.Thank you for considering this suggestion. I believe it could greatly benefit many users and improve their overall experience with your software.Best regards, Gabriel Eilhardt
Why is this feature important to you:This feature is essential because it improves data organization and management within Adobe Real-Time Customer Data Platform (RT-CDP) when activating datasets to Amazon S3. By allowing separate paths for each dataset, we can ensure more precise data handling. How would you like the feature to work:I envision this feature working by enabling users to define unique paths for each dataset within a connection. When setting up a connect for S3 dataset activation, users should have the option to specify a distinct path for each dataset, allowing for more granular control over data flow and storage. This could be implemented through an intuitive interface where users can easily assign paths during the connect configuration process. Current Behaviour:Currently, RT-CDP does not support separate paths for each dataset under a connect for S3 dataset activation. All datasets are managed under a single path, which can lead to challenges in data organization and management. This limitation makes it difficult to isolate issues and manage datasets independently, impacting overall data governance and operational efficiency. Resulting in creating new connection for a separate path
Description - The challenge lies in the inability to move scenarios in bulk from one folder or team to another within Adobe Fusion. This limitation complicates scenario management, making it difficult to organize and re-structure workflows efficiently. Where we have to either move one by one or by using blueprint. Why is this feature important to you -It will enhances efficiency in managing multiple scenarios. It allows for better organization, quicker restructuring of projects, and easier collaboration across different teams. As teams grow and projects evolve, the ability to easily manage scenarios ensures that resources are optimally aligned and workflows are kept seamless.How would you like the feature to work?Bulk Selection: Users should be able to select multiple scenarios at once using checkboxes or a "Select All" feature within a given folder or team. Then move it to the desitined folder.Current Behaviour - Currently, Adobe Fusion does not allow the bulk movement of scenarios between folders or teams. Each scenario must be moved individually, which is time-consuming and inefficient. This limitation affects workflow organization and complicates the process of aligning scenarios with project or organizational changes.
Request for Feature Enhancement (RFE) Summary: Currently, Smart Tagging in AEM leverages AI to generate metadata for assets automatically. While this increases efficiency, it can lead to irrelevant or inconsistent tagging. Introducing an allow-list would complement the existing block-tags functionality, providing both restrictive (block) and permissive (allow) controls over tag generation.The ask is the Implementation of an Allow-List Functionality for AEM Smart Tagging based on a Dictionary/JSON File. This feature will ensure that only business-relevant tags, as defined by the organization, are applied to assets, enhancing tagging accuracy and consistency. Use-case: Organizations require precise control over the metadata applied to their digital assets to maintain brand integrity, regulatory compliance, and content relevance. For example, a fashion brand may only want tags related to specific product lines, materials, or styles. An allow-list would enable them to define a set of pre-approved tags, ensuring that only relevant tags are applied, avoiding irrelevant or misleading metadata. Current/Experienced Behavior: Currently, AEM Smart Tagging supports blocking specific tags using the block-tags functionality. However, it does not support the enforcement of a strict set of allowed tags. This leads to inconsistent tagging where irrelevant or non-business-related tags may be applied, requiring additional manual cleanup and review.https://experienceleague.adobe.com/en/docs/experience-manager-learn/assets/advanced/blocked-tags Improved/Expected Behavior: With the allow-list functionality, Smart Tagging will reference a pre-configured list (in JSON or dictionary format) to determine which tags are permissible. Only tags included in this list will be applied to assets. This will ensure business relevance and compliance with organizational tagging standards. Additionally, a reporting mechanism will track and log the blocked tags and the frequency of their occurrence, providing valuable insights for content governance. Configuration: Admins can upload a JSON file or define a dictionary in the AEM configuration console. Validation: Smart Tagging compares AI-generated tags against the allow-list before applying them. Fallback Logic: If no tags match the allow-list, the system can be configured to either apply no tags or notify the user/admin for manual review. Compatibility: Works seamlessly with existing block-tags for dual-layer tag management. Environment Details (AEM version/service pack, any other specifics if applicable): Applicable to AEM as a Cloud Service with Enhanced Smart Tagging enabled. This feature should also be compatible with other AEM versions that support Smart Tagging through Content Intelligence APIs, ensuring flexibility across different AEM environments. Customer-name/Organization name: need to check with customer if the name can be mentioned. Screenshot (if applicable): Code package (if applicable):
Our department works with hundreds of companies on projects, shows, and events throughout the year. We create or handle hundreds of videos, graphics, designs, and other files for each event. These files must be shared with various approval teams for each area we are involved in. Our design and production teams operate in both Frame IO and Workfront Proof due to the distinct advantages of each product. Our customers would like a single location, similar to a Frame IO dashboard, where they can preview, see what needs approval, mark up as necessary, and download the finished product from a central location. They want to quickly view the proofing status and action items through a hover feature or side panel. This needs to be consolidated to at least a program level of documents and videos. It must allow for multiple permissions, sharing, and dashboards, enabling the overall project owner to get a high-level overview while allowing individual presentation or activation owners to focus on their specific areas. It should also enable keywords or smart filtering so that the customer can view just a particular format, monitor, or screen content from their dashboard. Security is crucial so other licensed users or clients cannot access it. It should be easy for editors and creatives and non-creatives to upload files to the individual locations, and it would be beneficial if it could integrate with either Workfront Documents, Adobe DAM, or a third-party storage provider to house the files.
It would be great to have the ability to limit the Custom Fields to users (including Group Admin) to use / access by Groups. This will improve the user's experience and allow them to only see Custom Fields that are shared with them and what they see when building reports as well. Similar to not being able to deactivate custom fields as we get more groups report creation is becoming frustrating for users.
The label "Subject" is confusing for the users who are already typing it in a custom form. I want to be able to rename it to better reflect its purpose.
Request for Feature Enhancement (RFE) Summary: We have a requirement, where the authors want by default the folder structure in an alphabetical order while the user is performing any operations such as the "move" operation on files or folders. The current display is not helpful to them to find locations. They also want to default their different views to list in alphabetical order as an option. Use-case: 1. As an author, I want to have the option to view my files and folders in alphabetical order by default, so that I can easily locate areas and not have to change the display to alphabetical each time. 2. As an author, I want to have the option to view my files and folders in alphabetical order by default when performing any operations such as move for example, so that I can easily locate areas. Current/Experienced Behavior: 1. The first time you load the sites or assets experience; you must change to list view and then sort on the column you desire to view in alphabetical order. 2. Anytime you load the sites or assets experience and perform an operation such as move on any folder(s) and/or file(s), you can only view locations in one way (whatever the default list view is here) and there is no way to change it. Improved/Expected Behavior: 1. Once a user sets their view and sort, it remembers the next time. I can set these options somewhere to toggle on/off and select which column to sort by. 2. By default, the locations are sorted by title or name. There should be options to set this or change it here as well while performing any operations on files/folders. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.20 Customer-name/Organization name: TMNA Code package (if applicable):
We are able to upload an attachment to a comment in the "Updates" section on an issue. When we convert this issue to a project, the comment transfers over. However, the attachment does not. The attachment should be transferred over to the project, as well. It is an inconvenience to our users to have to upload this attachment to two comments.
Request for Feature Enhancement (RFE) Summary: Automate TLS certificate renewal Use-case: Imagine you have 20+ different websites running on your AEMaaCS instance, each one with its own domain name, and therefore its associated TLS certificates. Further imagine that there are dev, staging and prod environments, both for preview and publish. Finally, the certificates may not be wildcard certs (*.example.org) but specific subdomain (preview.example.org, preview-st.example.org, ...). So you have easily 50+ certificates to renew, and they will not renew at the same time, but across the whole year. Having to manually renew each certificate is error-prone and time-consuming. Also, in order to do this job, the person needs to have elevated administrative rights, but the job itself does not have a lot of added value. It would therefore be appreciable to automate the renewal of the TLS certificates. In a different environment in the past I was using the certbot tool integrated well with the letsencrypt.org initiative to freely renew certificates every three months. The short duration and the automation ensured the sites remained secure all the time. But this is just an example, other tools and infrastructure probably exist. Current/Experienced Behavior: An administrator needs to manually renew each and every certificate. No added value for a specialist role. There is a chance to forget or to not have the certificate ready leading to browser warnings about an unsecured site, site visitors being worried and potential loss of reputation. Improved/Expected Behavior: Automate the manual process (see use case description). Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: OECD Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: We should have an improved way of authentication and authorization of GraphQL endpoint.In the current design, even unauthenticated or improperly authenticated requests are allowed to hit the endpoint with 200 response code. Instead we should have 401 or 403 response code with proper messages. Use-case: If we are doing any implementation on basis of response code the current implementation will not work as it will always giving 200 as response code. Current/Experienced Behavior: In the current design, even unauthenticated or improperly authenticated requests are allowed to hit the endpoint with 200 response code. Improved/Expected Behavior: If access token is not correct or request is unauthenticated then we should have 401 or 403 response code with proper error messages. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as SaaS Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: I want to be able to migrate content created in each AEM environment (dev, stg, prd) to another environment on the console without going through the package manager. Specifically, I would like to be able to migrate by environment on the content fragment screen. Use-case: Example: It will be possible to migrate a content fragment created in the dev environment to the stg environment on the console. (In this case, the status of the public information will not be carried over.) Current/Experienced Behavior:Content fragments cannot be migrated to a different environment on the console Content fragments cannot be migrated to a different environment on the console Improved/Expected Behavior: Content fragments can be migrated to a different environment on the console Environment Details (AEM version/service pack, any other specifics if applicable): AEM version：2025.1.19352.20250131T194709Z Customer-name/Organization name: Yuki Mama / NTT DOCOMO, INC. Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Better way to create custom AEM components Use-case: One needs to build from scratch a new AEM component Current/Experienced Behavior: In the current AEM world, there are way too often the situations when developers end up building new AEM components (and not use the core components). The experience of building a new component is not very pleasant, prone to human mistakes due to the heavy ponderous coding. Working manually with the XML to define the dialogs makes the developer very often lose focus on the big picture and easy get lost into details about not forgetting to add the well-known <items> element, or to keep track of tabs, or to properly arrange dialog fields, or to make the dropdowns work (specially when we have multiple dependent ones) and so on. All becomes even more complicated when he needs to (also manually) add extra clientlibs having to careful when writing it and not add a typo. On top of this, he often needs to go on the Granite UI Foundation specification page to lookup for the component in question and see what is the overall structure, what attributes it accepts and what they do, and then come back in the XML and manually add what he needs. Currently the Components tool (/libs/wcm/core/content/sites/components.html) is very poor. It is only giving you info data, not giving you much power to edit the component. Improved/Expected Behavior: Have a built-in UI tool to design a component in a more visual way rather then manual XML work, that should do the following: 1. It can be integrated with the available Granite typical components for an easy drag and drop in the dialog design. It can also provide easy access to each Granite component behavior, elements and so on. By having a visual drag-and-drop approach it can prevent developer for breaking the XML. It can contain with hints and documentation tooltips, for ease of understanding and guidance for making best choices 2. It can provide a list of available clientlibs from project for selectionIn this way it will prevent the developer to make typos and not properly link his component to the expected clientlib 3. It can better control granite data, renderconditions, granite classes, *-showhide-target etcHaving a holistic way across the entire dialog will avoid having inconsistencies or mismatches. 4. I can define component title, group, icon, initial field values and so on. 5. It might even allow developer to add a Readme.md file. The readme would contain the component’s documentation (like usage instructions) which can later be used by the editors and developers alike. 6. It might even be able to run the component in isolation, before even include it in project. Here there might be some potential constraints, considering component will run outside project context, so in the real project we might have slightly different results, but this a details left open to be clarified later on. 7. And it can also grow as a tool in the future, to add more component related features. - For example the OOTB Component tool allows you to see where is the component used. But it can do much more, like for example to have an one click away button to update all component instances with the new updated version. 8. It might even had a integration feature with project’s github, so that the component could be directly committed to basecode, once is verified and approved. Currently developers do this in two cumbersome-ish ways: - either create a package, download it, unpack it and put the stuff in the project codebase- or, when the component is already in project basecode, use aemsync to make manual changes on the component in their IDE and verify them in AEM afterwards 9. For now we can keep the HTL out of this tool, even if this could potentially be handled here as well. ------------------------------------------------------------------------------------------------------------------ The solution is not refined in depth, so there is a lot of room to change the idea. But the whole point is that we need a better, safer, easier and faster way to create AEM components. Environment Details (AEM version/service pack, any other specifics if applicable): All new AEM versions (AEM 6.5, AEMaaCS) Customer-name/Organization name: tethich.com Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Making timelines more resilient to heavy workflow activities. Currently timelines timeout because the number of nodes that it has to transvers is over the threshold. We had to purge and reduce our timelines from 30 days to 5 days in order for us to see the timeline results. Use-case: We heavy workflows that causes the timelines to transverse over 30,000 and fail to return results. Current/Experienced Behavior: We expect the OOTB functionality of timelines should work as expected. Which out create custom indexes Improved/Expected Behavior: OOTB indexes should be able used to ensure timeline return in a timely fashion and not timeout. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 SP19 Customer-name/Organization name: Toyota Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: New content fragment editor console doesn't show the "Source Edit" option despite being enabled and visible. It appears correctly on the old/classic console Use-case: Our Content Fragment Model has a multi-line text field configured with default type as "rich text".Under path - /apps/dam/cfm/admin/clientlibs/v2/authoring/contenteditor/editors/StyledTextEditor.jsWe can find source edit under "uiSettings" as seen below - The source edit option appears on the old/classic console - But is missing on the new console - Current/Experienced Behavior: Source Edit option is missing on the new console for editing CF Improved/Expected Behavior: Source Edit option should be displayed on the new console for editing CF Environment Details (AEM version/service pack, any other specifics if applicable): AEM Release - 2025.3.19823.20250304T101418Z Customer-name/Organization name: EPAM Screenshot (if applicable): Above #1 - Content Fragment Model with multi-line field and rich text type selected Above #2 - The old classic console displays the option of "Source Edit" allowing us to write HTML Above #3 - The new console does not show the option of "Source Edit" Code package (if applicable): N.A @kautuk_sahni
Request for Feature Enhancement (RFE) Summary: Ability to use "granite:class" and "granite:data" in the new CF editor Use-case: We developed a show/hide fields plugin for the new CF editor based on a type selection made in a select field. For this purpose we used the example provivided in the docs: https://developer.adobe.com/uix/docs/services/aem-cf-editor/api/data/#setting-styles-to-the-field api.setStyles(fieldName, {"display": "none"}); However, this is not an optimal solution, as we need to hide each field per name instead of creating a generic plugin that could be reused on any content fragment. If we had an option to retrieve the value of a custom data attribute, then our plugin could be reusable. Current/Experienced Behavior: The "granite:class" and "granite:data" set in the CF model is not present in the HTML, and custom data attributes cannot be retrieved by custom plugins. Improved/Expected Behavior: The "granite:class" and "granite:data" set in the CF model is present in the HTML, and custom data attributes can be retrieved by custom plugins. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS, release 2024.10.18311.20241017T104455Z Customer-name/Organization name: Assa Abloy Screenshot (if applicable): Code package (if applicable): <confirmation-title jcr:primaryType="nt:unstructured" sling:resourceType="granite/ui/components/coral/foundation/form/textfield" fieldLabel="Confirmation title" granite:class="mycustomclass" metaType="text-single" name="confirmationTitle" valueType="string"> <granite:data jcr:primaryType="nt:unstructured" mycustomdata="123" /></confirmation-title>
Request for Feature Enhancement (RFE) Summary: Add an API/extension point that would allow developers to change the rootPath for the Asset/CF/Content picker via a JS plugin: https://developer.adobe.com/uix/docs/services/aem-cf-editor/api/ Use-case: Our AEMaaCS project hosts more than 100 websites, each site has its own dedicated root folders for sites and assets (including subfolders for specific content fragment types). We had a custom, JS-based solution in the old CF editor to change the root paths of the CF/Content picker so that when an author opens the picker, it takes him to the correct location by default. This greatly improves the editorial experience of our 700+ authors that work on multiple sites. Current/Experienced Behavior: Asset/CF/Content picker always opens the root folder and editors need to navigate manually to their site and the correct folder. Improved/Expected Behavior: Customization can be enabled to programmatically set the correct root folder via JS, as we cannot do in the generic CF model. This would enable us to improve the editorial experience. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS, version 2024.10.18311.20241017T104455Z Customer-name/Organization name: Assa Abloy Screenshot (if applicable): Code package (if applicable): <story-industries jcr:primaryType="nt:unstructured" sling:resourceType="dam/cfm/models/editor/components/fragmentreference/multifield" allowNew="{Boolean}false" fieldLabel="Industry" filter="hierarchy" fragmentmodelreference="/conf/global/settings/dam/cfm/models/cfm-tag" metaType="fragment-reference" name="storyIndustries" nameSuffix="contentReference" renderReadOnly="false" showEmptyInReadOnly="true" valueType="string/content-fragment[]"> <field jcr:primaryType="nt:unstructured" sling:resourceType="dam/cfm/models/editor/components/fragmentreference" fragmentmodelreference="/conf/global/settings/dam/cfm/models/cfm-tag" name="storyIndustries" renderReadOnly="false" rootPath="/content/dam"> <granite:data jcr:primaryType="nt:unstructured" customCFRootPathFolder="tags/industry" /> </field> </story-industries>
Request for Feature Enhancement (RFE) Summary: The current API and the example shared in the docs to toggle (show/hide) fields in the new CF editor does not work as expected and contains multiple issues. Docs: https://developer.adobe.com/uix/docs/services/aem-cf-editor/api/data/#setting-styles-to-the-field Use-case: We have a few CF models where fields are shown or hidden depending on the type selection an editor makes. After creating a new CF, the editor first needs to select a provider, and then different fields show depending on the selection. Current/Experienced Behavior: While developing a small plugin for the new CF editor to show/hide fields based on a selection according to the documentation provided [1]. Concretely, we are relying on the api.setStyles , but we noticed two bugs:1) This approach works fine for standard input fields, but not for select boxes/enumeration fields, they remain visible even after we try to hide them with CSS display:none2) The standard input fields that do get hidden, but leave a margin that creates unnecessary blank space (this happens because the style is not applied on the container DIV) Improved/Expected Behavior: Fix both bugs and enable plugin developers to properly apply style to toggle input fields Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS, version 2024.10.18311.20241017T104455Z Customer-name/Organization name: Assa Abloy Screenshot (if applicable): Code package (if applicable): api.setStyles(fieldName, {"display": "none"});
Request for Feature Enhancement (RFE) Summary: New permission to remove the replace button on assets. Use-case: We have a lot of squad working in AEMAACS and for some areas we need to have more granularity on the permission, for example some areas can't publish, others can't upload assets and some areas can't replace the assets, so we need to have this permissions on the access control. Current/Experienced Behavior: We don't have this granularity to change this access level. Improved/Expected Behavior: The expectation is to have an access profile created with the “Replace” option profile disabled, in order to eliminate the risk of accidentally replacing the campaign image. We are currently exposed to this risk at all times. Environment Details (AEM version/service pack, any other specifics if applicable): 2025.3.19823.20250304T101418Z Customer-name/Organization name: Santander S.A Screenshot (if applicable): Code package (if applicable):
Zusammenfassung der Funktionsverbesserungsanfrage (RFE): When a component is moved from a container to another container in a livecopy the component appears again after sync. There should be a ghost component to prevent this. Anwendungsfall: If you move a component from one container to another in a livecopy, the component appears again in the original container after syncing with the blueprint.Steps to reproduce:- Create a new page with the template Content Page and open it- Add a Layout Container to the page- Add a component to the layout container (for instance a Text Component) and fill in some text.- Create a LiveCopy of the above page with Standard Rollout Config and open the LiveCopy- Add a second Layout Container to the LiveCopy- Drag (move) the component in the first container to the second- In the page settings synchronize with the blueprint- The component appears again in the first container There should be a ghost component in the first container when the component is moved, but none is created. Aktuelles/erlebtes Verhalten: The component appears again after sync Verbessertes/erwartetes Verhalten: A ghost component should be created in the original container to prevent the reappearing of the component Umgebungsdetails (AEM-Version/Service Pack, ggf. weitere Angaben): 6.5.22 Name des Kunden/der Organisation: Atruvia Screenshot (sofern zutreffend): Code-Paket (sofern zutreffend):
Request for Feature Enhancement (RFE) Summary: For in the loop page template, when user insert any link and provide specific dita file path and click on check icon of link option, its not routing to the provided dita folder.Steps to reproduce:Go to AEM sites https://auth-viewpoint-qa.pwc.com/sites.html/contentAuthor In The Loop Page Template.Add text component and add link by clicking on link option.Select a dita file manually.After selecting click on the tick icon on link option.Check that its not routing to provided dita path.Team, please look into this issue and help us at the earliest to resolve this issueAdobe support ticket : E-001529292 Use-case: Current/Experienced Behavior: link is not routing to provided dita path. Improved/Expected Behavior: its should rout to provided dita path. The cloud version routs to the path properly. We need this facility in non cloud version too Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5Service pack 21AEM Fmdita guides 4.6 Customer-name/Organization name: PwC Screenshot (if applicable): Code package (if applicable):
There are legacy queue topics that should no longer be used but deleting them results in a loss of historical data from already-submitted requests. The ability to deactivate queue topics will allow to toggle them off so that they no longer appear in the lists when submitting new requests to the same queue but will still preserve the queue topic data on the old requests.
Before implementing the Adobe Native Integrator to allow WF documents to write directly to our instanced of Adobe Assets, we could download WF document folders and/or multiple documents at one time. Since implementing, that functionality is lost.The goal of the native integrator was to allow our creative team members to work sole in Workfront. However, now if teams want to access files and bulk download, they must navigate to Adobe Assets to do so. Otherwise, they have to download documents one at a time from WorkFront. This defeats the purpose of finding operational excellence with using the native integrator. We would like the native integrator download to work the same as downloads from documents uploaded directly to WF today. Users should be able to download folders and download multiple files & folders at one time.
Description - Working on monthly scorecards, I need a date range that can always update itself to the report date range, but in the prior year. Would be even better if there was a day-of-week adjusted version, but I would take a "this month last year". This seems very basic for what Workspace should offer. Just a "this date range minus 365" would get me there. Why is this feature important to you - Creating comparison date ranges that can't update themselves and/or have labels that don't make sense to my internal customers means that we are going to have to create the reporting in PowerBI or Excel. How would you like the feature to work - If my panel date is for the month of February 2025, "this month last year" would show February 2024. Current Behaviour - I can create a static date range for this comparison, but it will not update when it's time to update this monthly scorecard for the next month.
We have several directors who all want to be able to track a project in their portfolio, even though it's managed by a different director's team. Only being able to put a project in one portfolio leads to projects being created multiple times so that each director can manage their team members work on the project and it just makes a mess!
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.
