Adobe Experience Manager

Request for Feature Enhancement (RFE) Summary: Add 3D asset viewer to the Brand Portal, similar to the one in AEM Assets Use-case: People who view, download and share assets should be able to make use of the 3D viewer functionality on 3D assets. Similar to the functionality that is available in AEM Assets. Current/Experienced Behavior: The 3D asset is not recognized as a 3D asset and cannot be viewed Improved/Expected Behavior: The 3D asset will be recognized as a 3D asset 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: Our authors are facing a problem with Asset authoring in AEM Page. Use-case: When Authors are trying to add a featured image (in page properties of a page), they just get a pathPicker where they have to manually browse through the asset hierarchy & select the image. Current/Experienced Behavior: Pathpicker doesn't provide ability to search for the asset before picking it as featured image. This is difficult for authors to navigate through multiple folders & select the image Improved/Expected Behavior: There should be an option to search for asset in this page properties screen while authoring any asset. Or if the siderail is enabled (which already has assets listed there) in this page properties screen that should help. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service Customer-name/Organization name: Cognizant Screenshot (if applicable):   Code package

Request for Feature Enhancement (RFE) Summary: CSV Import Tool which perfom Publish, unpublish, delete, Move actions on given paths in csv  Use-case: Generally in any project we have multiple nodes [Pages, Assets, Renditions...] that need to be Publish/Unpublish/Delete, and example n number of nodes are not in use and cause huge impact on environment performance and we need to unpublish those and then delete it, it could be n number of assets, pages [which used for testing or duplicates etc]. and let say the number could be in 1000+. so in that case we have to write groovy script, servlet, scheduler or worflow etc, to read the path of nodes from particular CSV and do operation like publish, unpublish, and delete using replicator API or in anyway. and writing this code need lot of optimization based on environment behaviour [e.g : making it sync or async]. Instead of this approach if we could have a generic solution where the product have a CSV importer tool which will read th

Request for Feature Enhancement (RFE) Summary: Create a Latam community Use-case:   Current/Experienced Behavior:  Find AEM certified in Latam  Improved/Expected Behavior: Create community to find consultors or Developers / TA to contract. 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: Content Fragment creation wizard to have option to allow only few models and not all. Use-case: When author tries to create a new CF, he/she should be able to control the models that should be populated on creation wizard. Current/Experienced Behavior: Currently, when creating a CF, we see a huge list of CF models available, which is cumbersome for author to scroll through all of them. Currently, there is option to search using browser or add customizations using additional clientlibs but would be better experience if taken care in product functionality. Improved/Expected Behavior: Pagination or Tagging or OOTB Search or having allowed models can help. Environment Details (AEM version/service pack, any other specifics if applicable): All AEM versions supporting CFs Customer-name/Organization name: Adobe Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: It would be excellent if multiple pages under one path could be selected and moved together. Currently only one page can be selected and moved at a time. It seems like the interface and behind-the-scenes processing is already capable of most of the heavy lifting, as a page with hundreds of children can be moved; just not multiple individual pages. Use-case: This feature would be a huge time-saver in situations like: breaking a section of a site into multiple sections closing down a section of a site and redistributing the child pages among a few remaining sections breaking a small news or event hierarchy into a more robust by-year or by-month structure (e.g. sorting 100 articles into 2020, 2021, 2022 folders) moving lots of pages into a folder (e.g. move 100 pages under a new "archived" page) Current/Experienced Behavior: When selecting one page, a "Move" button appears in the toolbar. When selecting more than one, "Move" disapp

Request for Feature Enhancement (RFE) Summary: The OOTB rollout functionality does not provide any notification or messaging on failed or skipped item, all of them will say successful even though some were not processed. As a result, technical person need to triage the rollout line by line to identify the issue and error in order to fix. Use-case:   Current/Experienced Behavior: The rollout functionality shows all items were process, even though some items were failed or skipped. Improved/Expected Behavior: Proper messaging to notify content author which item has failed/skipped roll out and the reasoning. Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Hi, Something that has been confusing our users is a message they receive when downloading assets in bulk. When they hit "Download," they see a green message that says, "Your download is generating, and will appear in your inbox when ready." Our users see the word "inbox" and think, "this is going into my Outlook or email inbox." So they sit and wait around for an email that never comes. Little do they know, until they ask me, that the "inbox" is different. Totally confusing. Anyone else also find this confusing? Thanks!  

Request for Feature Enhancement (RFE) Summary: Improve the UI of user group management in Touch UI Use-case: Authors managing user permissions Current/Experienced Behavior: Current UI can be confusing and hard to read Improved/Expected Behavior: New UI is simplified and made less confusing Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 SP 13 Customer-name/Organization name: Qantas   In 6.5 the group management UI can be very confusing compared to 6.3. The UI by default shows all group memberships, including those inherited by other groups. This can be surprising compared to 6.3 which only shows explicit memberships and it makes it a lot less clear what groups the user belongs to. Additionally, the only visual distinction between assigned and inherited group memberships is that the remove button is greyed out on the latter, which is visually very difficult to tell apart and is a bad indicator of which one is which.  

