Adobe Experience Manager

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):