Product ideas | Community
Skip to main content

Ideas

Filter by idea status

10000+ Ideas

Hide field choices on certain custom formsNew

I believe I have seen this in another thread somewhere and wanted to check on it to see if there have been any updates around this feature but can't seem to find it.. This would be a HUGE win for us if this functionality was possible.   Description - Ability to utilize the same 'multi-choice' field on multiple custom form hiding certain choices.    Why is this feature important to you - We use the same "Asset Type" dropdown field across all of our different custom forms so that we can easily report on this data, however not all Asset Types should be an available option across all forms. For example:    How would you like the feature to work - Example: On Custom Form 1 we would like the 'Asset Types' dropdown to include Print, Email, Social, Web as options to choose from. On Custom Form 2 we would like to hide Web as an Asset Type for them to choose, and only display Print, Email, Social.    Current Behaviour - Currently (to my knowledge), you cannot hide any options without it hiding on ALL custom forms. We have to create workarounds on each form where (ex.) Web is chosen as an Asset Type on Custom Form 2, we populate descriptive text that says "Sorry this is not an available option, please de-select this choice". However, this is not always a successful method because the form still allows you to Submit, so if a requestor purposely ignores it, or selects multiple Asset Types in which they may miss the message and continue with the form- it causes more work and aggravation on the team to have to reach out and let them know they cannot request that in which we receive a "well why is it an option then?" response 🙂 We are trying to avoid creating multiple versions of the same field so that we can pull clean reporting.     

whatever2000New Member

EDS - Universal Editor - Create Experience Fragment from BlocksNew

Request for Feature Enhancement (RFE) Summary: - AEM EDS Integration (cross-walk) for Adobe Target is currently very limited. - Clients heavily use the long existing feature, to upload experience fragments, created in AEM to the Adobe Target server for personalization usage. - This is currently a broken workflow in EDS cross-walk, as one can not create Experience Fragments from EDS Blocks - That's why - on behalf of our client DVAG - we request to have the possibility, to create Experience Fragments from EDS Blocks in the Universal Editor in order to export and update those to and on the Adobe Target Server in order to run A/B Tests and personalized Experiences in Adobe Target with provided Experience Fragments Use-case: 1. Editor creates Experience Fragment from EDS Block in Universal Editor (see provided draft image) 2. Editor creates variants of this Experience Fragment (existing feature for classic AEM Components) 3. User uploads the Variations to Adobe Target Server (existing feature for classic AEM Components) 4. User can change the Variants and update those in Adobe Target Server if ExF was already uploaded to Adobe Target before (existing feature for classic AEM Components) 5. The ExF's made available with this workflow are not ready to be used in Adobe Target VEC and also Form based (existing feature) Current/Experienced Behavior: 🔴 Currently it is not possible to create ExF's from EDS Blocks Improved/Expected Behavior: Creating editable ExF's from EDS Blocks is possible and consecutive handling of existing features like Uploading and syncing with Adobe Target Server is possible Environment Details (AEM version/service pack, any other specifics if applicable): Lates AEMaaCS - nothing specific Customer-name/Organization name: DVAG - Deutsche Vermögensberatung Aktiengesellschaft Screenshot (if applicable): provided in file upload Code package (if applicable): not applicable

Collections - improve usability and hygieneNew

Request for Feature Enhancement (RFE) Summary:   Use-case:   Current/Experienced Behavior: As the number of created collections continues to grow, we’re observing some usability and maintenance challenges. Please refer to the attached recording for reference.   Key Issues: Difficulty for users to find or filter relevant collections Increasing need for better maintenance and hygiene of collections in AEM Assets Improved/Expected Behavior: Filter Option: Public vs. Private Collections Allow users to filter collections by:      Public (shared)      Private (created by the user) This would simplify navigation and reduce clutter in the list view.   Expiration Date for Collections Enable users to set an expiration date when creating a collection. After expiry, the collection could either:      Be automatically deleted, or      Moved to an Archived state for review before deletion   Bulk Management Capabilities Provide tools to:      Select and delete/archive multiple collections at once      Assign or update metadata like owner, expiration, or tags in bulk   Owner/Creator Information Display Display the collection creator’s name in the list view, to help teams manage ownership and follow up with the right person.   Usage Insights / Last Accessed Date Add metadata showing when a collection was last accessed or used. This helps in identifying inactive collections for cleanup.   Environment Details (AEM version/service pack, any other specifics if applicable): AEM Cloud service (Assets or Admin view) Customer-name/Organization name: HUGO BOSS Screenshot (if applicable):   Code package (if applicable):  

juhujkddASNew Member

Enhanced content copy of large content set or packagesNew

Request for Feature Enhancement (RFE) Summary: Feature Idea:Adobe Content Copy Tool (CCT) Enhancements - Enhance the Adobe Content Copy Tool (CCT) to improve performance, usability, and flexibility for handling large content sets, environment constraints, and exclusion rules. Use-case: Syncing a large amount of content between different cloud environments Current/Experienced Behavior: The CCT is not practical for back-staging large content sets; it takes an excessively long time and often does not finish when handling large amounts of content. Content cannot be copied from lower environments to higher environments. The tool cannot be used if another pipeline is currently running in the same environment. No support for wildcard-based exclusion or inclusion patterns in content sets (e.g., excluding all subdirectories under a given path using regex or wildcards). Building packages in crx/packmgr works but has a timeout of 10 minutes which makes it hard to split content up in small enough packages Improved/Expected Behavior: Performance optimizations to allow faster and more reliable copying of large content sets. Enable content copying from lower environments to higher environments. Allow the tool to function concurrently with other running pipelines in the same environment. Introduce wildcard-based includes/excludes for content sets (e.g., support for patterns such as "modifier": "exclude","pattern": "/content/experience-fragments/heliux/adhesive/pro-now/language-masters(/.*)"). Environment Details (AEM version/service pack, any other specifics if applicable): 2025.3.20133.20250325T063357Z Customer-name/Organization name: Henkel AG & Co. KGaA Screenshot (if applicable):   Code package (if applicable):  

lutzULevel 4

Translation Framework | Improve create process with link to corresponding projectNew

Request for Feature Enhancement (RFE) Summary: Give the editor who creates a translation project the option to switch easily with one click to the project which has been created. Use-case: As an editor I wanted to have a efficient way of working once I want to sent my page out for translation. I create the page in the source language and with only some clicks without leaving the Sites console I want to start the translation job. Current/Experienced Behavior: If I am in the editing mode of my source page I can not start a translation job (btw. Lionbridge connector offers that option in the page menu), so I have to switch to the Sites Admin. Here I create the translation project via the left rail but after creating, system just says "Project created". I have to switch to Projects, look for the project created and start the translation. This is not a fluent way of working and not efficient!I have attached a screen recording to make it clearer. Improved/Expected Behavior: To improve the current situation the hint which pops up, telling you that project has been created successfully, should contain a link to the created project so that the editor just can click on it to open the project where he can also start it.And, in the left rail there could be a new category be introduced which shows the project in which the selected page is included. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: Carl Zeiss AG Screenshot (if applicable):   Code package (if applicable):