Request for Feature Enhancement (RFE) Summary: Related Case #E-000797571 Use-case: We noticed recently the new warning message added to AEM bulk edit scenario, where user attempt to “Select all” and edit these sub-pages in separate tabs. The warning message says that “Bulk action not supported, The selected action Edit(e) will only have effect X selected items currently loaded…”. As we understand, the justification for that warning message is to let user know that not all sub pages might have been lazy-loaded, and that’s fine. That also explains why the massage doesn’t need to appear when pages have been selected manually. The point is that the mentioned logic might be confusing when there are only few sub-pages to be selected by “select all”. In that case lazy logic is not the case and user can be sure that “select all” picks all the sub pages we have on the screen. Please consider extending that logic, because our customers feels uncomfortable with new behavior and confusin

Request for Feature Enhancement (RFE) Summary: Ability to propagate tag updates on custom fields referencing them Use-case: We have custom fields that are referencing tags. Whenever there are updates on the tag hierarchy like updates and deletions, we would need to do a lot of page re-tagging and updating since the updates are not cascading automatically. Current/Experienced Behavior: Changes on the tag hierarchy does not automatically reflect on custom tag fields Improved/Expected Behavior: Changes on the taxonomy should automatically reflect on the pages using them Environment Details (AEM version/service pack, any other specifics if applicable): AEMaCS Customer-name/Organization name: N/A Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Reporting  Use-case: Generation of reports about pages that should include any metadata available Current/Experienced Behavior: No OTTB reporting tool is available aside from exporting via CSV through the AEM Sits UI which is done manually per node Improved/Expected Behavior: Reporting tool should have the following:- Configurable columns (any property related to a page can be selected)- Ability to export to CSV or Excel - Ability to filter which content should be included- Can save configured reports (reused)- Schedule generation/exporting of reports- Identify the destination of the reports - Must be efficient (does not harm the performance of the website) Environment Details (AEM version/service pack, any other specifics if applicable): AEMaCS Customer-name/Organization name: N/A Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Related case #E-000807920 Use-case: If you want to use Launch functionality to change a template of a page that has sub-pages are using the launch functionality, then the subpages are deleted when you have include sub-pages toggle on.   Steps to reproduce: 1. Create Launch of a page having subpages2. Select the page and leave the "Include subpages" toggle on, then Next.3. Give a launch title and select the "using a new template to replace the page" option, then Next.4. Select different template and create the Launch5. Goto corresponding launch page and "Promote Launch" and continue with promote full launch.6. It shows the page's modified whereas all the subpages are deleted.   More details can be found on the ticket #E-000807920 Current/Experienced Behavior: Sub pages are getting deleted Improved/Expected Behavior: a) don't have the switch "include subpages" in the launch dialog so that you avoid this effect. This mea

Request for Feature Enhancement (RFE) Summary: Integation of Adobe photoshop with AEM Use-case: Teams can use it to design assets and design files and also have an ability to share it with diiferent team and instances , This also helps manage business designs and revisions. to have direct connect with xd on the product to access number of assets project wise. Current/Experienced Behavior: https://www.youtube.com/watch?v=nHjRk7dw9rI Improved/Expected Behavior: To have not just assets customization, to also have page level similar xd. Environment Details (AEM version/service pack, any other specifics if applicable): NA Customer-name/Organization name: NA Screenshot (if applicable): NA Code package (if applicable): NA

Request for Feature Enhancement (RFE) Summary: Allow "READ" operations using the Adobe Experience Manager Assets HTTP API without requiring "WRITE" access Use-case: Users who are not given write access should still be able to fetch asset data using the Assets HTTP API even if they don't have WRITE access Current/Experienced Behavior: Right now, if a user only has read-only access, he or she is not able to use the read functions of the assets API Improved/Expected Behavior: Provide the flexibility to be able to use the API while only having a read access Environment Details (AEM version/service pack, any other specifics if applicable): AEMaCS Customer-name/Organization name: Prequire Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Language Navigation should match the expected language code "id_ID" for Indonesian (Bahasa). Use-case: Language Navigation displaying incorrect language code for Indonesian (Bahasa). Current/Experienced Behavior: Language code displayed is "in_ID" or "in" which does not match the expected language code "id_ID"  Improved/Expected Behavior: Language code displayed should be "id_ID" or "id" Environment Details (AEM version/service pack, any other specifics if applicable): AEM as Cloud service Customer-name/Organization name: Abbott Screenshot (if applicable): Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary:  AEM S3 connector support for SSE-C Use-case: For protection of customer data, encryption in transit and at rest is required. Some data stored in S3, requires the use of customer managed, customer provided keys. This provides an extra level of security through separation of duties, as one team/role can manage the keys, while another team/role can use the provided keys for encryption of the data.   Currently, AEM S3 connection supports only two of the valid encryption options for S3 server-side encryption. SSE-C encryption is needed to allow for that separation of duties. Current/Experienced Behavior: AEM S3 connector currently supports SSE-S3 and SSE-KMS, but not SSE-C (customer managed, customer provided keys) Improved/Expected Behavior: AEM S3 connector would support all 3 encryption options Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 SP 13+ Customer-name/Organizatio

