Build better products with our product team
test idea final description
test idea creation description
test idea description
test aep event description
idea
I want to test ideas visibility in export
test test
When working with offers we cant filter the offers on the "created by" filter. It is not an option in the filtering menu and its not an option in the canvas/offers list. You can get the data to show in the offers list, but you cant click on that column to filter/sort on that data, like you can with "last modified" and "modified by". For our users it could be hard to find the offers you have created when we have over 40 creators of offers in our platform. Therefor there is a need and wish for a better filtering and listing of offers based on "created by" data.
In our daily work we are facing a challenge when it comes to maintaince of email templates build from fragments. We are using different pre-defined templates that is built from fragments. And the fragments again contains just dummy images and lorum ipsum texts. The users changes the content in the fragments when they create there Journeys with there emails. The issue we are facing is when a content designer wants to change the template that is in use in an running Journey – there will be a problem. The content designer could have ordered a total new template, with a new look that he wants to use (a new framwork) or simply just want to change to another existing template (could be seasonal variations in the design). When you use the “change design” feature in the email, and changes to another template – you use all your created content in that email you are changing design too. It should have been possible to keep your content when you change the underlaying template.Maybe it could be solved buy having a export content feature, that takes all HTML code from the “Drag and Drop” container, and make this possible to import into the new template you have selected. The code is there, it is just to move it into the new selected template -and store it. That could have been an option when changing the design – move the content true or false, when you make your change.With an option like that it would be much easier to play around with templates and make changes seamless without any boundaries or risking loosing your created content by mistake.
Create the ability to assign a default view on a portfolio and program level. We extensively use custom form data. Projects in different portfolios and programs will often have specific custom forms tailored to that project type. It would be very useful not to have to change views when navigating through different portfolios.
Request for Feature Enhancement (RFE) Summary: Ability to search for images in the “Pick Image” window on the image component As of now, when an author tries to select an image using the “browse for image” option in components or page properties, they need to drill through the entire AEM directory and hunt for the image they want with truncated file names and tiny thumbnails. Could we have the ability to search for an image using file names or descriptions? Use-case: Image Search in “Pick Image” Dialog Currently, when authors select an image in AEM through the “Browse for Image” option (in components or page properties), they must manually navigate through the entire directory structure. This process is inefficient and error-prone, especially when dealing with large repositories, truncated file names, or small thumbnail previews. By adding a search capability within the “Pick Image” dialog, authors could quickly locate assets by file name, description, or metadata. This enhancement would significantly improve the authoring experience by: Reducing the time spent searching for specific images Streamlining content creation and updates Minimizing manual navigation errors Increasing overall productivity for large-scale content teams Current/Experienced Behavior: When we select/pick an image into the image component, we have to select the aem directory and hunt for the image we want Improved/Expected Behavior: Could we have the ability to search for an image using file names or descriptions and then select the one we want Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 Customer-name/Organization name: OneTrust Screenshot (if applicable): Code package (if applicable):
There is no easy way to know if someone has deleted a scenario and who deleted the scenario ...or a way to restore it back. There is also no easy way to run a report or even copy/paste the scenario names into a spreadsheet to try and compare against. This is an urgent need, because someone could really mess things up the way the product works currently.
Request for Feature Enhancement (RFE) Summary: Today if we select multiple pages in sites and then click edit, only one page will open in a new tab for authors to edit the page. We wanted the behaviour where, if an author selects multiple pages and click edit, all of them should open up in new tabs. Use-case: ease of authoring Current/Experienced Behavior: Today if we select multiple pages in sites and then click edit, only one page will open in a new tab for authors to edit the page. Improved/Expected Behavior: it should open multiple aem pages in multiple browser tabs Environment Details (AEM version/service pack, any other specifics if applicable): 6.5 SP 20 Customer-name/Organization name: Dyson Screenshot (if applicable): Code package (if applicable):
We are facing a editorial challenge when users are creating emails in the email designer. This is regarding the use of email fragments. We have created many different fragments as design elements/modules, and in all of this fragments we are using variables to control how the fragment should look like. F ex we use variables to choose between pre defines background colors, we use variables to set the alignment of the content (can vary from mobile to desktop), we have different styling of CTAs etc. Today this settings needs to be done before the fragment is broken, and the content can be edited. The challenge is after the fragment is broken we cant change the variable settings from the interface.But there is a work around, and this is not user friendly. From the code editor we can access the fragment code, and by finding the right place in the code we can manually change the chosen value of the variable. And this is reflected in the template when we save the change.It would be very helpful if it would be able to change the variable values after the fragments is broken. We see that this can manually be done since the values is already present in the code, we just need the interface to do it -and not manually from the code editor.
DescriptionDynamic text visualization would allow the inclusion of dynamic fields (dimensions, metrics, segments, or date ranges) directly within text elements. This enables text to automatically update based on the context of the analysis, making dashboards and reports more interactive and informative. Why is this feature important to youProvides greater flexibility in storytelling with data.Reduces manual effort of updating static text when filters or date ranges change.Enhances clarity by showing contextual information.Improves user experience by making text responsive to analysis changes. How would you like the feature to workText visualization should support placeholders that can be linked to dimensions, metrics, or filters.When a user changes a filter (e.g., date range), the metrics displayed should automatically refresh to reflect the new values.Ideally, users can select fields from a menu or insert them via a formula-like syntax.Example: {{ date.range }} there were {{ orders.sum }} {{ orders.dimension }} from {{ country }} -> this would result into: Last week there were 567 orders from USA. Current BehaviourText elements are static and do not adapt to changes in filters, segments, or date ranges.Users must manually edit text to reflect updated analysis context.This limits the ability to create dynamic, self-explanatory dashboards.
Request for Feature Enhancement (RFE) Summary: Ability to delete workflow packages before maintenance task configuration is requested Use-case: A large number of unnecessary workflow packages used before setting maintenance tasks remain in the PROD environment, and some functions are unavailable due to timeouts. In addition, there is a significant impact on the performance of Timeline display.Specifically,・In order to display Timeline, the retention period of workflow archives must be set to one day.・Due to timeouts, the launch function cannot be used effectively, putting a heavy burden on authoring operations and scheduling. Current/Experienced Behavior: How to delete past workflow packages is not disclosed. In addition, there is no official tool or knowledge. Improved/Expected Behavior: Provide tools or publish knowledge to remove remaining workflow packages that cannot currently be removed Environment Details (AEM version/service pack, any other specifics if applicable): AEM aa CS Customer-name/Organization name: Panasonic (Org Name: panasonicglobal) Screenshot (if applicable): - Code package (if applicable): -
Request for Feature Enhancement (RFE) Summary: Remove Content Fragment jcr:title from being included for translation by default when using option "Enable Model Fields for Translation" Use-case: For translation rules for CF I don't want to maintain rules in the translation_rules.xml file, instead I want to give just the creator of the CF Model the chance to define which fields should considered for translation by setting the field "translatable". With current situation creator of CF Model does in fact have NO full control as jcr:title is always translated (creating costs for translation that I do not want to pay. Hence feature is useless as I need to maintain my translation rules manually. Current/Experienced Behavior: Even if I use the option "Enable Content Model Fields for Translation" to use the Translatable field of the Content Fragment Model in order to control which fields should be translated, the jcr:title of the CF is in by default. I can not exclude it and therefore is creates unnecessary costs. This makes no sense, as on the one hand you handover the control for translatable fields on creator of the Content Fragment Model, on the other hand you define the jcr:title to be translated by default with no option to control. See: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/sites/administering/reusing-content/translation/rules# Improved/Expected Behavior: Remove CF jcr:title from being translated by default and give creator of CF Models FULL control over fields to be translated. Actually it makes no sense to translate the jcr:title of a CF as it makes more sense to keep this in one language (English) for common readability in AEM UI. Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Carl Zeiss AG Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Use-case: Summary:Walmart data custodians continue to expand our metadata usage within AEM Assets, and it is necessary to reflect those metadata fields in custom search forms. Currently, adding new metadata fields to the custom search interface requires code-level updates, as we are using the Group Predicate option to consolidate search facets into a dropdown. This slows down iteration and limits the ability of administrators to maintain and evolve search functionality in step with schema updates. Current/Experienced Behavior: The Group Predicate (dam/gui/coral/components/admin/customsearch/searchpredicates/grouppredicate)—which is essential for logically grouping and structuring search filters—is not available through the AEM interface for manual configuration. While this predicate can be added through code, it cannot be added or preserved directly through the UI, leading to our business admins not being able to directly change the search form. Improved/Expected Behavior: Requested Enhancement:1. Make the Group Predicate Available in the AEM UI Users can add filters within group predicates Administrators can specify the title of the group predicate in the UI. The search form editor interface allows admins to specify whether the group predicate is initially open or closed for users. Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Walmart US Marketing Screenshot (if applicable): Code package (if applicable):
We shouldn't have to have our browser's zoom set to 100% in order for WF to display reports/lists properly without auto scrolling upward on its own.We didn't used to have to do this, but about a week ago something changed.I've already worked with support who said something changed and now it has to be at 100% zoom or when you scroll down to the bottom of a report, it automatically and on its own starts scrolling upward making it difficult to review the data.
Description - Calculate work effort based on planned hours on task instead of workday.Why is this feature important to you - It's a more realistic situation to calculate work effort based on the planned hours of the task rather than the workday. How would you like the feature to work -We would like our users to be able to change the work effort on their task based on the original planned hours of the task, not the workday. Current Behaviour - Work effort is calculated using 8hr workday.
Description -I would like to more easily keep track on day-to-day changes in number of qualified profiles for batch audiences. Why is this feature important to you -AJO end users often change audience criteria and want to follow-up on the effect of that change when it comes to difference in audience size. How would you like the feature to work -I would like the audience properties to show number of qualified profiles from both the most recent batch update as well as the previous one. Current Behaviour -Currently AJO end users have to keep documentation somewhere else than AJO to keep track on the difference in audience size after a change in the audience criteria.
Description:Having he ability to remove/delete/replace custom dimensions from those 10 in the system tab.
Description -Whenever an offer with status "Approved" has passed its offer end date, the offer is no longer available to customers but it still keeps the status "Approved". This can cause confusing for the AJO user since it's not clear whether the offer is available to customers or not. Why is this feature important to you -We mainly use offers as a way to communicate with our customers and we find it confusing and prone to mistakes when at first glance seeing an offer with status "Approved" but then also have to check the offer end date. We would also like to filter on "Approved" offers where the end date is passed or not. How would you like the feature to work -We would like to have a new offer status introduced called "Finished". The criteria for this status would be that any "Approved" offer that has passed its offer end date will change status to "Finished".
When you work in the Journey builder creating a new Journey, or want to do changes in an older one, the change you find necessary to do often is actually in an Audience used in the Journey. In other cases you need to check an Audience you have used. Today you need to go out of the Journey builder and find the wanted Audience in the Audience overview. In the Journey builder interface where you select Audiences to use, it would have been nice it you actually could go directly to the Audience and open it from this page/view. It is a little misleading that you have a edit button there, but the only ting that happens is that you open a popup with the total number of Audiences you can select from. You dont find the one that is selected directly and you cant open it to edit on it. That would be a way more helpful feature - open and edit the already selected Audience, directly from the Journey builder interface.
We have experienced that expressions with audience names in the expression is not updating if the audience is changing name. This causes the expression to fail. since the audience "is no longer there". This causes problems for the users of the platform and the customers receiving communication. In bigger organizations like ours there are many different teams working in AJO at the same time, also in different countries. If there is an audience library to be used of many users, as part of staying under the audience threshold limitation, many user can use the same audience for different kind of activities. Both as inclusions, as well as exclusions in the organizations activities. And many will therefor also have the same audiences used in expressions. We see that this now causes big and surveil danger in using expressions in AJO Journeys. An audience name can easy be changed, planned or by mistake. And the consequences can be big when expressions then stop to work as planned, only because of a name change. The changer of the name might not even be ware of all the Journeys where this audience name is been used. Backtracking this can be a though and hard job, finding all the logical breaks that now has has come. We suggest that there is "another" connector in the expression builder that uses the ID for the audience rather than the name. Relaying on a name is not a good idea in general. You can showing the name in the creator, but in the back is should really be an ID that is used, something stable and reliable that doesn't change regardless of name and content of the audience. This discovered weakness can cause surveil damage to our customers, without anyone knowing.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
