Build better products with our product team
Description - Two separate asks here. One is that currently when a prop is turned on within report suites, it will permanently reside in the default view, this is not true to Events and eVars. The props being stuck permanently on is causing confusion as we only intent on looking at the enabled eVars and any missclick to "add new" will muddy the report suite. Second request is to have a description field visible on eVars from within report suites (same as it is for events). It would be helpful to be able to view a quick description of the eVars as we can for events and would save time maintaining an SDRWhy is this feature important to you - Will clean up our data and save timeHow would you like the feature to work - prop=disabled, then remove from report suite default view, Description field added for eVars page (same as events)Current Behavior - prop=disabled, prop permanently stays on default view, this is true for as many props as you enable
Currently in Workspace, we have Date Ranges like "This Month", "Last Month", "Last 7 days", etc. But these date ranges are relative to your current date.What I would like are date ranges that are relative to my project's date range.Example 1:Today is 15 August 2017.I run a report for 1-31 July 2017.The "Previous Month" date range would show the data for 1-30 June 2017, i.e. the month previous to 1-31 July 2017.Example 2:Today is 15 August 2017.I run a report for 1-31 January 2017.The "Previous Month" date range would show the data for 1-31 December 2016, i.e. the month previous to 1-31 January 2017.And similarly for "Next Month".And similarly for other time periods, e.g. day, week, month, quarter, year.
It would be useful to be able to export reports from the Analysis workspace into AWS S3 or some other storage service, since the only option, as of today, is to export via email.Although you can use the data warehouse tool to export data into an S3 bucket, the analysis workspace offers some features that are unavailable in the data warehouse, like the use of calculated metrics.
Description - Provide visibility of the active user connection(s) to the AEP datalake. Why is this feature important to you - Feature is important for administration of the AEP sandbox to understand what the active connections to the datalake How would you like the feature to work - Provide an API or UI view of the active connections to the AEP datalake. Also provide the ability to drop the user connection to the AEP datalake. Current Behaviour - Unable to manage the active connections of users who are connected to the AEP datalake.
Request for Feature Enhancement (RFE) Summary: Custom Metadata Schemas and fields developed in AEMaaCS should be visible in Assets Essential console as well. Use-case: Currently we are not able to see any of the custom buttons or menu along with the metadata schemas designed in AEM in the Assets Essential console. Current/Experienced Behavior: Any custom metadata schema and fields developed in AEM Assets Cloud console are not visible in the Assets Essential console. Improved/Expected Behavior: Any custom metadata schema and fields developed in AEM Assets Cloud console should be visible in the Assets Essential console. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: Credera (Formerly TA Digital) Screenshot (if applicable): N.A Code package (if applicable): N.A Original Query Link - AEM Assets Essentials (Experience Manager Assets) vs Experience Manager - Custom UI Handling
Description - Need to adjust task rejection settings in order to consolidate feedback from multiple reviewers at a single stage. Why is this feature important to you - This should operate the same as the task approval does when multiple approvals are required at a single stage. This will enable the reviewers to add all feedback before the task status is reset, which will streamline revision time and keep the approval request in the work list of all required reviewers until all have made a decision to reject or approve. How would you like the feature to work - Just like the approvals do now. Task status will only reset to new once all reviewers have made a task approval decision, either approve or reject. Current Behaviour - Right now the task is immediately reset if any approver selects reject, which results in unnecessary revision rounds and confusion among multiple reviewers who rely on their worklists to track action items.
Description - Need a built-in standard way for assignees to see all of their logged hours per assigned taskWhy is this feature important to you - The assignees currently have no easy way to view the logged hours on their tasks without going one task at a time.How would you like the feature to work - There should be a built-in report or area for assignees (and managers) to view all logged hours and timesheets across the assigned tasks for a specific user. The assignee would only be able to see their logged hours on their assigned tasks. They can go back in history to view all tasks and all times logged, as well as totals per week, per month, and a way to filter on days with no logged hours in case they missed some days of logging.Current Behaviour - User must open a task to get to the task options to see "Hours", currently no way to see "Hours" across all assigned tasks.
Request for Feature Enhancement (RFE) Summary: Locked pages should prevent other users from editing the content; however, it should allow the content to get copied because the content can still be viewed. A locked page should Only restrict other users from editing the page. Use-case: We have Toolkit area which guides our Authors on how each component works. Additionally, we provide many samples to help authors come up with ideas for building new pages. All of those pages — which we refer to as Toolkits. As we have locked all these pages to protect from any unauthorized changes, it also prevent our Authors to copy those samples or examples. Therefore, it will be good if locked pages only prohibit users from editing the content and yet permit copying. Current/Experienced Behavior: Unable to copy a page or content Improved/Expected Behavior: Allow users to copy a page or content Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: Ashish Grover / Fiserv Screenshot (if applicable): Code package (if applicable): /
Request for Feature Enhancement (RFE) Summary: Heap Utilization Warnings and graphs on Reporting console should match the heap memory usage on servers Use-case: The Cloud Manager Portal - Reports displays a System Monitoring stat for all the environments and servers in terms of Host, Network, Storage and Application. Sometimes it displays in warning "Heap size is 85% of the allocated memory"If you check the server in question, mostly the figures don't align - For instance in the publish server for which the warning was flashed the usage was around 35-40% which is way off the warning limits.Ideally there should be a strong co-relation between these 2 figures. Current/Experienced Behavior: The overall heap memory usage in /system/console/memoryusage does not align with the Reporting console in Cloud Manager. Improved/Expected Behavior: The overall heap memory usage in /system/console/memoryusage should align with the Reporting console in Cloud Manager. Environment Details (AEM version/service pack, any other specifics if applicable): AEM (6.5.0.20180328) | Adobe Experience Manager (6.5.18.0) Customer-name/Organization name: Credera Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Request to improve behaviour for View in Admin button during page editing. Use-case: When user clicks “View in Admin” he or she expects that the same page will be opened in sites admin. Usually pages have many children, so it takes time to find edited page again. Current/Experienced Behavior: 1. Open any page for editing (e.g. http://localhost:4502/editor.html/content/we-retail/language-masters/en/experience/arctic-surfing-in-lofoten.html) 2. Click “View in Admin” Opened parent page - http://localhost:4502/sites.html/content/we-retail/language-masters/en/experience Improved/Expected Behavior: 1. Open any page for editing (e.g. http://localhost:4502/editor.html/content/we-retail/language-masters/en/experience/arctic-surfing-in-lofoten.html) 2. Click “View in Admin” Opened edited page - http://localhost:4502/sites.html/content/we-retail/language-masters/en/experience/arctic-surfing-in-lofoten Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.20 Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Instead of free form field when adding a content fragment variation, provide authors a pre-populated list of variation titles to choose from. Use-case: Content Fragment Variation titles are often used across an application. Current/Experienced Behavior: Author must type in correct variation title Improved/Expected Behavior: Allow developers to provide a list of variations for authors to choose from Environment Details (AEM version/service pack, any other specifics if applicable): Cloud Customer-name/Organization name: UHG Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Enhancing Search Feature of Connected Assets with Path based search to Remote Assets in AEM 6.5 Use-case: Authors uses Assets finder in Media Library by using search features such as Keyword,Path,Tags etc. Whereas in Connected Assets 6.5 we just have search by Keyword|Tags but its not supporting Path based search which is a big degradation in author experience when they switch to use connected assets from AEM Assets Current/Experienced Behavior: AEM Author when using Connected Asset to fetch an Asset from Remote Asset unable to search Asset bu Path similar to Asset finder in media library Improved/Expected Behavior: Include Search feature similar to Asset Finder of Media Library Which is path based search in AEM 6.5.I hope this feature is available in CaaS. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 SP17 Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Enhancing the IP Allow Lists functionality in Adobe Program Overview for Experience Manager Use-case: Providing users with IP Whitelist access to specific domains Current/Experienced Behavior: Recommendation 1 - Improve how environments are applied for an IP Allow List Name. Currently, you have to go into the specific environments and add the IP for all relevant segments (author, publish, preview). Recommendation 2 - When adding an IP Allow List Name to the dispatcher/publish environment, there is no warning that this will stop all other users from viewing this environment. This can sometimes be an easy mistake with a significant impact. Improved/Expected Behavior: Recommendation 1 - Improve how environments applied are adding for a IP Allow List Name. Allow admins to add/remove environments in IP Allow List view provided below. Recommendation 2 - Add an alert for this scenario so users are aware before applying the rule. Environment Details (AEM version/service pack, any other specifics if applicable): Adobe Cloud Customer-name/Organization name: Openreach Screenshot (if applicable): Recommendation 1 - Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: As of now AEM author session is getting logout either user is active /inactive.is it possible to add in author a feature of “Pop-Up” to users (well in advance) informing about time out and allowing users to save work Use-case: it is useful for author to get notified to save their work. Current/Experienced Behavior: As of now AEM author session is getting logout either user is active /inactive. Improved/Expected Behavior: To add in author a feature of “Pop-Up” to users (well in advance) informing about time out and allowing users to save work Environment Details (AEM version/service pack, any other specifics if applicable): 6.5 cloud Customer-name/Organization name: Shell Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Currently asset management is interlocked with site management, i.e. moving assets in the asset module requires republishing of pages in the sites module instead of just updating the asset references in the affected pages, especially on Publish. Use-case: We have dedicated asset and site managers. When an asset manager moves an asset the site manager is required to republish the page(s) with this asset to update its references on the page. This can become a hassle when page(s) with the asset are being reworked. These pages are not ready to be republished. Due to this dependency asset and site managers cannot work independently. Current/Experienced Behavior: When assets are being moved, affected pages need to republished Improved/Expected Behavior: When assets are being moved, asset links on affected pages should be updated without the need to republish the page Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS latest, likely affects any AEM version Customer-name/Organization name: Munich Re Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Move/Copy of Context-Aware Configurations when a page is moved/copied Use-case: Pages with special CAC's (like header, footer ...) are moved/copied and all the CAC's have to be manually set again in the destination tree. Current/Experienced Behavior: When a page with specific Context-Aware Configs (set below it) is moved or copied then all the CAC's (below /conf) remain in the same place so the editors have to redo the configurations every time. Improved/Expected Behavior: It would be easier that when page (or complete tree) is copied or moved that also it's related CAC's (/conf) are also copied/moved. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS 2024.4.16145.20240430T082417Z Customer-name/Organization name: Pictet/One Inside Screenshot (if applicable): Code package (if applicable):
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.