Build better products with our product team
Request for Feature Enhancement (RFE) Summary: Ability to re-baseline RDE environment after reset / Backfill code image from Prod to other environments Use-case: After a production release we backfill our environments. This is done by executing pipelines for the various Dev environments however this could be different to whats deployed to production depending on when the master branch was deployed.For our RDE environments however, this is manual and when we have multiple RDE's for our developers its a time consuming task to reset each environment. It would be great if we could simply select an image that has previously been deployed to an environment such as Production and be able to deploy that to any dev/rde environment without having to run a build pipeline.This would minimise effort from executing multiple pipelines and manual effort and would also minimise processing by Adobe as the image would already be built and validated. Current/Experienced Behavior: Manual for developers to deploy code after resetting it Improved/Expected Behavior: Create the ability for an environment to be backfilled based on an image that has already been deployed Eg: Production code image can be deployed to Dev & RDE Environment Details (AEM version/service pack, any other specifics if applicable): AEM cloud manager Customer-name/Organization name: Spark NZ Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Allow to search for Assets by combination of options e.g. Created by, Created Date and Modified Date Use-case: goto aem activate filter Select created date - in last 2hours (same for all options) Select modified date - in last 2 hours (same for all options) Current/Experienced Behavior: Tick box now removed from created by and added to modified by Improved/Expected Behavior: Would expect to be able to filter by all 3? Environment Details (AEM version/service pack, any other specifics if applicable): AEM Assets CS, AEM Release ID 18175 Customer-name/Organization name: Jet2 Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Dispatcher GUI Use-case: Dispatcher management Current/Experienced Behavior: Not often it is cumbersome to develop, manage and trroubleshoot Dispatcher configurations, including those specifically belonging to Apache HTTP server. Improved/Expected Behavior: - I remember that back in the days there was a pretty good UI tool for managing Apache HTTP related configurations. It was called http://www.apache-gui.com/apache-windows.html and we can refer to it and check it out to see how it works.- I would propose to have a similar tool for managing Dispatcher configurations. Everything should nicely be viewed in a visual editor. It may contain hints and preferably validators that can be used during editing. The core engine for the tool can either be developed from scratch using maybe ANTLR or it may reuse the stuff that Adobe uses internal to read, interpret and apply the Dispatcher config. - I would be more than glad to participate and contribute to development of such tool. Environment Details (AEM version/service pack, any other specifics if applicable): For both on-premise and AEMaaCS. Customer-name/Organization name: Techich.com Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Provide a means of permission and user-management for AppBuilder Applications (through Adobe IMS, AdminConsole) Use-case: When developing App Builder Apps, the question occurs how to give different users different permissions within the App (or access to the app at all).How can access to an App be granted or denied - and what about granual permissions within the app?How is permission-management / user-management within Appbuilder Apps handeled?IF we do not yet support something like that ..I think each app should have the ability for product profiles in the admin-console, which could then be customized to have as many different permission levels as required by creating additional profiles.(Naturally these should be easily available on runtime "OOTB" for developers to use. And not though something like the UMAPI - which is very cumbersome ... ) Current/Experienced Behavior: Unfortunately ORG level is the only granularity in terms of access to an app which is way too broad. Everything else currently needs to be handled within your app.IDPs like Auth0, cognito, supabase, must be integrated directly into the app (so only "non-Adobe IPDs can be used). This is not simple when you inevitably get into MFA, SSO, password rules enforcement, fraud detection, etc Improved/Expected Behavior: I'd also like to see more fine grained control built in on our side, e.g. via profiles added to an IO project, which would change the required scopes to invoke the action, so only users with that profile/group would be able to access it with their token Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Adobe & serveral customers using App Builder extensively Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Developer Console in AEMaaCS should display runtime environment variables values too - This helps to know which is the current value being picked (default or custom) Use-case: Currently the config.json displayed in the pod at cloud manager for an instance displays configuration for environment variable as is in the codebase - "configKey": "/configValue/$[env:CUSTOM_KEY;default=9876543210]/rohan", If the CUSTOM_KEY is configured in environment variable then the value that should be displayed is the actual one and not the above one. If it's not configured then the default value should be displayed to give a better idea of whether an environment value is configured for an instance or not. Current/Experienced Behavior: User has to navigate to the Environment Variable console to manually verify whether CUSTOM_KEY is configured or not. In a project with 150+ env variables this becomes an unnecessary lookup. Improved/Expected Behavior: The config should display the proper correct value. If no environment value is configured then display the default one else display the custom one. Environment Details (AEM version/service pack, any other specifics if applicable): 2024.10.18311.20241017T104455Z Customer-name/Organization name: EPAM Systems Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: The Cache metrics report generated by Adobe SME named "AEM CS BPO Tech Staff Report.pdf" monthly basis recommends improving the CDN Cache ratio but the way its generated needs to be revisited as the internal call, or URL forwarding requests, internal redirects are all being tracked differently causing the cache hit and coverage ratio scores reported low. Use-case: Ex: when the request is made for our website like fiserv.com gets (302) redirect to https://fiserv.com and to https://www.fiserv.com/ in this case considered as different requests and reports miss or pass. As this is the homepage and the number of page visits to the homepages are high the score gets impacted significantly. other examples like A) there are calls like /autodiscover.xml and other that gets originated from network or bots or health checks and not from core AEM application which also gets reported as MISS/PASS and impacts the score. B) json responses with url params cannot be cached due to impl nature and requirements but this also gets reported as MISS After detailed manual analysis and cache coverage details the Adobe SME confirms we are on excellent coverage beyond the minimum standards and no issues but as per BPO report and score from Cloud manager dashboard we are not. Hence request for revisiting of reporting to reflect actuals appropriately. Current/Experienced Behavior: The Cache score is low Improved/Expected Behavior: The Cache Ratio should reflect the relevant and appropriate scores Environment Details (AEM version/service pack, any other specifics if applicable): AEM CS Customer-name/Organization name: Fiserv Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Alias for Environment Names in Cloud Manager Use-case: We are working on AEM Cloud Service environment and due to our Business Strategy we were required to rename the cloud environments. I reached out to support to check on this topic. Unfortunately we do not have a possibility to rename or set another value to the name of the environment https://experienceleague.adobe.com/home?support-tab=my-cases&case-id=E-001417728&org-id=21EC1DCC64F9DFD10A495FAA%40AdobeOrg#support Current/Experienced Behavior: Due to this our customer is facing issue in remembering all the names which are not aligned with the business strategy Improved/Expected Behavior: Having Aliases will enable customer to have the names of the environment aligned to the business strategy Environment Details (AEM version/service pack, any other specifics if applicable): All Cloud Environments Customer-name/Organization name: PHILIP MORRIS INTERNATIONAL(PMI) Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: We propose adding accessibility testing to the AEM Cloud Service Cloud Manager pipeline, providing a baseline assurance for compliance with the European Accessibility Act (EAA) and the Web Content Accessibility Guidelines (WCAG) 2.x. By embedding accessibility checks directly into the CI/CD process, this feature would enable proactive identification and resolution of accessibility issues, fostering a more inclusive user experience and aligning with industry standards. Use-case: Compliance with Accessibility Standards (EAA, WCAG 2.x):Ensuring compliance with the European Accessibility Act (EAA) and WCAG 2.x is critical for organizations operating in Europe or serving global audiences. Automated testing within the Cloud Manager pipeline would provide a baseline for meeting these legal standards, reducing the risk of non-compliance and associated penalties. Early Detection of Accessibility Issues:By running accessibility checks at each deployment, teams can catch issues as they arise in the development lifecycle rather than after the website has gone live. This proactive approach enables timely fixes, reducing the effort and cost of retrofitting accessibility after deployment. Consistent Accessibility Checks Across Updates:Websites evolve over time with new content, features, and design updates. Automated testing ensures that accessibility remains a consistent focus, regardless of these changes. Testing at each deployment helps maintain high accessibility standards without relying solely on manual checks. Enhanced User Experience for All Audiences:Regular accessibility checks improve the overall user experience, particularly for users with disabilities. By identifying and resolving barriers to access, organizations can create a more inclusive experience that caters to all users, increasing engagement and satisfaction. Real-Time Visibility into Accessibility Status:Integrating accessibility testing into Cloud Manager provides real-time feedback for each deployment, helping teams monitor the site's accessibility status over time. This visibility allows for better tracking of improvements, trends, and issues, fostering a culture of accessibility awareness. Reduced Dependence on External Tools and Manual Processes:Teams often use separate tools or manual processes for accessibility testing, which can lead to inconsistencies and require additional setup. Having accessibility testing directly within AEM Cloud Manager centralizes this process, reducing dependency on external resources and making it easier to manage compliance in a unified way. Quick, Actionable Reporting for Developers:Axe DevTools CLI provides actionable insights into specific accessibility issues, helping developers understand and fix problems more efficiently. Integrating this into Cloud Manager would give development teams immediate feedback on violations, with clear paths to resolution, accelerating the remediation process. Simplified Audits and Documentation:Regular automated testing creates a log of accessibility compliance that can be used for audits, internal reviews, or reporting to regulatory bodies. With consistent testing and reporting, organizations can better document their commitment to accessibility and provide proof of compliance if needed. Improved Cross-Functional Collaboration:Accessibility compliance often involves collaboration across teams, including developers, designers, and content authors. With a centralized testing system in Cloud Manager, different stakeholders have easy access to results and can work together to address issues, fostering a more collaborative and inclusive approach to accessibility. Optimized Resource Allocation for Accessibility Work:Automated testing helps teams identify which pages and components are non-compliant, allowing them to allocate resources more effectively. For example, developers can prioritize fixes on the highest-traffic pages, ensuring that accessibility efforts are strategically focused on areas with the most impact. Simplified Enablement of Accessible Design Practices:Regularly surfacing accessibility issues through automated testing encourages teams to design and develop with accessibility in mind from the start. Over time, this helps build a team culture that prioritizes accessibility, reducing the frequency of issues in future releases. Risk Mitigation in High-Visibility or High-Risk Deployments:For major releases or updates to high-traffic pages, automated accessibility testing provides an extra layer of assurance that all users will have a positive experience. This is especially important for key marketing pages or campaign launches, where accessibility oversights could negatively impact a large audience. Simplified Accessibility Compliance for Multiple Geographies:Many organizations operate in multiple regions, each with different accessibility standards. Automated testing within Cloud Manager can help ensure compliance across various legal frameworks by testing for standards like WCAG 2.x, reducing the risk of non-compliance regardless of location. Current/Experienced Behavior: Adobe Experience Manager (AEM) Cloud Service currently does not include built-in accessibility testing as part of its Cloud Manager pipeline. Accessibility compliance checks are often handled through external tools or manual processes, resulting in potential inconsistencies and increased risk of non-compliance with standards like WCAG 2.x and EAA requirements. This can make it challenging to maintain consistent accessibility standards across updates. Improved/Expected Behavior: We recommend integrating automated accessibility testing within the AEM Cloud Manager pipeline. This enhancement could use a solution like Axe DevTools CLI to conduct accessibility tests on either a set of pre-configured pages or the customer’s 20 most-visited HTML pages, provided the site is not headless. This would give developers a reliable way to identify accessibility issues within the CI/CD process, ensuring regular compliance checks and addressing issues early in the development lifecycle. Key benefits would include: Consistent accessibility testing aligned with WCAG 2.x and EAA standards. Proactive issue identification within the CI/CD pipeline. Enhanced usability for all users through improved accessibility compliance. Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: e.g. VodafoneZiggo Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Add caption and copyright to Image component policy Use-case: Our clients have legal issues with artists due to copyright not being shown. Authors forget to enable the checkbox. But they never forget the caption, because it's auto-enabled by policy. Current/Experienced Behavior: Author adds image to page Author edits properties Author enables "Get copyright from DAM" Author clicks Done Improved/Expected Behavior: Author adds image to page But that is only possible of the options "Get copyright from DAM" and "Display copyright" are added to the Image component policy and we as admin can enable them as default for our clients. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS 2024.10.18311.20241017T104455Z Customer-name/Organization name: Verlag des ÖGB GmbH Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Creating customised triggers in error logs. For an instance when a trigger for Null pointer is placed in the logs file then an email alert should be triggered when Null pointer is encountered in that log file. Use-case: Monitoring the expected errors Current/Experienced Behavior: There is no notification kind of feature for error logs, download the log file and check the logs. Improved/Expected Behavior: An alert for customised errors in log file Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 onprem Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Adding rules to custom metadata fields in metadata form in Assets UI Use-case: A user wants to narrow the search for a particular asset by using fields where the parent is selected, only the remaining values of the children field are displayed to use. An example is Brand/Subbrand. There may be 20 values in the brand, but there are 5 unique subbrand values under each brand. Current/Experienced Behavior: Rules are not available in Assets UI Improved/Expected Behavior: Add rules functionality or an alternative Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: Hershey Screenshot (if applicable): Admin UI view Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Remove "Download" button for Viewer Presets Use-case: Based on the current behaviour of AEM as a cloud service, when users open the assets and select Viewers section, a download button is available so the users try to download the viewer but an error message is shown. Current/Experienced Behavior: "Download" button is available for the feature Viewer Preset but it 's not possible to download them because no content is there. Improved/Expected Behavior: "Download" button should be disabled/hidden after selecting viewer presets to avoid confusion in the users. Environment Details (AEM version/service pack, any other specifics if applicable): 2024.10.18175.20241010T124406Z-240900 Customer-name/Organization name: Jet2 Screenshot (if applicable): Code package (if applicable):
Today, when a Marketo user accesses the REST API and reads Activity ID #22 (Change Score), the primary attribute is called "Score Name". This is defined as an integer. However, the integral value does not provide a match with other calls, like checking object fields. If I look in the UI at a score activity, I can see that both a score ID attribute and score name attribute are logged: As a result, I'm guessing there's been a slight error where Score ID is being retrieved instead of Score Name. Could this please be updated so the proper, resolvable value is passed? Otherwise, this forces solution providers to write manual workarounds.
Description - It was recommended by Workfront Support to enter an idea. Currently, there is no column or filter for report entry date only last viewed date. Why is this feature important to you - It would be helpful data to have especially for Admins doing report clean-up to know when a report was entered.How would you like the feature to work - Report entry date element included in reporting for users to use as a column, filter, and groupingCurrent Behaviour - Does not exist
I'd love the ability to be able to export the dialog script into a format such as PDF or other wireframe that can be then downloaded and shared internally. This would be very helpful when proofing logic with users who do not have access to the application to review the chat details and logic.
Description - When a users share a segment with a group of users or individual, there should be an option to decide edit rights - edit copy or edit original. Why is this feature important to you - Our Analytics community is mixed with foundational to advance users and we are often sharing components based on expertise level. This feature would help us to democratize more of the IP across teams. How would you like the feature to work - The sharing prompt should work much like workspaces. Edit copy - Edit Original- Read Only. Current Behaviour - Today we can only ask the user to clone segments from the components section, if they want any specific universal segments OR work based on trust that the user wont make an update and would be careful.
Users have high-priority need to take a Request that has been converted to a Project (using a specific template) and create a second project (with a different template) out of the original Issue/Request. Users would be able to browse from Request list and see all projects created from original request.
The Report Description In the header of a report will display in one line with no line breaks regardless of whether line breaks are applied in the actual description in ‘report settings’Many of our reports use bulleted lists in the description (implemented with line breaks and dashes) so displaying in one single line in the report itself is not the best experience.Adding here as an enhancement for consideration!
Request for Feature Enhancement (RFE) Summary: Enhance the view settings for the list view so that you can select the alias (sling:alias property) next to the options which are available currently. Use-case: If you want to localize the URL's of your web pages, the way to go is to keep the name of the page in English and use the alias value for the translation. E.g. if you have a page about history, you would create a page with name history in AEM and set the alias of this page to geschichte (which is the German translation). So at the end you will get .../geschichte.html as external URL. Current/Experienced Behavior: The alias value is hidden in the page properties of the page. So, from all views which are available in Sites console, you don't see this important value at one glance. If you have an external localized URL and want to figure out which page in AEM is behind, you need to open page properties of the pages in the folder in question. This is not really efficient as it could be hundreds. Improved/Expected Behavior: With having the option to display the sling:alias property as a column at least in the list view, you could easily identify the page. 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: Introduce a search box to find completed workitems by model under Workflow Archive Use-case: Currently workflow archive tab lists ALL completed workitems. We have a Post-processing auto-assign workflow which fires 5000+ times everyday. Making really difficult to find specific other workitems completed daily. We couldn't sort/filter by model or find interested workitems of specific model. Current/Experienced Behavior: Workflow archive tab only lists ALL completed workitems. No ability to sort/filter/find specific workitems Improved/Expected Behavior: Introduce a sort button on Model column to sort by models. Introduce a "Search by Model" searchbox that ll filter the workitems based of selected model. The search box can be typeahead that prompts models which user can click. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS latest, likely affects any AEM version Customer-name/Organization name: SouthernGlazers Screenshot (if applicable): Code package (if applicable):
Hi there it would be great if on the 1st or even 2nd of the month if it were possible to have a global setting that would close off all timesheets instead of doing it manually.We produce financial reports hence are unable to have anyone running late to enter time into the previous month so this would be amazing for us and such an amazing timesaver!
Everyone can make a mistake... as well as users who post updates. If I misspelled something, or want to change something in my comment I should be able to do so.
We would like to have the ability to download a pdf of the proof with comments attached
Description - When downloading an Analytics Project, the date in the .csv file comes in a UNIX format. This requires a formula in excel to convert to a readable date. Why is this feature important to you - I have users that are not technical and could benefit from a csv export on a preset Project. But they are unable to use the project dashboard because of this bug.How would you like the feature to work - Have a regular date fieldCurrent Behaviour - The date appears in UNIX format (which is not useful) for example Monday, July 3, 2023 will show as "1688356800000". This is not helpful or meaningful for any user. In order to convert the date to a normal setting I have to use a formula "=(CELL/86400000)+DATE(1970,1,1)" to convert the date.
We just began exploring Boards (Dynamic) and the team loves the filters, tags etc. We would like to be able to create reports using these tags even if it is a data dump to excel. Why is this feature important to you - We are taking for Milestones, Teams, and Priorities it would be so helpful to have this available to report on. How would you like the feature to work - Choose the Tag field in a Custom Report and export or create a new Workfront report in a Dashboard. Current Behaviour - Currently, this is not available. Thank youAngie
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
