Product ideas | Community
Skip to main content

Filter by idea status

10000+ Ideas

Asset Selector Microfrontend MFE - Make Status field ConfigurableNew

Request for Feature Enhancement (RFE) Summary: Asset Selector Microfrontend MFE: Make Status field Configurable to display publication status Use-case: The Status indicator on the MFE seems to have been designed for an Assets-only installation, and with the new Asset view in mind, only.    On Enterprise installations, i.e. where one has an Author and a Publish system, tasks and the approval status are rarely used. Instead user would "publish" an asset, which implicitly means "approved" (otherwise why would you publish).Use Case: AEM is used to manage and host the website. Assets are delivered from Publish.,A 3rd party, external, customer-facing application uses AEM as delivery system for their assets.  The according backoffice application uses the MFE to select assets.    This application  needs to know which assets have been published. Otherwise it would store path references that have not been approved (in this case "published") and cannot be resolved on Published. Current/Experienced Behavior: The field dam:status is rendered hard-coded in the MFE.  Improved/Expected Behavior: Make the status field in the MFE configurable, so that the provider of the MFE can choose what to display here. In the described use case, show the publication status (not the approval status). Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS latest as of Nov. 2. 2025 Customer-name/Organization name: any Screenshot (if applicable):   Code package (if applicable):  

Review Process Dropdown Lacks User Search FunctionalityNew

Request for Feature Enhancement (RFE) Summary: The "Assign to" selection dropdown menu within the AEM Guides review process does not filter results when a user's name is typed into the field. This requires users to manually scroll through the entire list to find and select a name.This issue significantly hinders workflow efficiency, especially in projects with a large number of registered users, making the process time-consuming and prone to selection errors.Steps to ReproduceNavigate to the AEM Guides interface and select content for review.Initiate a review process (Menu -> "Create Review Task").Click on the "Assign to" dropdown field.Begin typing the name of a known user into the field.Feature Request:Implement a type-ahead search or filter functionality for the user selection dropdown menu to allow for quick and efficient searching. Use-case: Ease of functionality Current/Experienced Behavior: Typing into the field has no effect on the list. The full, unfiltered list of users remains visible, forcing the user to manually scroll to locate the correct person. Improved/Expected Behavior: As characters are typed into the field, the dropdown list should dynamically filter in real-time to display only the users and groups whose names match the entered text. Environment Details (AEM version/service pack, any other specifics if applicable): 6.5  Customer-name/Organization name: Red Hat Screenshot (if applicable):   Code package (if applicable):  

Update email master templates in an always on JourneyInvestigating

We have found an issue in AJO making us concerned about how to handle emails in an always on activity - when the master email template is been updated. It seems like there is now obvious way of changing and updating a template, and at the same time keep the content that is created in a template used in an running Journey. Changing the master template directly in prod, or from a upgrade package is no problem. The issue is how to keep the created and customized content used in that template you are updating. In many cases you are just updating the "framework" like header/footer or other more than less static content in a template. And in a Journey you create the relevant content for this activity using the "static" framework. But when you need to change/upgrade the framework, and change the template in use with the new and updated version, the customized content is been deleted. Is is not able to update just the template, and keep the customized content inside the template. We strongly suggest that there could be a feature making it possible to update an email "master template" that is in use, and at the same time be able to keep the customized content that has been created using this template. The template is still a template and that framework is used in several Journey's. We run into serious problems it we need to re-create all content just because the the template has an update in the static frame content. If you in the back end could split between what is template code and content code this might not be a problem. It seems like those two things is merged together and AJO cant see the difference between template code and customized content code. 

Bulk Delete Feature for Journey OverviewInvestigating

OverviewThis change request proposes adding functionality to allow users to delete multiple journeys simultaneously from the Journey overview, with built-in dependency checks to prevent deletion of journeys in active states.Current BehaviorCurrently, users can select multiple journeys in the Journey overview (indicated by a blue line showing the number of selected items), but must delete journeys individually through each journey's ellipsis menu.Proposed ChangesEnable bulk deletion of multiple selected journeys through a single actionImplement/Keep as is - dependency checks to prevent deletion of "Published" (including "In review", "Dry Run") journeys. Only delete when status is Draft, Draft (Test), Finished or similar. Add a "Delete Selected" button that appears in the blue selection bar when multiple journeys are selectedDisplay a confirmation dialog showing:Number of journeys that will be deletedNumber of journeys that cannot be deleted (with their states)Option to proceed with deleting eligible journeys onlyValidationOnly journeys in Draft, Draft (Test), Finished or similar status can be deletedIf mixed selection (some eligible, some ineligible), provide clear feedback on which can be deletedAfter deletion, the selection counter should accurately reflect remaining selected itemsError HandlingIf deletion fails for any journey, show appropriate error messageProvide detailed feedback on which journeys were successfully deleted and which weren'tBenefitsImproved user efficiency when managing multiple journeysReduced risk of accidentally deleting active journeysConsistent user experience for bulk operations

Moving landingpages between SandboxesInvestigating

Today: Landingpages are used for opt out (unsubscribe) to emails. Link to this page is placed in a email fragment in the footer of all email. A standard way of doing this. When this link to this page is created in the email designer tool, it adds a landing-page-id to the link. This in a unique ID that need to be there present for the link to work. And here comes the challenge .... If you use a Sandbox for testing, that many do. We have all our email fragments present in the test Sandbox. And it you then have created links to a landingpage for opt out, that page does not exist in the test Sandbox, or the other way around.The problem:We are running into a problem either way we look at this. If we create the link to the opt out page from the test Sandbox, this will not work when moving the fragments to a Prod Sandbox. Or if the link is created in Prod it will not work in Test. The result of not having the right landingpage present in eighter Test or Prod we are not able to send Proofs. The need:It is not a sustainable solution that we need to change the landingpage-id in this out out links to get email fragments and Proof sendings to work, when working with a test and prod environment. Especially when you easily can move fragments and templates with no problems between Sandboxes. But in most cases it is a link in a footer fragment that will not work if you aren't able to move the landingpages as well.