Product Communities

Request for Feature Enhancement (RFE) Summary: I would like to change the backend storage of assets based on its metadata while keeping the assets where they are in the DAM.  Use-case: I would like to set up a property called Archive with a yes checkbox. When the box is not checked the asset is stored in active storage on the backend. When the status box is checked the asset is moved to glacier storage in the backend. So the asset stays in the same location in the DAM interface but the storage of it on the backend is dependent on the metadata in one of the properties. Current/Experienced Behavior: Archived assets are moved to a folder and all assets in that folder get moved to glacier storage on the backend. Improved/Expected Behavior: Backend storage is based on the metadata of an asset instead of what folder it is in. Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Dario Mescia/Enterprise Mob

Request for Feature Enhancement (RFE) Summary: Display jcr:score next to result path in Query Performance Use-case: When using Query Performance to analyze a query sorted by jcr:score, it would be very useful to display for each of the result its jcr:score generated during the query execution.That would allow better understanding of the final results whenever query results are sorted by jcr:score and also make index management and lucene boosting evolutions much more predictible. Current/Experienced Behavior: Currently, only the paths of the results are displayed. Improved/Expected Behavior: With this feature, there would be two, one for the asset paths and one for the jcr:score Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: Benjamin Jacquet / Accor Hotels Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Enable customers to programatically create task for the Asset Essentials task board Use-case: Upon asset expiry, we want to automatically create a task to the asset creator's task board in Asset Essentials. The asset creator needs to take action (re-approval, retire, etc.) which will be performed through an App (built using App Builder). Current/Experienced Behavior: No API exists allowing us (customers) to create tasks programmatically which are available to users in their task board Improved/Expected Behavior: Have the ability to create tasks programmatically (through the internal Collaboration API) Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service Customer-name/Organization name: Pfizer Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Due to the volume of assets, a search function is being requested to be added when viewing the Columns. Use-case: Destination Pet has so many assets loaded that users are unable to narrow their search when using the Columns view Current/Experienced Behavior: Search only exists in List view Improved/Expected Behavior: Be able to search in Columns view Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: Destination Pet Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: All users, admin and non-admin, in the organisation are receiving multiple notifications based on activity in the Asset Contribution Folders within our Brand Portal environment. This has created a significant number of email 'notifications' and there is no way to disable this currently for non-admin users. Please refer to the previously raised ticket: E-001726839 Use-case: Due to the current process and not being able to disable these notifications for non-admin users, we have less control of what is being notified on or being sent to non-admin users. This is a risk for our external stakeholders also as we don't want to notify them of every update in our system. Current/Experienced Behavior: Current experience we have no control of notifications being sent to non-admin users Improved/Expected Behavior: Being able to have full control over what information and notifications are being sent to which users Environment Details (

Request for Feature Enhancement (RFE) Summary:   Use-case: Composite metadata is needed for store information which follows a Map format. Like: - key1: val1, val2 - key 2: val2, val3, val4 .... key n Current/Experienced Behavior: Composite metadata is only available for Pages. Improved/Expected Behavior: Composite metadata should also be enabled for Assets Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 Customer-name/Organization name: Mondelez Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary:   Use-case: Editors need the possibility of moving folders and removing in case of making a mistake. Current/Experienced Behavior: Folders in the new Content Fragment Editor can be created. They cannot be moved, copied, cut or deleted. Improved/Expected Behavior: Folders can be moved, cut, copied and deleted by editors.  Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Assa Abloy Screenshot (if applicable):   Code package (if applicable):  

機能改善要求（RFE）概要： Regarding the replication process when a page is locked and a deletion process is executed ユースケース： If the deletion process is executed while the page is locked, the replication process (private) is not executed, and the page is deleted in the Author environment, while the page remains published in the Publish environment.From the user's point of view, the deletion process is considered private, so it appears as if the process has ended normally, and errors caused by locks cannot be detected.   Can you please improve the behavior so that the deletion process on Author cannot also be executed when locked? 現在／体験した動作： An event occurred in which a page was not actually private, even though we thought we had deleted the page and made it private.Upon investigation, it was determined from the log that this was due to the fact that the page was locked. 改善／期待される動作： The deletion process on Author cannot be executed while locked. 環境の詳細（AEM バージョン／サービスパック、もしあればその他の詳細

Request for Feature Enhancement (RFE) Summary: This ticket addresses issues with the AEM asset timeline and revision tracking not displaying all changes, focusing on understanding limitations and potential solutions. Use-case:   Karen Barton (AWC Librarian) reported that asset overwrites by Jeff Hess were not shown in the timeline, causing tracking frustration. Sainikhil Reddy (Bounteous Dev) explained AEM timeline shows workflow/publication events but not all low-level edits without custom versioning or audit listeners. Sarah Scalia (Bounteous) noted implementing such custom workflows in AEM as a Cloud Service is complex, estimated as a 15-point effort. The asset metadata like "Modified" and "Modified By" is visible in column and list views but not in card or insight views. Current consensus is that timeline limitations are due to AEM core behavior; custom solutions would require significant development effort. Current/Experienced Behavior: timeline does not show all l

Request for Feature Enhancement (RFE) Summary: Users should not be able to download the assets from Brand Portal, if they have reached expirationDate. Use-case: To maintain consistency and compliance. Current/Experienced Behavior: Currently its not blocked in brand portal Improved/Expected Behavior: Non admins should not be able to download assets from brand portal, if it has reached expiration date. Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Signify Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Enable Full PDF Preview in Brand Portal "Link Share" Mode Use-case: Brand and Creative teams frequently share CI guidelines and marketing documents with external agencies, vendors, and regional partners using Brand portal share link. Current/Experienced Behavior: Manually resending files or explain partial previews which in results in: * Slower collaboration and review cycles * Suboptimal brand experience for external stakeholders * Inconsistent experience between internal and external user Improved/Expected Behavior: Providing a complete in-browser preview of multi-page PDFs is critical for: * Ensuring brand consistency without needing to download files * Reducing redundant back-and-forth communication * Avoiding re-sharing or clarifying partially visible content * Maintaining a seamless, professional experience for partners Environment Details (AEM version/service pack, any other specifics if applicable): AEM Assets

It would be great to allow administrators to set specific and unique error pages when a login error happens. I have two types of users in my system. Those who authenticate with SSO and those who do not and use the mydomain.my.workfront.com/login page to log in directly and manage their password. Unfortunately, any user who errors out of SSO authentication bounces to that /login page which then causes an error loop for many users who do not realize that they can't log in through that page with their SSO credentials.It would be better if I could set a specific error page that directs them to help articles on how to resolve their SSO error and get to log in again rather than redirecting them to the /login page. But I need to keep that /login page as the error page for my users who do NOT use SSO. I need both options available because I have two separate use cases here.