Skip to main content

Ideas

Filter by idea status

10000+ Ideas

JimPresley
JimPresleyLevel 2

AEM Assets - Batch Edit across folders using custom schemaInvestigating

Request for Feature Enhancement (RFE) Summary: Allow Bulk edit against a search result set maintaining selected schema Use-case: I filter for specific files, and I wish to batch edit fields in the result set of that search.  Presently, If the result set of assets are located in different folders, the schema displayed is the OOTB basic schema, not the custom one we use.  I'd like to do a search for assets that contain specific metadata, then bulk-update the result set of assets.  That result set is spread across multiple (hundreds) of folders.  I can't do an export csv function against assets in multiple folders as that function is only available against a single folder and its subfolders.  Current/Experienced Behavior: What I do now, is select the top most folder, then export csv (that contains all files in and under that top folder including subfolders, then pull it all into a spreadsheet to parse for the files I need to modify, make the modifications in the spreadsheet, then upload as a metadata update.    The flexibility of doing a metadata export against a search result would be extremely useful. Improved/Expected Behavior: Time, accuracy, consistency Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: Nordstrom / PMO Screenshot (if applicable):   Code package (if applicable):  

UnjiBaAdobe Employee

Enable IP Allow List Support for Content Hub Delivery EndpointsInvestigating

Request for Feature Enhancement (RFE) Summary: Based on the customer’s internal IT policy, it is required to restrict access to Content Hub endpoints using an IP allow list, similar to the current IP-based access control available for AEM Author (DAM). Without this capability, there is a significant risk that the customer will be unable to adopt Content Hub in their production environment due to internal security compliance requirements. Use-case: The customer utilizes AEM Assets and Content Hub to share content with both internal teams and external agency users. For security and compliance reasons, access to internal content must be restricted to pre-approved IP addresses. While AEM Author supports IP allow list configurations, Content Hub delivery endpoints are currently publicly accessible and do not support the same level of access control. The customer requires the ability to limit access to Content Hub by IP to align with internal security policies. Current/Experienced Behavior: Content Hub delivery endpoints (e.g., *-delivery) are publicly accessible by default. There is no configuration available to apply IP allow list restrictions specifically for Content Hub. IP restrictions set on AEM Author do not apply to Content Hub endpoints. Improved/Expected Behavior: Content Hub should support IP allow list functionality, allowing administrators to define which IP ranges are permitted to access delivery endpoints. If a user attempts to access Content Hub from a non-approved IP, the system should block access and return a 403 error. Ideally, this feature would also allow for different IP configurations for internal users and external partners. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service     Screenshot (if applicable):   Code package (if applicable):  

dmescia2
dmescia2Level 4

Can we have nested Namespaces in AEM?Investigating

Request for Feature Enhancement (RFE) Summary:   Use-case: We have built a taxonomy in our AEM DAM based on custom fields for search, filtering and reporting. We are using a namespace to bucket all of these tags as a top level bucket. Under that we have built out the tag structure for the rest of our taxonomy. The first level of those tags is a category which pairs up to a custom field used for search. These tags are technically "buckets" as well. We would like to set these up as namespaces as well but have them be children of the overarching namespace for our organization? So the structure would look like this:organization-namespace:category:tag-level-1/tag-level-2 Current/Experienced Behavior: We have a namespace to bucket all of our custom tags as a top level bucket. Under that we have built out the tag structure for the rest of our taxonomy. However, the first level of those tags is a category which pairs up to a custom field used for search. Improved/Expected Behavior: We would like to set these up the second level "buckets" as namespaces as well but have them be children of the overarching namespace for our organization? It'll be so much cleaner if we can have all of our tags in one place at the top instead of spread out among 20 or 30 separate namespaces at the root level. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud most recent version Customer-name/Organization name: Enterprise Mobility Screenshot (if applicable):   Code package (if applicable):  

Garima21Adobe Employee

Process for Sonar Rules Update in Cloud ManagerInvestigating

Request for Feature Enhancement (RFE) Summary: Sonar ruleset significantly influence BMW's development workflows. To ensure smooth integration and minimal disruption, it is essential that any changes to these rules—including minor adjustments—are communicated in advance. Developer teams require early access to updated rule definitions so they can validate their code against them before the changes are enforced in Cloud Manager pipelines. Use-case: BMW experienced a situation where a previously successful pipeline began failing overnight due to newly detected Sonar vulnerabilities, despite being based on the same commit. This indicates that the Sonar ruleset had changed unexpectedly from one day to the next. Given BMW’s multi-project setup—comprising around 10 interdependent projects managed by different development teams—each project is built through its own pipeline. As a result, a Sonar scan failure in any one pipeline can have a significant ripple effect across the entire development landscape. Current/Experienced Behavior: A Sonar scan failure in any one pipeline can have a significant ripple effect across the entire development landscape. Improved/Expected Behavior: To ensure smooth integration and minimal disruption, it is essential that any changes to these rules—including minor adjustments—are communicated in advance. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: BMW AG Screenshot (if applicable):   Code package (if applicable):  

dmescia2
dmescia2Level 4

Can we update the way folders and assets are handled in AEMInvestigating

Request for Feature Enhancement (RFE) Summary: I would like to see more of a separation in how assets and folders are managed in AEM. They are both managed the same way in 2 separate spaces, the assets pane and teh content tree. I would like to see the content tree be the space for managing folders and the assets pane be the space to manage assets. Use-case: Admin users managing assets are creating a folder structure with multiple nested folders to keep things organized. In this use case we'll use brands and lines of business. We have assets that are are for a specific brand Current/Experienced Behavior: Admin users managing assets are creating a folder structure with multiple nested folders to keep things organized. There are folder based profiles added to those folders including tags that are applied to any assets added to those. We also created a workflow that will copy tags down from parent to child so those tags aren't overridden by subfolder tagging.   In this use case we'll use brands and lines of business. We have assets that are are for a specific brand. They are placed in the folder for that brand and the metadata from the folder based profile is applied. There are multiple lines of business that fall under that brand and there is a folder for each one of those in there as well with a folder based profile added and specific tags for those. Assets are added to those and the tags are automatically applied.    This workflow is working fine, however, it leaves us with folders living among a sea of assets. When navigating the DAM via folder structure it becomes very difficult to sift through when there are hundreds (sometimes thousands) of assets surrounding the folders. If I have to update permissions or profiles for specific folders its either confusing (scrolling) or clunky (filtering on folders) to find the folder. Improved/Expected Behavior: I would like to be able to manage all of my folders in the content tree space. Create folders, select and get info, add folder based metadata, etc. And I'd like to be able to manage my assets in the asset pane.Create assets, select and get info, add asset based metadata, etc. Environment Details (AEM version/service pack, any other specifics if applicable): We are on the most current Assets as a Cloud Service environment. Customer-name/Organization name: Enterprise Mobility Screenshot (if applicable):   Code package (if applicable):