Adobe Experience Manager

Request for Feature Enhancement (RFE) Summary: Allow users to add restricted characters in asset file/folder name through a console/tools menu Use-case: There has been many instances of this use-case, where customer has asked to restrict use of specific chars in the asset file/folder name. Current/Experienced Behavior: Current : There are some restricted chars which are not allowed, apart from that , if you need to add a new one, you need to overlay libs file and and your new chars to the list. Expected: A console/dialog exists in the asset section of the tools where we can add a list of chars we don't want to be included in the file/folder name.  Improved/Expected Behavior: No overlaying of OOTB code for a small change such as including a single char in the list of characters not allowed. Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name:   Screenshot (if applicable):   Cod

Request for Feature Enhancement (RFE) Summary: We would propose to have an out of the box way to always add the "?wcmmode=disabled" url slug to urls inside the author "Preview as published" environment because without it, we experience custom components breaking in the "Preview as Published". If it was always added, the author instance's "Preview as Published" could be fully navigateable for an author, which is good for demo's to stakeholders or business or testing UX flows. Use-case: An author wishes to test or demonstrate a UX flow to stakeholders on the author's "Preview as Published" to include the most recent visual changes. Current/Experienced Behavior: An author clicks a link on a "Preview as Published" page and is redirected to the correct URL, but without the "?wcmmode=disabled". The new page features components that visually break, visually misbehave or do not load content from content fragments.  Improved/Expected Behavior: An author clicks a link on a "Preview

Request for Feature Enhancement (RFE) Summary: AEM Support for HEVC / H.265 Videos Use-case: Cinematic videos from the new iphone are a new file type Current/Experienced Behavior: Video previews do not play correctly as MOV files Improved/Expected Behavior: Videos should preview as MOV files Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name:   DSW Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: We have an challenge with our implementation of Adobe Assets specifically, that when a user is in the system working in a specific folder of the DAM, and then opens an asset via the inbox, when they close the asset, they are taken back to the folder they were originally in, not to the folder of the asset they were just reviewing. Please see below for the steps to recreate, and what we would like to have happen, and why this is a pain point for my company's implementation. This system design has negatively impacted our company because users are uploading their assets with some frequency in the wrong folder, requiring our admins to help get them moved, or deleting the mis-loaded assets and helping the users re-upload the assets. Use-case: A user is working in a specific folder in the DAM, navigates to inbox to complete a review task, and is taken back to the original location when the review task is completed, not the the most recent fo

Description - There should be a way of introducing parent child relationship in AEM component dialogs (like we can in multifield). If there are two instances of one component included in another, the ansence of such a functionality leads to a lot of duplicate code.   Usecase example is for an AEM + Angular code setup. There is a requirement to add a reusable link object/resource, that can be added to many different dialogs under different resource names "primaryCTA", "secondaryCTA", "link" nodes in Banner component, for example. It is as easy as doing a  <sly data-sly-resource="${'primaryCTA' @ resourceType='my-project/components/cta-link'}" /><sly data-sly-resource="${'secondaryCTA' @ resourceType='my-project/components/cta-link'}" /> in HTL. However, we need similar solution with Angular. A dirty way of achieving this to have following in CTA dialog: <primaryCTA jcr:primaryType="nt:unstructured" sling:resourceType="granite/ui/components/coral/foundation/

Request for Feature Enhancement (RFE) Summary: Better UI experience for Settings and Rules section in the metadata schema Use-case: To be able to create metadata schemas easier and faster Current/Experienced Behavior: 1. When scrolling to the bottom of the metadata schema form (especially when it has numerous fields), the "Settings" and "Rules" section are no longer visible. 2. When selecting fields already in the metadata schema, "Build Form" option is also visible. This can lead confusion to the users as users might think that "Build Form" is a setting of the selected field.  Improved/Expected Behavior: 1. When scrolling to the bottom of the metadata schema form (especially when it has a lot of fields), the "Settings" and "Rules" sections should follow with the scrolling or "stick" to the page. The "Settings" and "Rules" sections should always be visible so that it would be easy to change the settings when selecting the fields.  2. When selecting fields already

Request for Feature Enhancement (RFE) Summary: "Build Form" should "stick" on the metadata schema editor page Use-case: To be able to create metadata schemas easier Current/Experienced Behavior: When we are creating metadata schemas that have a lot of fields, it is cumbersome to drag the field from the top of the page (since the "Build Form" scrolls with the page) and drag it again to the bottom of the page Improved/Expected Behavior: The "Build Form" should stick to the page and not scroll with the page so that it is within easy reach. The "Build Form" interface then should have a separate "scroll" from the page, to scroll through the field types. We also think it would be better to have it in the left side of the screen and collapsible so that it does not intrude as much in building the metadata schema.  Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name:   Screenshot (if applicable): &nb