Request for Feature Enhancement (RFE) Summary: Restrict IP access for ingress integration that use Service Credentials on AEMasCS author without putting the whole environment behind vpn Use-case: The third-party connector leverages Service Credentials to access AEM as a cloud Author. It uses POST and Sling Post requests for updates in AEM. We want to make sure that if the credentials are compromised, nobody would be able to make any updates to the production environment from IPs that are not whitelisted. While the environment should be still publicly accessible. Current/Experienced Behavior: No IP restrictions per Service Credentials/Integration Improved/Expected Behavior: It is possible to restrict the access for the integrations per IP Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service Customer-name/Organization name: Macys Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Would like to add functionality to allow the following: Add a button or option to allow the user to create a smaller collection from assets already in a collection..  Use-case: The researchers will create a collection for their clients to send for review. Upon review of the collection, the client selects which images they would like to use from that pool.   Prior to using Adobe, the researchers could then just save those final images into a new collection. In the Adobe system the researcher needs to search for the images/assets again and create a collection or go through and remove all the rejected images from the original collection.   If the researcher could just highlight and save the selected photos to a new collection it would be easier and save time.    Another scenario is that the researcher could keep larger collections of frequently used assets and then create tailored collections. Current/Experie

Request for Feature Enhancement (RFE) Summary: Make AEM + Target a truly seamless integration Use-case: Delivering Personalized Experiences as Standard Content Management Current/Experienced Behavior: User creates the default experience on an AEM page, creates XF in AEM, exports those XF in AEM, then swivels the chair over to the Target UI to create a Personalization Activity, selecting from the experiences exported from AEM to then deliver back to AEM.  This makes customers feel like Personalization is distinctly separate from Content Management, and that AEM and Target may "talk to each other" but are not truly an "integrated content marketing platform". Improved/Expected Behavior: Keep Target there behind the scenes, and even the UI for customers that don't have AEM.  But for customers that do have AEM, allow Activities to be fully created directly within AEM such that to a content author they don't even need to know that Target is a separate tool/technology.&nb

Request for Feature Enhancement (RFE) Summary: Lower the risk of having an unresponsive server by restricting the page reach for the functionality “Create launches” Use-case: A content author opens the Adobe Experience Manager (AEM) Launches interface (/libs/launches/content/launches) and clicks “Create”. The next step is to click to top-left button “+ Add Pages” to select a page or a folder. On the next screen, the content author selects “Included subpages”. The top-right button “Next” is clicked, the next screen is displayed and “Inherit source page live data” is clicked along with “with existing content”. The button “create” is clicked. Current/Experienced Behavior: The current behaviour is described above, with the mention the content author is allowed to select any page or node, even the top folder that might include a very large number of pages that will trigger AEM to create copies for all those pages. Due to the number of nodes, a site-wide transversal is triggered,

Request for Feature Enhancement (RFE) Summary: By adding Dynamic Renditions as an option for Download of Collections, would save time of scrolling and selecting all images within a collection (sometimes collections have 500+ images) Use-case: Many accounts that we provide images to all accounts have different image specs/sizes that are needed and we have created dynamic presets for these accounts. Current/Experienced Behavior: Currently we have to select all images within a collection for the dynamic rendition option to be an option for download. We also are getting an error when collections contain a 100+ images and we select dynamic renditions- so we then have to download these collections in smaller batches.  Improved/Expected Behavior: Saves time and improves efficiency and accuracy that all images have been downloaded and sized accordingly.  Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization n

  Request for Feature Enhancement (RFE) Summary: Orientation detection is not available OOTB Use-case: There is a filter to see assets based on orientation -- portrait, landscape, and square. However, this will not be useful if assets are not manually tagged with the orientation tag.  Current/Experienced Behavior: Orientation detection is not available OOTB Improved/Expected Behavior: Orientation detection is available OOTB Environment Details (AEM version/service pack, any other specifics if applicable): AEM Cloud Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: The review process makes use of the inbox. When a user has multiple items to review each individual item has to be clicked  Use-case: Use Case: As a user, I have 10 items to review. I have reviewed them and I would like to:   select all 10   press complete   select approve and leave comment   press ok Current/Experienced Behavior: Current behaviour is I need to do the above us- case 10 individual times! The number of clicks is huge. It is not a friendly process. Improved/Expected Behavior: As use-case above. 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: Add keyboard shortcuts for common builder functionality: Insert component Configure Insert image Preview Edit  etc. Use-case:   Current/Experienced Behavior:   Improved/Expected Behavior:   Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):