Build better products with our product team
Description - We need better and more customizable real-time reportsWhy is this feature important to you - we can monitor live traffic and results on launch daysHow would you like the feature to work - more similar to google analytics, be able to see top page views and number of unique visitors on the page at that moment in time. breakdown of orders, revenue, products sold and locations of purchases.Current Behaviour - current real time reports are limited to three variables, you can't modify the visualizations, and doesn't work for variables that have processing rules. There isn't even a share link available.
Description - Permissions for segments / calculated metrics / etc are explicitly connected to the one suite under which it is created. On the surface, this makes sense... but many companies use Virtual Suites to control access to specific sites or regional variations within their global footprint... however, unless those users are granted access to the main global suite, they cannot use/access components (even when explicitly shared to those users). Being able to explicitly choose multiple suites on a component (particularly something based on completely "global" dimensions or metrics - like a "Referrer: Google" segment, or a PVs/Visits metric that could apply to any tagging profile) should be accessible from multiple suites. At the very least, there should be a way to all all virtual suites created from the main to have access, even if the main suite is not part of the user's permissions. Creating multiple copies of a segment or metric to use on every suite or virtual suite is massive overhead - sure, the component can be copied and a new suite can replace the old; but when an update has to be made, someone has to go through every item to apply the changes (and ensure that those changes are made exactly the same and to all variants). Segments, Calculated Metrics and other components need to be more flexible to allow us to maintain clean, optimized organization and sharing capabilities to ensure we don't have to repeat work and effort unnecessarily. Why is this feature important to you - The Components have come a long way from how they used to be, but there is still room for improvement to allow proper cross suite usage and permissions. Admins shouldn't have to choose between proper suite permission settings or having to duplicate efforts (and making maintenance so much harder) in order to ensure their users can access the segments or calculated metrics they need. How would you like the feature to work - I would like there to be a multi-suite selection available on components... where an item uses something specific to one tagging profile, this would allow only one or 2 suites to be connected. But for truly shared contents, being able to select all matching suite profiles would be best. There could also be an option to "auto-select" all sub-virtual suites from a global suites as part of the permission levels. Current Behaviour - Only one suite can be selected per component... while the components can be used on any suite, they can only be used if the user has permissions to the main selected suite of the component.... The Select Tracking Suite should be a multi-selection list, not just a single selection.
Request for Feature Enhancement (RFE) Summary: in AEM Assets - select renditions you want to download Use-case: when we have many assets selected, to avoid download all renditions, be able to select renditions we want to download Current/Experienced Behavior: in our DAM we have several renditions, we want to be able to select renditions we want to download to be more efficient Environment Details (AEM version/service pack, any other specifics if applicable): AEM as Cloud Service Customer-name/Organization name: Louis Vuitton Screenshot (if applicable): Code package (if applicable):
We have a requirement to customise headers in multiple different of areas of Workfront (via Layout Template) to support an enterprise Workfront instance globally across multiple solutions. There are two requirements:We can currently customise up to five fields in headers for Projects, Tasks and Issue/Requests but the list of options to choose from is very limited, to allow custom and system fields would be great - our specific requirement at the moment is for Resource ManagerWe have the requirement to add Resource Manager to other areas i.e. Resourcing and Team, but currently no customisation is available for these.
Description - Add the undo button like we currently have in the comment feature to the beta comment featureWhy is this feature important to you - we constantly use undo to correct/revise commentsHow would you like the feature to work - the beta feature should also have the undo buttonCurrent Behaviour - There's currently no way to undo the comment in beta.
Description - When a project owner or PM rejects time at the Project level - the user who submitted the time is notified by email so they can fix the time. Why is this feature important to you - Several of my agencies have the PMs review the time and they are ALL complaining that rejecting the hour and then notifying the user is too much work and takes too much time. How would you like the feature to work - Time is rejected and the user is notified via email and notifications Current Behaviour - The PM rejects the time and the user doesn't know it was rejected (and it isn't reflected in the timesheet either)
Description -Add a new widget that looks like this: Why is this feature important to you - Anything less than what we have now is "Something taken away from us". A LOT of folks depend on this type of "all-in-one" view of their assignments and requests. Losing it would cost us actual money. I posted this on July 7 in the New Home Beta channel but have heard nothing.How would you like the feature to work - Just make a widget that we can drag in to our New Home and use it as our sole widget if we choose.Current Behaviour - A hodge podge of unreliable and disconnected widgets that have zero governance.
Description - With the feature "make date range components relative to panel calendar", if you change the panel date range to a different amount of time (ex, 7 days to 30 days), the number of days in the date ranges in your table stay the same. For example, if I set my panel to a week, and bring in "last week", it works. But if I change my panel range to 30 days, the component in the table still stays at 7 days. Having the option to adjust the amount of days based on the number of days in the panel range would be useful. Why is this feature important to you - This is important because sometimes dashboard users want to look at different time periods, and if we want accurate YoY numbers, then we need to make multiple versions of the same panel. Having the number of days update automatically would prevent us having to make the same dashboard multiple times. How would you like the feature to work - Have an option when creating a preset date range to enable changing the number of days based on the panel calendar. Current Behaviour - Currently this isn't possible.
Description -Why is this feature important to you - this helps in debugging in case of any failures.How would you like the feature to work - File name should be made available in list of fields available so that it can be mapped to a field in schema.Current Behaviour - No such information is available so that we can link a batch to a file name and use that for debugging.
In the current set-up, data files can be sent to the Adobe Data Landing Zone, which in AEP is considered as an external cloud storage.The file there can be sent encrypted and decrypted by AEP.Huge data files (over 1gb) can be zipped. Issue now is that unzipping and decrypting the data files are 2 distinct steps, where ideally both can be handled immediately together.Enhancement request: unzip & decrypting files via 1 command/step
Request for Feature Enhancement (RFE) Summary: OOTB Option to search using tag in AEM Assets view for convenient filtering of assets within the AEM authoring interface. Use-case: OOTB Option to search using tag in AEM Assets view for convenient filtering of assets within the AEM authoring interface. Current/Experienced Behavior: Currently, tags can be added to any asset but searching for assets with a specific tag is difficult from the native UI. One has to generate a query and use custom reports to get this information. Improved/Expected Behavior: There should be an option in AEM Filters to search assets using a tag picker. This feature exists for auto generated tags like Orientation and Style but not for custom tags. PFA. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as Cloud service Latest release Customer-name/Organization name: Abbott Screenshot (if applicable): Code package (if applicable):
Description - I didn't see any keyboard shortcut to rotate a proof and the default one from Acrobat doesn't work (Ctrl, Shift, - or +). Our line of work constantly has elements that are horizontal or upside down on envelopes and other flat proofs. I wish WF Proof used the same keyboard shortcut to zoom in and out with the mouse wheel (Ctrl + Mouse wheel) as it is in Acrobat so I don't have to constantly think about which shortcut to use since Proof uses Shift and the mouse wheel. Why is this feature important to you - To easily navigate a proof using the keyboard for those of us who prefer shortcuts over the mouse to do everything. I am much more efficient in Acrobat than Proof. How would you like the feature to work:Ctrl, Shift, - or + keyboard shortcut to rotate a proofCtrl + Mouse wheel keyboard shortcut to Zoom in and out Current Behaviour - No shortcut to rotate. Different shortcut to zoom in and out than Acrobat (possibly a Chrome issue, but it seems like Proof shares other shortcuts with Chrome, it just depends on if you are in the proof itself or not)
Description - Harness the power of data analytics using Workfront Reporting or Fusion to systematically extract and categorize proof comments within a specified timeframe or based on other filters like file name or version. This endeavor aims to pinpoint areas ripe for improvement, refine training modules, and optimize processes by analyzing comment interactions and resolutions at critical stages. Moreover, this will allow us to collect a robust data reservoir to fuel AI-driven insights in the future. Adobe confirmed this isn't possible within Workfront reporting or Fusion's API capabilities. Why is this feature important to you - Collecting data to improve efficiency moving forward How would you like the feature to work - Run a report on all comments using various filters and have native columns available that show comment text, the proof version number and file name associated with the comment (NOT the latest version of the proof like we can see now with custom reports). If we can gather all this data into Excel that can be plugged into AI later to gain insights, this would be really helpful. Current Behaviour - Not possible at the moment per support
When utilising API developers note: the following endpoints: Get Email by Id, Get Email by Name, Get Emails are only able to retrieve the subject line of emails that have been created as a template but does not have the ability to pull the subject lines of campaigns that have been created for A/B testing or a Champion/Challenger test. As per the developer notes below there is currently no way to pull the test subject lines and all these fields are returned as a blank. This is a mission critical reporting metric for any EMS (Email Marketing System) and should be something that comes out the box. The functionality must be available because this function is possible through RCS, however is not possible through the API currently. Developers noteIf an email is part of a program that is using Email Testing (A/B Test, or Champion/Challenger Test), then that email is not available for query using the following endpoints: Get Email by Id, Get Email by Name, Get Emails. The call will indicate success, but will contain the following warning: “No assets found for the given search criteria.”This functionality would improve reporting adding more value to the product and the available data.
Zusammenfassung der Funktionsverbesserungsanfrage (RFE): Currently the system only delivers ootb the option to download - Renditions (which include every rendition, even the unnecessary system renditions like for example the thumbnails) - Smart Crops (which include ALL the smartcrops)- Dynamics (were Presets can only get downloaded one at a time) Anwendungsfall: A User wants to download 100 pictures, but only a specific rendition or smartcrop. Lets say the16:9 Smartcrop for all of them. Aktuelles/erlebtes Verhalten: The Download option does not tell the user what this all contains.He will get every available rendtion (even those that are only useful for the system) and every smartcrop that is available for his selection. He does not see which options his download will contain. He can not opt out of the unnecessary options. Verbessertes/erwartetes Verhalten: The download dialoge needs to have sub-options that make it possible for the user to only download what he wants. It should be possible to limit the renditons in this sub-options dialoge, so the system renditions are not automaticly in the download. The Dynamic Presets should be also be available as checkboxes, so the user can download multiple presets at a time.Also, the image modifier pannel is not very user friendly. For example, the https://landing.adobe.com/en/na/dynamic-media/ctir-2755/dynamic-assets.html site displays how such a selector could look like. Choose your own Background, quality factor, format... It is hard to demand from every user to understand the image modifiers and them use them correctly Umgebungsdetails (AEM-Version/Service Pack, ggf. weitere Angaben): 2023.9.13665.20230927T063259Z Name des Kunden/der Organisation: medi GmbH & Co. KG Screenshot (sofern zutreffend): Code-Paket (sofern zutreffend):
Request for Feature Enhancement (RFE) Summary: Add a "Lock" button to the top rail in order to lock an experience more easily Use-case: Our content authors didn't even know they could lock experience fragments due to the button not existing in the standard location. Current/Experienced Behavior: There is a way to Lock experience fragments via the dropdown when in the editor for the page itself but you cannot lock it via the top rail lock button like you can for pages in Sites as well as with "Checkout" inside Assets. Improved/Expected Behavior: Lock button in top rail just like other content in AEM has. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.8 Customer-name/Organization name: Securian Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: 1) Being able to assign permissions to groups for Administrator-Roles and "AdobeIO Developers" 2) to enhance permission handing in AdobeIO-DeveloperConsole Use-case: Imagine: 20 program, 20 different partner-companies. Every partner has 10 developers and devops whom might need to raise tickets for their environment (1 out of 20). The role to be able to Create or See support tickets is "Support Administrator". Generally one would think to create 20 groups and add 10 people to each of these groups. These groups allow : AEM Administrator access (on DEVs and STAGE) Support Administrator permissions But this is NOT possible! You need to create these 20 groups and assign 10 people each.But then you have to add "Support Administrator" to 200 individuals separately.That makes NO SENSE! In AIO-developer-console it is similar - as all these DEVS cannot be given "Full admin in the ORG".Now you need 3 devs for each project to be able to create and maintain AIO-projects.The assignment could again be done using groups (one would think) - but one needs to do that individually!And - once a project in dev-console is created by one dev (once he has the right permissions - and some APIs do not even provide profiles!) - only THIS developer and the FULL-ADMINS can edit/maintain this project.All other developers only have READ ONLY to the project - and would have to recreate it to make changes! Current/Experienced Behavior: current understanding and behavior:"when you add an admin, you will select one account for the job, not a group. there's no other option in admin console for this" Improved/Expected Behavior: Being able to assign permissions to groups for Administrator-Roles and "AdobeIO Developers" Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Various Screenshot (if applicable): Code package (if applicable):
Demande de résumé des améliorations des fonctionnalités (RFE) : Having the ability to clone one environment to another one Cas d’utilisation : each 3 months we have to align the environment from PROD to STAGE or from PROD to DEV for all our digital world(from STAGE to DEV and for starting project DEV to STAGE, STAGE to PROD is also usefull) Comportement actuel/expérimenté : today we use the feature of content copy - but it's taken around 4 days and the feature is not done for that. Comportement amélioré/attendu : have a feature of cloning, duration expected : less than one day Informations sur l’environnement (version d’AEM / service pack, et autres informations spécifiques si applicables) : AEM Cloud Nom du client/de l’organisation : Nathalie Riasse / Louis Vuitton Copie d’écran (si applicable) : Package de code (si applicable) :
Request for Feature Enhancement (RFE) Summary: Add multifield support to content fragments Use-case: Sometimes, using nested content fragments just makes no sense to editors. Our case: making a cooking recipy. We'd like to break down the recipy into steps necessary to make a meal component (such as: mashed potatoes) including ingredients, and we have no need of reuse. If we'd split off the fragments into a seperate fragment, life for content editors becomes a lot more difficult - it's much easier for them to fill in everything inside of a single fragment view. Current/Experienced Behavior: No multifield is available in content fragments Improved/Expected Behavior: We have multifield available in content fragments, including the option to configure them in the model editor Environment Details (AEM version/service pack, any other specifics if applicable): All versions (but we're on 6.5 on-prem) Customer-name/Organization name: AmeXio (system integrator) Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Dispatcher read only view similar to Repository Browser to view stat file and caching configuration Use-case: Option to view content tree on dispatcher under /var/www/html for better troubleshooting of cache flush issues and general configuration Current/Experienced Behavior: No access to dispatcher apart from Splunk logs Improved/Expected Behavior: Option to view content tree on dispatcher under /var/www/html for better troubleshooting of cache flush issues and general configuration Environment Details (AEM version/service pack, any other specifics if applicable): AEM as Cloud Service latest release Customer-name/Organization name: Abbott Screenshot (if applicable): Code package (if applicable):
It would be helpful if annotations would appear if the user uses a segment or a quick segment to filter the data instead of just a dimension-level filter. I find that most in my organization filter at the panel level and not the dimension/metric level, so annotations that I have set up do not appear in those instances. They are still relevant regardless of where the filter is applied. In my attached screenshot, you can see that if the filter is set for the country site for Japan (where this annotation applies) at the metric level, the annotation appears. If the user utilizes the quick segment for the country site Japan, there is no annotation, although it is exactly the same data. The annotation that I built really should also apply here, but support determined this is the expected behavior for this feature.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK