Adobe Experience Manager

Request for Feature Enhancement (RFE) Summary:     Be able to bulk edit smart cropping of images Current/Experienced Behavior: Users need to select each image one by one and then enter the smart crop editor to adjust. Doing this for 100 images one after the other is time-consuming.  Improved/Expected Behavior: User selects 50 assets in bulk --> Smart crop --> Adjust the smart cropping on all assets --> Save All Environment Details (AEM version/service pack, any other specifics if applicable): AEM Assets Cloud service (latest version) Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Case Insensitive Asset Upload in AEM Use-case: Currently, if we upload assets - abc.pdf and ABC.PDF - They are treated as different assets in AEM (Your local machine's storage parses it in case insensitive manner)The JCR stores the nodes abc.pdf and ABC.PDF as 2 distinct nodes. Most storage systems even in different OS (Mac | Windows) store files by default in case insensitive manner. Current/Experienced Behavior: The assets are treated as different due to their case difference. Improved/Expected Behavior: The assets should be treated as similar and versioning popup should be displayed. Environment Details (AEM version/service pack, any other specifics if applicable): 2023.11.14227.20231108T162349Z Customer-name/Organization name: TA Digital Screenshot (if applicable): N.A Code package (if applicable): N.A  

Request for Feature Enhancement (RFE) Summary :Currently, Card view in AEM Assets is staggered. Metadata displayed on the card as well as the asset's format can push assets below it down, and the rows are not even. The staggered view is hard on the eyes, when trying to pick the right asset. When we scroll down to view more images, the pages redraws and assets keep moving around. This has been very frustrating to our users and this is the most common enhancement request from our users. Our request is to make the Card view grid-like, where all rectangles in a row are aligned. Use-case:Search results and browsing assetsCurrent/Experienced Behavior:Currently, Card view in AEM Assets is staggered.Improved/Expected Behavior:Card view is grid-like, where all rectangles in a row are aligned.Environment Details (AEM version/service pack, any other specifics if applicable):AEM Assets 6.5.6Customer-name/Organization name:Wakefern Food CorpScreenshot (if applicable):..........................

Request for Feature Enhancement (RFE) Summary: For investigations within repository browser it would be nice if you could select property values with your mouse in order to copy it to clipboard and use it further. Use-case: If I lock for a page and want to check which cq:template is assigned, I would like to copy the value of cq:template property and past this path into oath browser of the Repository Browser in order to check this node. Example attached. Current/Experienced Behavior: No marking and therefore copying of the values possible. Improved/Expected Behavior: Have standard behavior available to simply mark text with your mouse and copy it. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS: Repository Browser Customer-name/Organization name: Carl Zeiss AG Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Improve the visibility logic of Manage Publication button Use-case: For a node, make the button of Manage Publication visible when the conditions are meeting crx:replicate + workflow users. Current/Experienced Behavior: 1. workflow-users are seeing Manage Publication functionality even if users don't have crx:replicate privilege.2. crx:replicate privilege is making both of Quick Publish and Manage Publication visible for a node. However, Quick Publish is working well, and Manage Publication requires additional permissions from workflow-users. Adding users into workflow-users group will cause another problem where users will see Manage Publication feature for the nodes which don't have crx:replicate privilege. It doesn't make sense because the publish access from workflow-users is extended to the nodes even only having jcr:read privilege. Improved/Expected Behavior: The visibility logic of Manage Publication button should be improv

Demande de résumé des améliorations des fonctionnalités (RFE) : Display metadata specific of 3D assets Cas d’utilisation : as we have for all images or videos we need also to know what is the identity of our 3D assets, and it will be easier to select the good asset between different "resolution" of assets Comportement actuel/expérimenté : no info today just preview Comportement amélioré/attendu : Display metadata specific of 3D assets (GLB, GLTF, FBX, 3DMAX, USDZ) : size, vertex number, number of textures, cherry on the cake : resolution of texture, to display for in the properties of the assets Informations sur l’environnement (version d’AEM / service pack, et autres informations spécifiques si applicables) : AEMaaCS Nom du client/de l’organisation : LOUIS VUITTON / Nathalie RIASSE Copie d’écran (si applicable) :   Package de code (si applicable) :  

Request for Feature Enhancement (RFE) Summary: AEM Instance link should be provided in the access email Use-case: - A big team of authors when enabled with AEM access are expected to have all the information of AEM instances in the welcome email.  Current/Experienced Behavior: - When you provide AEM access to a user from admin console, user gets a welcome email. The link in the welcome email usually redirects user to https://experience.adobe.com/ instead of specific AEM instance to which the access is given.- Because of this user has to navigate to https://experience.adobe.com/  and have to find the link to the specific AEM to which he/she was given access to Improved/Expected Behavior: - When you provide AEM access to a user from admin console, user gets a welcome email. The link in the welcome email should redirect user to the AEM (https://author-pXXXX-eXXXX.adobeaemcloud.com/) instead of https://experience.adobe.com/ Environment Details (AEM

Request for Feature Enhancement (RFE) Summary: Changed Page Order - Fix Publishing Process Use-case: The main navigation of your website is build by the order of the first level pages. Now, you want to change the order. To achieve that you change the order of the item in the Sites Console and publish the reordered item. Let's take the WKND example. Here the initial main navigation is: MAGAZINE | ADVENTURES | FAQs | ABOUT US. Now, we want to have ABOUT US entry at very first item, so we move position of the corresponding about-us document before magazine document and publish the about-us document.Pls see screenshots. Current/Experienced Behavior: The changed order is not present on the publisher, instead you still get the old order in the main navigation.To get this working you need to publish whole website content which is basically not possible in daily work as you have always some prepared pages (status = modified) which should not go online yet and of course you don't want

Request for Feature Enhancement (RFE) Summary: Currently adidas is using user synch tool to synch the users from adidas Azure to Adobe Admin console. We are not able to synch the users with GUEST type (different domains) and forcing use to create adidas external accounts for 1000+ users. Enable the feature to support the synch from Azure to Admin console with EMAIL attribute for GUEST users.  Use-case: Azure to admin console synchronization for GUEST Type Users Current/Experienced Behavior: Its only possible to synch the users and groups from Azure to Admin Console for the fixed domains. Improved/Expected Behavior: It should be possible to synch the users from Azure to Admin console for guest accounts whose domains are dynamic (personal accounts and agenciens) and should be created as Federated type on admin console. Environment Details (AEM version/service pack, any other specifics if applicable): Admin Console Customer-name/Organization name: adidas Screenshot (if

Request for Feature Enhancement (RFE) Summary: When we are inside Assets, on click of AEM Home button on top navigation should redirect to AEM Home Screen or Start screen. Use-case: We have multiple assets to upload first and then need to go to Sites to author those assets on individual components/pages. When we click on AEM home button on top navigation, it should redirect to AEM Home/Start screen. Current/Experienced Behavior: Currently, when we are inside Assets and if we click on AEM home button on top navigation, then it's redirecting/landing on Assets home screen only. Improved/Expected Behavior: Expected behavior should be, if we are inside Assets doing assets operation and if we click on AEM home button on top navigation, It should redirect to AEM home/start screen. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service - 2023.10 Customer-name/Organization name: Malabar Group Screenshot (if applicable): Code p

Demande de résumé des améliorations des fonctionnalités (RFE) : No blocking replication even if we have one contribution issue Cas d’utilisation : multiple times we were facing incident with blocked replication queue due to a contribution issue, it has not to arrive for a contribution issue ! Comportement actuel/expérimenté : replication blocked for a single asset wrongly contributed Comportement amélioré/attendu : not block replication even if one asset is wrongly contributed, we can ignore it, and warn admin team that we have an issue on this one...and let replication continue for all the other data Informations sur l’environnement (version d’AEM / service pack, et autres informations spécifiques si applicables) : AEM Assets as Cloud Service Nom du client/de l’organisation : Louis Vuitton, Nathalie Riasse Copie d’écran (si applicable) :   Package de code (si applicable) :  

Request for Feature Enhancement (RFE) Summary: This request is for AEM Forms specifically Correspondence Management. In Correspondence Management and Interactive Communication you can create conditions which can be used to select the right paragraph for the letter.   The current condition editor for correspondence and the condition editor for interactive communications are working fine for EASY conditions with just a small number of rules. When defining complex rules, the editor is quite hard to use. It would be very helpful to see the underlying condition in a code style view AND to allow the user to edit in this view (e.g. to build conditions with similar parts with copy and paste and just change some elements in the code editor) ->Demand: Ability to display and edit rules and conditions in a code-style view No JavaScript editor for condition code. You need to drag and drop fields. todo: Build a letter in Interactive communication Use-case: Better Condition Management

Request for Feature Enhancement (RFE) Summary: This request is for AEM Forms specifically Correspondence Management. In Correspondence Management and Interactive Communication you can use various assets such as fragments and so on. Current asset management allows moving assets from one place to another. Each movement takes about 30 seconds to resolve dependencies and move one asset. It is not possible to move multiple assets at the same time. With this restriction, it is impossible to restructure large asset directories with thousands of assets –time consumption is tremendously high. => Demand: Ability to move multiple assets (of the same type) at once by selecting multiple assets and either directly move or queue for moving Use-case: Moving assets Current/Experienced Behavior: Currently you can only move one asset at a time Improved/Expected Behavior: Move more than one asset at a time Environment Details (AEM version/service pack, any other specifics if applicable): A

Request for Feature Enhancement (RFE) Summary: This request is for AEM Forms specifically Correspondence Management. In Correspondence Management and Interactive Communication you can export letters. When a user is exporting assets/letters into a CMP file, he normally selects one letter to be packaged. Clicking on "Resolve" shows all related assets to be exported, always together with the data dictionary, even if not updated. In a staged environment, the data dictionary in the lowest environment always contains details which must not be promoted directly. A template author would then like to exclude the unchanged data dictionary from the CMP so as not to promote unwanted development artifacts. The "resolved" asset list just displays the assets but without any option for the user to define which assets have to be included or excluded. This makes a granular export impossible as the user always gets everything. The user cannot export a letter alone on its own.   =>Demand: Abil

Request for Feature Enhancement (RFE) Summary: When adding a new component to a page, post translation, it is displayed by default in all the locales. We would like an option to choose the locales in which the component is displayed. Use-case: We have a Gartner Reviews component which has content only in couple of languages. We cannot translate this content as it's pulled via API from Gartner website and also it has to be displayed verbatim since it is customer review.  Current/Experienced Behavior: If we add it to the English language page, it'll be display in English language across the site. We cannot translate it, nor can we hide it in certain locales. Improved/Expected Behavior: I would like an option to hide / not display the component in certain locales i.e. I should be able to choose the locales in which the component will be displayed post translation. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.18.0 (Managed Servi

Request for Feature Enhancement (RFE) Summary: Concurrent usage of the Data Dictionary is impossible because the users are not informed when someone else is working on a specific Data Dictionary.Ideally, it should say, "Hey, you can only view it because John Doe is working on it". Use-case: Editing of the Data Dictionary for Forms and Letters (Correspondence Management / Interactive communication Current/Experienced Behavior: Every user can edit the Data Dictionary; the last edit prevails Improved/Expected Behavior: Once a user edits the Data Dictionary, the Data Dictionary is locked until the editing user has saved the changes.  Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.18.0 Customer-name/Organization name: Deutsche Bank Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: A service user / technical account should be able to be created for Cloudmanager GIT (eg. Oauth/certificate-based-login, through AdobeIO / Adobe Developer Console) to avoid using regular users with password (difficult with FederatedID) for operations on Cloudmanager GIT. Use-case: when using cloudmanager, one needs to constantly sync the 3rd party git to Cloudmanger. To do this in an automated fashion, a service user / technical account is required. The current approach is a workaround in creating a regular user with password in Adobe Admin Console, but this is insufficient and error-prone (at last once a year). Current/Experienced Behavior: No real technical account to access and use Cloudmanager-GIT in a automate fashion can be creaeted. Improved/Expected Behavior: A technical account should be able to be created  (eg. though Adobe-Developer-Console / AdobeIO, maybe in the Cloudmager API)  which uses certific

Request for Feature Enhancement (RFE) Summary: When using a path browser and searching (ie in the thumbnail of the page) for a particular image, the results appear to only be based on the name. Search results from the assets search (when placing an asset in a page) or in the global search are different (as they appear to search the metadata as well). Use-case: Have the same search results when doing a search using the path browser component as in other search location (assets search and global search) Current/Experienced Behavior: On a base install of 6.5 with SP18: If you search for "biking" on http://localhost:<port>/mnt/overlay/wcm/core/content/sites/properties.html?item=/content/we-retail/us/en/experience/arctic-surfing-in-lofoten in the "Thumbnail" tab > Select image > then do a search for "biking", you get 3 results (with one being the "mountain-biking.jpg"). When you search for "biking" in the asset panel of the page (http://localhost:<port>/editor.html/

Request for Feature Enhancement (RFE) Summary: Setting to not allow a specific role to change Project Status but still own the project Use-case: We would like to force Project Managers to use a request to change the Project Status from Planning>Current and vice versa as well as the same for putting a project On Hold. Due to SAP integrations, we cannot use the Status: Planning Pending that is native to the project as it disrupts the flow of project costs and other valuable data going to/from SAP.  Current/Experienced Behavior: PM can change the Project Status Improved/Expected Behavior: The PM could no longer change the Project Status, but would rather use a Request workflow for approvals and subsequent changes to project status by the Project Sponsor.  Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: NTT America Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Branding capability within the Adobe MFA app Use-case: Adding brand attributes like brand logo, some help links specific to the brand/client into the Adobe MFA App which make more relevant to the clients who are the first time transitioning to MFA from other MFA apps like Duo or Authenticators  Current/Experienced Behavior: Use the Adobe MFA access app with no configurations specific to branding. Improved/Expected Behavior: Adding the brand details like brand logo and help text/link makes it to more client relevant. 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: Deleting a Page : Need an option to update Link references of the deleted page Use-case:  Content author Deleting a page. Current/Experienced Behavior: When content author deletes a page from AEM then the deleted page link references don't get removed in the Site core and There is no option to redirect the references to a new page or completely delete the references(hyperlinks). Improved/Expected Behavior:  When we try to delete a page then it gives us the three options ·         link to another item (if the page being deleted has been                     hyperlinked somewhere then it will redirect the deleting                page URL to new location before deleting) ·         To remove the references if the page is hyperlinked         

Request for Feature Enhancement (RFE) Summary: Apply Metadata Profile properties to assets when they are moved into a folder, that is associated with that property.  Use-cases: 1. User uploads an asset to a folder "upload" for pre-screening. From here, the assets are moved to their final destination to complete the meta data. 2. User accidentally uploads asset to the wrong folder and successively corrects by moving into the proper folder.  Current/Experienced Behavior: Currently, metadata Profiles are applied only when assets are uploaded to a folder. They are not applied, when an already uploaded asset is moved from another folder into the marked folder.   Improved/Expected Behavior: Issue: The above is somewhat unintuitive: User apply metadata profiles to ensure, that all assets in that folder have the same set of defaults. There is no reason not to apply the profile on move. I.e. we end up with a mix of assets in a folder. Some assets have the pr

Demande de résumé des améliorations des fonctionnalités (RFE) : Be able to reach Inbox in one click or one shortcut Cas d’utilisation : Inbox used when workflow takes time Comportement actuel/expérimenté : Today inbox is bellow notification, it's not easy way to reach it Comportement amélioré/attendu : gain of time to access to this inbox Informations sur l’environnement (version d’AEM / service pack, et autres informations spécifiques si applicables) : AEM CLOUD Nom du client/de l’organisation : RIASSE NATHALIE / LOUIS VUITTON Copie d’écran (si applicable) :   Package de code (si applicable) :  

Demande de résumé des améliorations des fonctionnalités (RFE) : Be able to multiselect inbox message to clean them Cas d’utilisation : to have notification of inbox not always +100 Comportement actuel/expérimenté : select one by one to suppress Comportement amélioré/attendu : select all or multiselect to suppress Informations sur l’environnement (version d’AEM / service pack, et autres informations spécifiques si applicables) : AEM CLOUD Nom du client/de l’organisation : RIASSE NATHALIE / LOUIS VUITTON Copie d’écran (si applicable) :   Package de code (si applicable) :  

Demande de résumé des améliorations des fonctionnalités (RFE) : We have developped on UI specific buttons and columns, to switch new UI, we need these customised buttons & columns Cas d’utilisation : benefit new UI Comportement actuel/expérimenté : custom buttons & columns Comportement amélioré/attendu : new UI of AEM support customised button and columns Informations sur l’environnement (version d’AEM / service pack, et autres informations spécifiques si applicables) : AEM CLOUD Nom du client/de l’organisation : RIASSE NATHALIE / LOUIS VUITTON Copie d’écran (si applicable) :   Package de code (si applicable) :