Request for Feature Enhancement (RFE) Summary: Default option values when creating dropdown options in the metadata schema editor Use-case: To be able to create metadata schemas faster especially when creating dropdowns with a lot of options Current/Experienced Behavior: When creating dropdown options, we need to enter manually both "Option text" and "Option value"  Improved/Expected Behavior: When creating dropdown options, as a default for the "Option value", it should have the same value as the value inputted in "Option text"  Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Ability to copy fields in the metadata schema editor Use-case: When creating a metadata schema that involves similar fields, it will be a lot easier if there was a copy function for the fields Current/Experienced Behavior: No copy function for metadata fields. We need to define similar rule settings over and over again for several metadata fields Improved/Expected Behavior: Ability to copy fields so that rule settings, field type, and field options (if applicable) will be copied as well.  Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Ability to re-arrange options in the dropdown fields in the metadata schema editor Use-case: Easier to maintain dropdowns in metadata schemas Current/Experienced Behavior: Currently, the metadata schema editor does not allow the re-arrangement of the dropdown options. For us to change the order of the options, we need to delete and create the options again according to our preferred dropdown option arrangement. Improved/Expected Behavior: Ability to drag and drop the dropdown options according to our wanted display from first to the last dropdown option  Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: There is no exclusion or blocked keywords list that can be configured for Smart tags Use-case: Currently, there is no way to prevent Sensei from adding some keywords via smart tags. This is important since in our organization, we cannot simply tag assets with race, gender and ethnicity tags without approval or consent Current/Experienced Behavior: There's no exclusion list Improved/Expected Behavior: Have a keyword exclusion list Environment Details (AEM version/service pack, any other specifics if applicable): ACS Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Allow users the ability to remove metadata values from multiple assets when selected via multselect Use-case: We can select multiple assets today and then click Properties, to add metadata to all those assets.  DAM librarians are wanting to do the same steps, but to Remove certain pieces of metadata. For example, if we needed to remove a Tag field we originally selected on a set of assets, we’d have to access each asset, one at a time, to do that.   This is especially difficult when the selection was just user error, and now hundreds of assets must be selected, one at a time, to remove that selection. Current/Experienced Behavior: Not able to remove metadata from multiple assets at once Improved/Expected Behavior: Add the ability to remove metadata values from assets, when multiple assets are selected at once. Environment Details (AEM version/service pack, any other specifics if applicable): 6.5.9+ Customer-na

Request for Feature Enhancement (RFE) Summary: Move the manage tags button to be on the top menu bar on the More details screen, so users can quickly manage tags when viewing an asset from a workflow.  Note:  When you click on Payload from a workflow, you are landed on the More Details screen. Use-case: Move the manage tags button to be on the top menu bar on the More details screen, so users can quickly manage tags when viewing an asset from a workflow.  Note:  When you click on Payload from a workflow, you are landed on the More Details screen. Current/Experienced Behavior: No Manage Tags Option Present Improved/Expected Behavior: Add Manage Tags Option Environment Details (AEM version/service pack, any other specifics if applicable): 6.5.9+ Customer-name/Organization name: Humana Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: As a user, I’d like to see a red notification pop up that lets me know I’m missing values in the *Rights Managed Asset field so that it will display the same way as other required data fields.  Use-case: adding metadata to an asset Current/Experienced Behavior: Rights Managed Asset field and other required fields using a dropdown picker do not show up in red when asset is first opened and only displays a red outline but no triangle after an attempt is made to save the asset.  Improved/Expected Behavior: Those dropdown fields will look like free text required metadata fields and display a red outline and triangle when asset is first opened.  Environment Details (AEM version/service pack, any other specifics if applicable):   AEM as a cloud service Customer-name/Organization name: Mark Edelstein/Accenture Screenshot (if applicable): Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: An Author should be able to set some preferences in the Action bar, such as sort alphabetically, always display in column view, alwas open the references sidebar... Use-case: When an Author opens a section, AEM will load them base on creation date and in Card view. An Author can click on the action bar to sort them alphabetically or to display them in column view; or any other configuration which help the author find the necessary resources. But when an author then navigates to another section or returns later during his day, the author always has to repeat the same task of clicking sort alphabetically, display in column view... If an an author could set his preferred sort of view, then he would not have to repeat these tasks every time. Current/Experienced Behavior: Repeated manual task of setting the view configuration in the action bar Improved/Expected Behavior: A saved preference so the author does not have to repeatedly set

