Adobe Experience Manager

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

Request for Feature Enhancement (RFE) Summary: ▽ Product-side collection response (request)Add _previewUrl to AEM CF, especially the site content Reference, and implement a specification that returns it depending on the settings. Use-case:   Current/Experienced Behavior: ▽ BackgroundIn normal page rendering, AEM constructs a URL for the set path, including resource mapping and domain settings, and returns it to the front end.These are the same for CF graphQL, and you can get information resolved from the path.Example) Set the site path in CF → CF graphQL returns the full URL of author and publish in a specific json format ▽ ChallengesThe particular json above is called Reference, but there is no previewURL present inside the Reference for the path to the site content_authorUrl: Exists_publishUrl : Exists_previewUrl : does not existTherefore, in order to set the preview URL, it becomes necessary to configure, manage, and implement resource mapping, domains, rules, etc. on A

Request for Feature Enhancement (RFE) Summary: When setting the page property "(Example) Redirect" for a launch page with the URL in the launch and promoting the launch, it is not reflected in the page property "Redirect" of the original source. Use-case: I want to change the redirect property for the launch page and have it reflected on the source page when promoted. Current/Experienced Behavior: In addition to redirect properties, title and description properties were also not reflected during promotion. Improved/Expected Behavior: I would also like page properties to be reflected as a parameter when promoted. Environment Details (AEM version/service pack, any other specifics if applicable): 2023.10.13804.20231005T183332Z Customer-name/Organization name: Panasonic　（IBM　Digital　Service） Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Mindmap view for a CF hierarchy Use-case: The Mindmap view for a hierarchy of CF. It will make it easy to browse and Edit the CF down the hierarchy. Current/Experienced Behavior: Authors need to manually browse to the CF. And if the CF is linked to futher CF, it becomes more difficult to browse and reach. Improved/Expected Behavior: Authors would easily be able to reach and edit a linked CF. Environment Details (AEM version/service pack, any other specifics if applicable): Authors would easily be able to reach and edit a linked CF. Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Currently when you use Manage Publication functionality to publish/unpublish pages, the timeline does NOT provide information about the target so that you can not see to which target it was published/unpublished. And instead of "Page published" entry like in AEM 6.5.16 on Prem only workflow steps are visible which is confusing. Use-case: Timeline should give the possibility the see what happened to page and it is important to know which target was published. If you have pages which are frequently published a clear overview is needed of editors. Current/Experienced Behavior: Missing information about publishing target. Listing of workflow steps for publication which are confusing. Improved/Expected Behavior: Provide proper information about the target to which the page has been published to. Use clear entries for publication like "Page published to Publish" or "Page published to Preview" instead of listing connected workflow steps

Request for Feature Enhancement (RFE) Summary: Open "Reveal in Sites" and "Reveal in Assets" links in the new browser tab automatically Use-case: AEM author users needs to open several Page's or Asset's language copies at the same time, so that they can compare the content on different locales. Current/Experienced Behavior: "Reveal in Sites" link is not opened in the new browser Tab even automatically. "Reveal in Sites" link is not opened in the new browser Tab even if I press "cntrl" key on the keyboard. Improved/Expected Behavior: "Reveal in Sites" link is always opened in the new browser Tab even (without pressing "cntrl" key on the keyboard). Environment Details (AEM version/service pack, any other specifics if applicable): Tested on the clean AEM 6.5.19 (without our application) Oracle JDK 11.0.20 Customer-name/Organization name: Veeam Software Screenshot (if applicable): Click on the Page or Asset Go to the "References", then "Language copies" Select a langua

Request for Feature Enhancement (RFE) Summary: Enhancement request to add 2 uicontrol elements when a menuscascase is inserted, instead of one. Use-case: Insert menucascade then insert another uicontrol to achive the end goal. Current/Experienced Behavior: When a menucascade is inserted, a single uicontrol is added. Improved/Expected Behavior: When a manucascade is inserted, 2 uicontrols are added. At the preview output, a caret is placed between the two uicontrols. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.18SP, AEM Guides 4.3 Customer-name/Organization name: Olu Oladipo / Verizon Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: AEMAACS Enhancement Request to automate reports sending to other AEM Users Use-case: In other Adobe Products (ACS,etc.) there is the ability to send reports to other users with a login. Would like this automated functionality in AEMAACS. When you  Current/Experienced Behavior: Under Tools -> Assets -> Reports -> Create -> Upload (Report of uploaded assets) Unable to automate report to send to other AEM users. I realize this is currently not a feature that I would like included a future feature request. Improved/Expected Behavior: automate reports sending Environment Details (AEM version/service pack, any other specifics if applicable): AEMAACS Customer-name/Organization name: Epsilon Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: From Guides, add an option to open dita topics and maps in Source view. Use-case: Navigate to a dita topic or map in Guides; click Options; select 'Edit Source' or 'Check out in Source'. Current/Experienced Behavior: Dita topics and maps are opened in Author view. Improved/Expected Behavior: Provide an option to open dita topics and maps in Source view. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.18,  AEM Guides 4.3 Customer-name/Organization name: Olu Oladipo / Verizon Screenshot (if applicable):   Code package (if applicable):