It would be great if you could change the Landing page fallback on asset expiration. A common use case would be a webinar registration page that is set to expire after the webinar has taken place and then redirect to a page that tells the person that registration is no longer possible.
Request for Feature Enhancement (RFE) Summary: Show an indicator (small lock symbol) also within the List and Column View to give and editor to see at one glance which pages are locked. Use-case: As an editor I want to see "outside" which pages are locked and from whom. E.g. when I do a publish with children this will fail if one child page is locked because version creation is not possible in that case. Current/Experienced Behavior: Only in Card View you have this small symbol which indicates that page is locked. On hover you just get the information "Locked" without the user who is locking it! Improved/Expected Behavior: In every view of the Sites console the information if a page is locked should be displayed. In addition to that the information which user locked the page should be available (on hover for Card and List and as text item in Column view. In the old Classic UI this was in - not sure why in TUI is has been removed. 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: Remove limitation how many columns can be shown in the List View. Use-case: As an editor I want to see despite the standard columns also ones showing e.g. translation status or analytics data at on glance. I want to be flexible which columns I want to see according to my field of works. Current/Experienced Behavior: Currently you can only select up to 7 columns which should be shown in the list view. But there are a lot of more columns which could display additional information. So, you can't have all information at one glance or even an additional column to be shown apart from the standard ones. Improved/Expected Behavior: Remove limitation and let user decide how many columns he wants to be displayed depending on the use case he has. We have responsive UI, this should be no problem! 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: Cloud Manager Deployment: Add emergency production deployment pipeline Use-case: LGE.com is trying to roll back the deployment after a successful production deployment. Currently, the only way to roll back is to re-deploy the code in Cloud Manager, which takes 2 to 3 hours. Given that they are supporting 24 websites (with more to come in the future), they need to reduce the build time for any rollback operations. The best way to achieve this is to enable re-deployment using an earlier stable built image. Current/Experienced Behavior: The production deployment is completed. After the deployment, the customer discovered blocker issues on one of the 24 websites. They decided to roll back the deployment. They reverted the change that caused the issue and pushed the revised changes to Cloud Manager. They restarted the Stage/Prod build, which took 2 to 3 hours. The customer is trying to minimize this 2 to 3-hour downtime as much as possible. The current production deployment pipeline is as follows: 1.Stage Deployment(77m) validation → build & unit testing(38m) → code scanning(14m) → build images(10m) → deploy to stage(15m) code scanning(14m) : code coverage(42%) 2.Stage Testing(5m) product functional testing(3m) → custom functional testing(2m) → custom ui testing → experience audit custom functional testing : Only library downloads required for testing, no actual testing 3.Production Deployment schedule production deployment → deploy to production Improved/Expected Behavior: The basic idea is an expedited deployment pipeline is a staged deployment after production deployment. Deployment using the emergency production deployment pipeline begins. first task : Production Deployment Only build (Excluding unit tests)→ build images → deploy to production second task : Stage Sync deploy to stage Since testing and code verification pipelines exist in QA or DEV pipelines and are verified by our deployment team, we believe that this task is unnecessary in production pipelines. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud (2024.4.16145.20240430T082417Z) Customer-name/Organization name: LG Electronics, Global HQ Korea 24 subsidiaries (UK,DE,PE,TR,JP,FR,SG,CO,SA,SA_EN,CA_FR,CA_EN,KZ,ID,IT,CL,TH,PT,IN,HK,HK_EN,BR ,MX ,PA) Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Sort the list of groups in the User Profile alphabetically. Use-case: As an administrator I want efficiently check to which groups a specific user is assigned to. Current/Experienced Behavior: After opening the user profile and selecting the tab "Groups", the list below the headline "Groups that this user is a member of" is not sorted, it just displays the group names randomly. You need to scroll through all the list to check if a certain group is in. Improved/Expected Behavior: The list below the headline "Groups that this user is a member of" should be ordered alphabetically to easily get an overview! 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: When using the new AEM view, the default columns that are available to users in the Configurable Columns settings should be customizable in two ways:1. Admins should be able to add/remove metadata fields (especially custom metadata fields) to the overall list available to users.2. Users should be able to select attributes relevant to their workflow experience and save the configuration. Note: Users being able to save/load multiple configurations for different workflows would be nice. Use-case: Current fields offered in Configurable Columns are limited and not applicable to many of our users. The ability for admins to offer custom metadata in these columns would eliminate bad habits by decreasing the need for users to include these values in asset file names in order to see them easily. Current/Experienced Behavior: Current metadata available to view in Configurable Columns is locked to 9 default values. Improved/Expected Behavior: Improved/Expected Behavior: Desired metadata available to view in Configurable Columns should be configurable by system admins for users to choose from. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: Tighe McGillivray/Walmart Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Pickers must remember their last location and start from there Use-case: Our editors create pages on specific topics and upload assets related to that topic. They very often upload the assets into the same folder to have everything in one place. Then they start to build a page and add the assets to the page. Current/Experienced Behavior: For the first image asset: 1. Drags in Image Component 2. Opens asset picker 3. Navigates all the way to the sub-sub-sub-sub folder 4. Selects asset 5. Confirm 6. Confirm For the second image asset: 1. Drags in Image Component 2. Opens asset picker 3. Navigates all the way to the sub-sub-sub-sub folder 4. Selects asset 5. Confirm 6. Confirm ... repeat for each asset Improved/Expected Behavior: For the first image asset: 1. Drags in Image Component 2. Opens asset picker 3. Navigates all the way to the sub-sub-sub-sub folder 4. Selects asset 5. Confirm 6. Confirm For the second image asset: 1. Drags in Image Component 2. Opens asset picker 4. Selects asset 5. Confirm 6. Confirm ... repeat for each asset So, pickers should remember their last location and start from there, at least for the current session. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: VERLAG DES ÖGB GMBH Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Introduce a tile where editors can go to see their 15 recently edited pages, assets, experience fragments -etc. incl. links to them and their parent folders. Use-case: Our editors have a newsroom culture. They must quickly put content out there. They can get interrupted to do another task and continue later. Current/Experienced Behavior: Currently, they just have the option to open all pages, assets -etc. one by one using the various locations in AEM and continue work then. Improved/Expected Behavior: In future they could just go to the Recently Used and re-open all their work from within one single place. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: VERLAG DES ÖGB GMBH Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Need access to old Blue environment after Blue/Green switch Use-case: To evaluate roll-back decision based on the issues found after Blue/Green switch we need to be able to verify issue is introduced due to the change, or existing issue. Current/Experienced Behavior: Currently, old Blue environment is only accessible by Adobe, and not integrated with the rest of the systems. Improved/Expected Behavior: Instead of putting the old Blue environment away, place them into the Green Load-Balancer, so that Green URL can be used after the switch. Environment Details (AEM version/service pack, any other specifics if applicable): Cloud Manager for AMS deployment Customer-name/Organization name: Go Endo Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Add Save as Version to Page Information menu Use-case: Many of our users miss a saving button. We don't promote that. Their need is to: Create page Modify it to their liking Save the page once they reached a "milestone" Colleagues then publish the "milestone" version or use it for approval The main editor continues working on the page Currently, the main editor must leave the page editor, go the Content Tree and create a version from there. They wish to create a version from within the page editor. Current/Experienced Behavior: The menu is not existant yet. Currently: User must close the page editor User goes to location of page User selects page User switches to the Timeline sidebar User clicks the three dots at the bottom (see screenshot) User clicks Save as Version User fills in Label User fills in Comment User clicks Create System saves Version Improved/Expected Behavior: User clicks Page Information menu (see screenshot) User clicks Save as Version User fills in Label User fills in Comment User clicks Create System saves Version Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: VERLAG DES ÖGB GMBH Screenshot (if applicable): see attachments Code package (if applicable): Somewhat related: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/enable-page-versioning-on-save/m-p/420886
Request for Feature Enhancement (RFE) Summary: Add a column with path (/content/...) to the search result list in Sites Console. Use-case: As an editor I want to search for pages which contain a special keyword in the name and/or title. In the Sites console I use the search functionality and enter my keyword to find those pages. Current/Experienced Behavior: The search result contain name and title of the pages (and also other information) but the important information where the pages are located is NOT visible - there is no column or information which is displayed via mouse over. So, I need to open each search result to get to know about location - this is not efficient! Improved/Expected Behavior: Have a column with a path available so that editor sees at on glance the location information Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: Carl Zeiss AG Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: When text is highlighted (or selected) in the Author view of the content. fragment editor, it would be ideal to see the same highlighted info in Source view. Use-case: 1. In the content fragment editor Author view, select or highlight a link or sentence.2. Go to Source view; the same piece of information should also be highlighted or selected. Current/Experienced Behavior: Text selected in Author view is not selected in Source view Improved/Expected Behavior: Text selected in Author view is also selected in Source view and vice versa Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.19.0 Customer-name/Organization name: Verizon Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Customer when using Adobe Managed Services, the AMS team used a distribution list that client managed (they could add and remove users) internally. Then, that list appeared on the notifications so they knew who received the notices. Unfortunately, for AEMaaCS, they can only see their individual names, so it's not very reassuring. Hence, customer would like to have a similar option as in AMS for AEMaaCS. Use-case: Handle, managing with more control proactive / incident notifications. Current/Experienced Behavior: When receiving incident/proactive notifications in AEMaaCS, customer can only see their individual names in the recipient list, not all. Improved/Expected Behavior: Include a distribution list that client manages (add and remove users) internally. Then, show the list on the notifications so they know who received the notices. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: Nordstrom Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Customer would like to have available logs related to Proactive/Incident notifications in their end for troubleshooting Use-case: In case a notification presents irregularities, customer would like to have logs available for knowing what's happening in the backend and proceed with trouble. Current/Experienced Behavior: No logs available for customer. Improved/Expected Behavior: Getting access for notification logs and get details about who received, managed, included in proactive / incident notifications. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: Nordstrom Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: The Add Content menu is not available in Manage Publishing of XF (Experience Fragment).I want to use the Add Content menu. Use-case: We can launch multiple publishing workflows at once for pages (sites),but this is not possible with Manage Publishing of XF (Experience Fragment). I want to use the Add Content menu for XF (Experience Fragment) as well as for pages (sites). Background There are many cases where XF (Experience Fragment) is launched in a publishing workflow at once, and the current function does not allow efficient work. Current/Experienced Behavior: The Add Content menu is not available in Manage Publishing of XF (Experience Fragment). Improved/Expected Behavior: We want to use the Add Content menu for XF (Experience Fragment) as well as for pages (sites). Environment Details (AEM version/service pack, any other specifics if applicable): AEM Release 2024.4.16145.20240430T082417Z Customer-name/Organization name: Panasonic Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Update Timewarp functionality to work with nested launches and with launches utilizing experience fragments. Use-case: Successfully utilize Timewarp functionality within all AEM launches, to avoid capturing manual screenshots of all scheduled updates to have on record. This will allow us to compare our home page to older versions of itself in order to compare metrics, trends, and any other data needed to help us improve our business. Current/Experienced Behavior: Timewarp does not work as desired for Nested Launches or when experience fragments are used. The experience fragment is not loading when the page is viewed in Timewrap or the Version UI for Preview or Compare versions. The experience fragment does load appropriately if it was part of the initial template. Our process for home page launches today involves creating nested launches off each Sunday's home page. The breaking the inheritance on components that will change for the next launch. Then we reauthor those components changing and set up for a future launch date. Improved/Expected Behavior: When utilizing timewarp we expect to be able to review previous version of any page regardless of how it was launched or what components were used on the page. Environment Details (AEM version/service pack, any other specifics if applicable): Production Customer-name/Organization name: DSG (DICKS Sporting Goods) Screenshot (if applicable): Code package (if applicable):
I think it would be extremely helpful, if you could enhance the "New Person" activity with all field values the person came into Marketo with. This is a little scarce:You can do it with form submissions or with merges, why not at lead creation?
Description -Why is this feature important to you - When we create a dynamic report using segment filter, it always pull in zero visits dimensions which is confusing the audience.How would you like the feature to work - Bounce Rate should exclude zero visitsCurrent Behaviour - Bounce Rate include zero visits
We utilize Marketo forms to gather opt-ins for a major newsletter. During an accessibility review, it was highlighted that these forms are not designed with accessibility in mind. While clients can make the necessary adjustments, it requires considerable effort. We believe this enhancement should be implemented by Marketo, rather than placing the burden on clients.
Description - Add Conditional Formatting for My Task Widget so that late tasks can appear as in the color red.Why is this feature important to you - This is crucial for my end-users as they have strict deadlines to adhere too. My worry is they will miss tasks do to not having the late description How would you like the feature to work - In referencing the legecy homescreen, the idea would be similar. Late tasks are colored in red,Current Behaviour - Currently does not exist.
Description - Option to make the Description in the Overview section of the project details a rich content editorWhy is this feature important to you - Our team uses the Description in the overview section of each project. To make it even more beneficial to them, it would be nice to be able to use this like the Text with Formatting field in Custom Forms. How would you like the feature to work - To give project owners the option to use it as a rich content editor.Current Behaviour - Doesn't allow users to put bullet points and format the Description of the project.
Description - In the past, as an admin we could use a "login as" to authenticate to an account and use that to establish a fusion connection. With the new Unified Experience this no longer works. We need a way to establish this connection, whether it is through setting up an OAUTH2 Application in Workfront and using that in Fusion or other way. Why is this feature important to you -Tying fusion to a live user is risky since a user may be deactivated. It also provides a poor user experience when the updates say Josephine Admin did this, rather than "Workfront Automation" did this.How would you like the feature to work - Current Behaviour - Broken. Can no longer set up a Fusion Connection to a service account.
For reporting based on template used, we would like to be able to change the template that was initially attached to a project. For example, if project A initially used template B we want it to be allowed to attach template A and remove template B from it entirely.
Description - Today the Segmentation view has a table view of all segments created. The Name column is so small in widths that you cannot read most of the segment names and there is no way to change the column size. The only way to make the column size bigger is to hide other columns with the "Customize table" function. However, the system doesnt save your settings and you have to hide them every single time again. Why is this feature important to you - This feature allows you to work with the segmentation list much more efficient. Currently when you have anything above 20 segments it is nearly impossible to efficiantly work with the list because there no folder functionality to group your segments and you can also not read the full segment names in the table view. Allowing for custom column widths will provide highe improvements in UX. How would you like the feature to work - Allow drag-and-drop column resizing and have any hidden columns remain hidden upon page refresh. Current Behaviour - This functionality does not exist today.
Description - Schema less event data collectionWhy is this feature important to you - Using a schema less approach to data collection will allow event data collection without having to defined all of the event attributes for an event.How would you like the feature to work - Ability to defined a schema as event based data collection with an identitfer(namespace(s), _id, and timestamp. The metadata of the event(s) does not need to be defined upon the schema.Current Behaviour - When defining event based data collection within the XDM experience class we need to define all of the attributes which are expected to be collected by a producer.
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.