Request for Feature Enhancement (RFE) Summary: As an AEM user who is editing within Manage Tags, after I remove a tag and click Save, it is not straight forward to me on how to close the window. Enhancement request is to add an intuitive "Close" button vs the current "Cancel" being the only option. Use-case: As an AEM user who is editing within Manage Tags, after I remove a tag and click Save, it is not straight forward to me on how to close the window.  Current/Experienced Behavior: The current experience only includes "cancel" option in top right of UI.  Improved/Expected Behavior: Enhancement request is to add an intuitive "Close" option. Environment Details (AEM version/service pack, any other specifics if applicable): 6.5.9+ Customer-name/Organization name: Humana Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: When viewing a list of assets in Column or Card view, after I publish or update asset properties, I am brought back to the same asset in the column view where I left off; so that I don't lose my place and have to scroll to find it. Use-case:   Current/Experienced Behavior: Today, the experience is that the user is returned to the top of the list each time. Improved/Expected Behavior: When viewing a list of assets in Column or Card view, after I publish or update asset properties, I am brought back to the same asset in the column view where I left off; so that I don't lose my place and have to scroll to find it. Environment Details (AEM version/service pack, any other specifics if applicable): 6.5.9+ Customer-name/Organization name: Humana Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: AEM Assets - When using the Filter rail to search, it should only display matching assets.  Use-case: Using the Filter rail, with a Property Predicate set up, adding a keyword to that field should make it so the filter only returns assets that have that value in the configured metadata field. Current/Experienced Behavior: Search returns all assets that contain said keyword in any metadata property Improved/Expected Behavior: Search returns all assets that contain said keyword in the metadata property configured in the Property Predicate Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 Service Pack 8 Customer-name/Organization name: The Raymond Corporation Screenshot (if applicable):   Code package (if applicable): N/A Notes: This feels like a bug to me, and certainly not a "new idea", but we opened Support Ticket E-000488914 and were told to file a "fea

Request for Feature Enhancement (RFE) Summary: Generic Data Import Tool Use-case: Import data from external CMS Current/Experienced Behavior: Not Available Improved/Expected Behavior:   Environment Details (AEM version/service pack, any other specifics if applicable): AEM Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Requesting that folders be returned in search results (in addition to files)  Use-case: We often want to see inside a whole project folder, not just a file from that folder Current/Experienced Behavior: Workaround: we can access the folder from a search by removing the file name in the URL from a file that we know is inside the folder Improved/Expected Behavior: A folder is delivered in the search results Environment Details (AEM version/service pack, any other specifics if applicable): 2021.11.6019.20211109T172940Z Customer-name/Organization name: King County Screenshot (if applicable): Please see screen recording posted to Support ticket E-000521299 Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Enable the Copyright page display in AEM Assets without overriding the XMP web statement property Use-case: Right now, if we want to enable the custom coypright page to display whenever a licensed asset is going to be downloaded, the XMP web statement property is being overriden by the content path to the copyright page.  Current/Experienced Behavior: Right now, if we want to enable the custom coypright page to display whenever a licensed asset is going to be downloaded, the XMP web statement property is being overriden by the content path to the copyright page.  Improved/Expected Behavior: We don't want the web statement property to be overriden becauase we are losing important info Environment Details (AEM version/service pack, any other specifics if applicable): AEMACS Customer-name/Organization name: Accenture Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Support for NginX as a dispatcher  Use-case: Any AEM setup where a dispatcher is used. NginX outperforms Apache: NginX is faster than Apache, has a smaller codebase and can handle more request than Apache with less load on the machine. It would be beneficial for both the Adobe's server (because NginX is lighter for the machine) and the client (because NginX can handle requests faster). Current/Experienced Behavior: No NginX support Improved/Expected Behavior: NginX support Environment Details (AEM version/service pack, any other specifics if applicable): any AEM version Customer-name/Organization name: National Lottery Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: When setting an Experience Fragment in a blueprint, live copies will not automatically pick the correct corresponding language version of the Experience Fragment. This makes our author's output slower on Experience Fragments. And it increases the risk of human error/inconsistency significantly. Use-case: A multilingual setup making use of Experience Fragments. Each Experience Fragment has a Blueprint (en) and a language copy. And in Sites, a Blueprint (en) and live copies in the same languages. Current/Experienced Behavior: When an author creates or updates pages in Sites blueprint, and we synchronize those changes into the live copies, the Experience Fragments in those pages have to be adapted manually to the correct laguage. This means authors cannot manage Experience Fragments from the Blueprint in a multilingual setup. It means an Author is forced to go an manually pick the correct Experience Fragment in each language, whereas

Request for Feature Enhancement (RFE) Summary: Modify the License checker functionality for Assets since node is granite hidden folder ((granite:InternalArea)) Use-case: Checking license of an asset in the DAM Current/Experienced Behavior: can easily get to required data but can't because it is in a hidden folder Improved/Expected Behavior: change either folder permissions so it is easily accessed or move license checker functionalty to a new, accessible folder.  Environment Details (AEM version/service pack, any other specifics if applicable): AEM Assets as a cloud service Customer-name/Organization name: Mark Edelstein/Accenture Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Optimize "orderable" folders feature Use-case: User orderable folder feature for 700+ folders Current/Experienced Behavior: Right now, we are not using the "orderable" features for folders since we were told that there's going to be performance implications Improved/Expected Behavior: Be able to use the orderable features to a lot of folders in the hierarchy without any performance implications  Environment Details (AEM version/service pack, any other specifics if applicable): AEMaCS Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):