Adobe Experience Manager

Request for Feature Enhancement (RFE) Summary: Enable Preview for referenced content in AEM as Cloud Service Use-case: Currently, Preview service is limited in the sense that referenced content associated with the page does not automatically get pushed to Preview and there is no option to Push to Preview for Assets, Tags, etc. Current/Experienced Behavior: Currently, Preview service is limited in the sense that referenced content associated with the page does not automatically get pushed to Preview and author has to use Add content option to include Referenced assets, tags, etc. The only option to do this in Bulk is to use a Workflow but that does not allow author to selectively distribute content. Improved/Expected Behavior: Page and all referenced content associated with the page should automatically get pushed to Preview or at least author should get an option to select the references and decide whether to push those. Environment Details (AEM version/service pack, an

Request for Feature Enhancement (RFE) Summary: Please enhance the information which is displayed if you hover on the publish date with exact time of publishing Use-case: As editor I maintain a lot of pages per day. And, I also publish them. The UI provides me just the date of publication, even on hover it shows me not the time when publication took place - it just provides the weekday which is pretty useless at all. For investigation reason it is a lot of effort to mark the page and check timeline in left rail to get the information about the publishing time. Current/Experienced Behavior: Currently if you hover on the publish date just the weekday is displayed in addition to date. Improved/Expected Behavior: On hover the exact time should be displayed as well like it was the case in Classic UI. This should be an easy task! Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Carl Zeiss AG Screenshot (i

Request for Feature Enhancement (RFE) Summary: Enhance External Link Checker page Use-case: As en editor I want know about broken external on my website which I'm responsible for and want to fix the links efficiently. Current/Experienced Behavior: Under /etc/linkchecker.html you get a list which but you can not export it to a csv. Imaging you have a lot of editors working on AEM instance each responsible for different subtrees reflecting different business groups. Now it is hard to figure out the error for specific paths in order to fix this. It is even harder if error occurs not just on a single page but in blueprint page and the connected livecopy pages (imagine 20 livecopies) - here the column get's flooded (just very long comma separated list) and hard to retrieve the information out of that.   Link to documentation: https://experienceleague.adobe.com/docs/experience-manager-65/content/sites/administering/operations/external-link-checker.html?lang=en#external-link-ch

Request for Feature Enhancement (RFE) Summary: Our system has some DAM folders with more than 1000 PDFs in a single folder.  We are encountering an index error when using the default Assets interface. Use-case: This should occur in an AEM system with no custom code, provided that some DAM folders have huge numbers of assets in them. The user opens Assets and traverses the system using various views. Some folders may fail to open in certain views. Current/Experienced Behavior: This appears in the log: *WARN* [10.240.32.86 [1693910873433] GET /mnt/overlay/granite/ui/content/tree.0.html/content/dam/document-library/corporate-pensions HTTP/1.1] org.apache.jackrabbit.oak.plugins.index.Cursors$TraversingCursor Traversed 1000 nodes with filter Filter(query=select [jcr:path], [jcr:score], * from [nt:base] as a where ischildnode(a, '/content/dam/document-library/corporate-pensions') order by [jcr:created] desc /* xpath: /jcr:root/content/dam/document-library/corporate-pensions/*

s Request for Feature Enhancement (RFE) Summary:  in pipeline process choices, enhance a choice to Stop/Terminate after stage installation the pipeline beside current choices of "Ask every timeFail ImmediatelyContinue Immediately" Use-case:   Current/Experienced Behavior: only these three options of Ask every timeFail ImmediatelyContinue Immediately Improved/Expected Behavior: add option of Stop/Terminate after stage installation  Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Pipelines | Cloud Manager (adobe.com) Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: I would like you to modify it so that hyphens are not automatically converted to underscores. Use-case: When creating a folder in XF, I entered a hyphen in the title (required) and saved it, but the name (optional) was automatically converted to an underscore. Current/Experienced Behavior: When creating XF settings, hyphens entered in the title are automatically converted to underscores. Improved/Expected Behavior: When creating XF settings, Hyphens entered in the title are not automatically converted to underscores. Environment Details (AEM version/service pack, any other specifics if applicable): 2024/3/8version Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Users should be able to preview ZIP files Use-case: As a DAM user I should be able to preview the contents of the ZIP files before unzipping them to save DAM storage space. Current/Experienced Behavior: With the new released feature, we can unzip the contents of the ZIP file. Improved/Expected Behavior: Being able to preview the content of the ZIP before unzipping Environment Details (AEM version/service pack, any other specifics if applicable): AEM as Cloud Service Customer-name/Organization name: Philip Morris International Management SA Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Make button order in Author UI consistent Use-case: Our users want to work quickly in AEM. However, the inconsistent button order of the menu bar slows them down. We got a number of complaints by our authors regarding the Author instance UI: Authors are irritated by the changing order of buttons throughout the DAM and Sites. Current/Experienced Behavior: Each content type (image, video, pdf, webpage, CF) changes the order to some degree. Our authors understand that different asset types may have different options, but the position of the buttons changes too much for them. Improved/Expected Behavior: Our users work mostly with Sites and expect the DAM button to be at the same location, which is hardly the case. See screenshots. We would move the options that are available to all types in front and the specific ones at the end. That should ease their situation. Either this comes by default, or our admins can configure the ord

Request for Feature Enhancement (RFE) Summary: Duplicate Image component IDs decrease accessibility score Use-case: Our accessibility tool detected a WCAG AA violation, when the same image is used multiple times on the same page. When the same image is used multiple times on the same page, both instances share the same ID. That should not be like that according to WCAG and W3C. HTML IDs must be unique. There is also a support ticket for that: E-001038208. Our developers recommend this being fixed on a platform level not in custom code to ensure WCAG and W3C compliance for all customers. Current/Experienced Behavior: When the same image is used multiple times on the same page (e.g. hero image is used also in content), both instances share the same ID. Improved/Expected Behavior: All instances of the same image have different IDs by combining the already existing image ID plus the JCR path to make it truly unique. Environment Details (AEM version/service pack, any other

Request for Feature Enhancement (RFE) Summary: Tools to validate regex and glob against rules defined for Dispatcher. Use-case: Validating dispatcher globs and patterns can be time-consuming. It would be great, if there was a tool to verify the regex/globs quickly like Glob Tool.  Current/Experienced Behavior: We need to deploy and validate Improved/Expected Behavior: Would be able to quickly verify without deployments Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS and AMS Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Use full screen height for displaying member list in group dialog. Use-case: As admin I need to check who is member of a group but although my view port is high enough the list is not displayed completely and AEM forcing me to scroll. Area should use full height of screen. Tools > Security > Groups > select one group and open properties > switch to tab 'Members' Current/Experienced Behavior: Area for member list has fixed height although you have view port available, see screenshot. Improved/Expected Behavior:   Environment Details (AEM version/service pack, any other specifics if applicable): 2023.11.14227.20231108T162349Z Customer-name/Organization name: Carl Zeiss AG Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Add 3rd invalidation processing mode in AEM dispatcher based not on paths but tags. Use-case: Currently dispatcher supports either statfile level based or ttl based page invalidation. Those two approaches can't be reliably combined (with dispatcher 4.3.5) and are too inflexible for big multinational websites. AKAMAI has concept of tag based invalidation where each page supplies list of tags when it's cached and those tags can be used during invalidation. Current/Experienced Behavior: stat file or TTL based page invalidation Improved/Expected Behavior: 3rd mode where a list of tags (arbitrary ascii strings) is supplied from publisher with a cacheable page in a custom header. The tags are stored and indexed along with cached resources (e.g. in a page.html.tags file) in the dispatcher cache. Then when some resource is invalidated an osgi service installed on publisher is invoked by flush agent to supply a tag value. That tag value i

Request for Feature Enhancement (RFE) Summary: Currently, to edit a user permission we do the following steps -  1. Navigate to User Management Console (/security/users.html) 2. Select a particular user and then select properties 3. On the new page, navigate to the Groups tab and edit the groups. (/libs/granite/security/content/v2/usereditor.html/home/users/..)   Doing this for multiple users takes time as one has to repeat the 3 steps again and again. If we have a custom console which allows user to search by email and quickly display the page in Step 3's Groups Tab it would speed up the multiple users assignment to groups. Use-case: A custom "Users" console which allows quick assignment of groups without following the above 3 steps. Current/Experienced Behavior: Currently, the user has to follow the above 3 steps. Improved/Expected Behavior: Removing Step 2 and allowing user to grab view of current groups along with addition of new groups in Step 1 itself will be

Request for Feature Enhancement (RFE) Summary: Displaying Permissions flowing from Groups to a User in AEM for view only purpose. Use-case: Currently, the permissions console in AEM is streamlined into Users, Groups and View All. This allows to search for Users and Groups and then see the permissions.The permissions are seen distinctly for users and groups. But often a user is associated with multiple groups and thus has overlapping set of permissions. To see this currently, we have to see the groups user is tagged to and then explore each group permissions individually.If we could have a section within permissions window which allows us to see different permissions received from the groups it would help see the overall access control better. Current/Experienced Behavior: AEM Product Admin has to see permissions for individual and groups separately. Improved/Expected Behavior: A user console where permissions assigned to user and permissions flowing from groups to user are vis

Request for Feature Enhancement (RFE) Summary: Moving an asset to a folder where an asset with the same name already exists creates a duplicate asset without asking if duplicate assets are wanted.  It should not be assumed that users want duplicate assets in a folder.  The system should prompt the user to make the same selections upon a move that it does upon an upload.  The options are:  "NAME CONFLICT  An asset named ex.1234567.pdf already exists in this location.  Click Create Version to create the version of the asset or Replace to replace the asset or Keep Both to keep both assets." Use-case: The use case is duplication of unwanted assets and asset governance. Current/Experienced Behavior: Moving an asset to a folder where an asset with the same name already exists creates a duplicate asset without asking if duplicate assets are wanted Improved/Expected Behavior: The system should prompt the user to make the same selections upon a move that it d

Request for Feature Enhancement (RFE) Summary: A tool that will show all the asset statuses under a particular path. The status will contain some important information like (Reference count, Publish status, Created By, and so on) Use-case: At the time of authoring, the Authors uploaded a lot of DAM assets and referenced them on the AEM page. But sometimes many assets are unused or some pages are deleted after a certain time. But by this time assets are not deleted since this is a time-consuming task. Authors cannot see all the unused assets at a time and are not able to delete them so easily. Current/Experienced Behavior: There is no UI for to see all the Asset statuses under a certain path and bulk delete from that UI. Improved/Expected Behavior: A tool under the asset tool section will help Authors to make clean DAM easily. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5, AEMaaCS Customer-name/Organization name: Brain Station

Request for Feature Enhancement (RFE) Summary: Possibility to configure per DAM folder/location which user groups are allowed to upload which asset types Use-case: Restrict authors from uploading unwanted asset types in unwated locations, while keeping super users (or e.g. admins) the full/unrestricted access.  Current/Experienced Behavior: Possibility to limit allowed asset types globally for all users Improved/Expected Behavior: Possibility to confiure the allowed asset types per DAM folder for specific user groups Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: Hitachi Energy

Request for Feature Enhancement (RFE) Summary: AEM users should be able to filter licensed assets from Adobe stock, given that these assets are not saved in AEM Use-case: AEM users should be able to filter licensed assets from Adobe stock, given that these assets are not saved in AEM Current/Experienced Behavior: AEM user can save assets from Adobe stock to AEM asset, then user can search licensed assets from already saved Adobe stock assets in AEM. User can't filter only licensed assets from Adobe stock search in AEM when Adobe stock assets are not saved in AEM. Assets need to be saved in AEM to do the same. If we connect AEM with Adobe stock and there are many licensed assets in Adobe stock, there is no way to filter all licensed assets from Adobe stock search. Improved/Expected Behavior: AEM user can filter licensed assets from Adobe stock in AEM and save them in AEM Environment Details (AEM version/service pack, any other specifics if applicable): NA Customer-name/Or

Request for Feature Enhancement (RFE) Summary: The ability to sort the destination folders alphabetically when moving assets Use-case: We currently have hundreds of client folders in our AEM, being able to sort the list of available folders when moving assets would save us a lot of time. Current/Experienced Behavior: Currently, there is no way to sort the list of folders in the Select Destination step when moving assets. It requires our team to scroll through our entire list of client folders when needing to move assets. The folders also do not populate automatically by alpha Improved/Expected Behavior: We would love to be able to sort the available folders by alphabet at the select destination step to eliminate the need to scroll through a list that seems to be haphazardly sorted. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a cloud service, AEM Assets Customer-name/Organization name: Corinne Preston / Stream Companies Screen

Request for Feature Enhancement (RFE) Summary:  Capability to search for domains in the Domain Settings Page of the Cloud Manager for AEM as a Cloud Service. Use-case: As an administrator, I need to search for a specific domain configured via the Cloud Manager Domain Settings in AEM as a Cloud Service. I am managing hundreds of domains that span across multiple pages, and currently, there is no efficient way to locate a specific domain quickly. Path: <Program> > Program Overview > Domain Settings Current/Experienced Behavior:  There is no search functionality available to rapidly locate a specific domain. Improved/Expected Behavior: Search functionality available to rapidly locate a specific domain. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Cloud Manager Customer-name/Organization name: Boston Scientific Corporation Screenshot (if applicable):   Code package (if applicable):  

#chatgpt3 #adobeexperiencemanager #chatbot #aichatbots   Video Demo : https://drive.google.com/file/d/1bvuI03FlXSXdUY1gncI3u1uFZR22_Uz_/view?usp=sharing   As ChatGPT continues to be a buzz word around the internet, an idea intrigued me in how ChatGPT's potential can be leveraged in Adobe Experience Manager Sites.   ChatGPT can be integrated into AEM in several ways to enhance the user experience and improve the performance in below areas like 1. Content personalization 2. Image and video optimization 3. Insights and analytics 4. AI Chatbots   The integration of ChatGPT with Adobe Experience Manager as a Chatbot for websites offers a new level of customer service and engagement. With ChatGPT's cutting-edge natural language processing capabilities, users can receive quick and accurate responses to their inquiries through an intuitive chat interface.   This integration enables businesses to provide a personalized and interactive experience for their customers

Request for Feature Enhancement (RFE) Summary: DataDog integration for report monitoring tools. Use-case: Most organizations now are using DataDog for monitoring systems.  Current/Experienced Behavior: Currently, AEM can only be integrated with Splunk.  Improved/Expected Behavior: Able to comply with different company standards especially for organizations that are using DataDog and not Splunk Environment Details (AEM version/service pack, any other specifics if applicable): AEMaCS Customer-name/Organization name: Proquire Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: GraphQL API to get References to a Content Fragment/Asset Use-case: In a headless approach utilizing GraphQL with content fragments, we aim to clear the cache on a third-party app whenever content is manually updated on AEM or via packages. Additionally, we seek to reset the cache for other content that references the updated content fragment or asset. Current/Experienced Behavior: We are unable to find the content referencing the updated CF/asset via GraphQL queries. Improved/Expected Behavior: Should be able to find the content referencing the updated CF/asset via GraphQL queries. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Enable Component level inheritance status OOTB without the need to overlay  Use-case: As a content author, MSM roll-outs is a key content authoring activity. When a content author performs a roll-out of the content from the language master to the related livecopies, there is a provision to see the page level inheritance status in the rolloutdialog.html. But this page doesn't provide any information about the component level inheritance status of all the components inside the live-copy page. At times, this creates a lot of confusion where a content author is trying to roll-out a page to live copy but some components are not getting updated due to the fact that component inheritance is broken on the live-copy page. if there are too many components on the page, then it becomes very tedious process for the content author to check each and  every component for its inheritance status. Currently, this can be solved by overlaying t

Request for Feature Enhancement (RFE) Summary: AEM Assets supports   browsing through folders and form-based searching for tags Other DAM systems offer a third alternative:  tag-based browsing In these systems the tag hierarchy would be rendered as if it was a folder and users can naturally browse through the folders. Whenever you'd "browse" to the next tag, the UI would display the assets tagged with these current tag.    Yes - in principle AEM supports that case already: You can  a) Open the filter b) Click on a tag filter c) Browse to the tag you want to search for d) Select that tag e) Submit the search form.   "Real" tag based browsing is a one-step interaction, only. You would "open" a tag from the "hierarchy" side rail - and AEM would implicitly display all assets with that tag. Imagine it as implicit search-as-you browse: product (select * where tag ~ /product/*) - food (select * where tag ~ /product/food/*) - regional (select * where t