Build better products with our product team
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.
Description - Provide a way on Project Templates at the Project / Task and Issue levels to limit which users can be assigned. Could be done by setting a "Select Users from..." and allow the project owner / template owner to select groups, teams, users, or access levelsWhy is this feature important to you - Some teams are assigning work to people who do not actually do the workHow would you like the feature to work - Act in similar way to using the Typeahead FilterCurrent Behaviour - Anyone can actually be assigned
There isn't an efficient way for team members to log time so there is loss of adoption and increase of friction. How I would like the feature to work: Currently assignees are required to click multiple times and navigate away from the storyboard to log hours; timesheet is not flexible enough to include parent task visual, which would help Agile task owners who have repeatable tasks in multiple stories.
My Tasks widget could be grouped by Project Name and Parent Task (helpful for Agile user stories that have tasks with the same name). The user could log hours inline without having to open each individual task. This feature is important because currently there is no efficient way for assignees (especially on Agile teams) to log actual hours spent, reducing adoption and increasing friction.
Description -Why is this feature important to you - Our data engineering team is working to leverage system data using the API but cannot access everything they need without running reports.How would you like the feature to work - Same as all the other data. Accessible via API call.Current Behaviour - Reports are required to pull the data.
Upgrade the "Core - Enters Viewport" to match GTM behavior, precision and getting the "Click Element" variable into AA. Cf. support ticket linked attached.
Hello, We are in the process of implementing the timesheet functionality within Workfront. If users have to input actual work in the timesheet and then update percent complete on their tasks, it would make more sense to have the actual work on the task update the percent complete or percent work complete on that task. I know there isn't a field for calculating the amount of work complete but I think it would be beneficial to have that option and have it be auto populated by using the actual work against the planned work. We don't want to inconvenience our users by making them update both the percentage complete and the actual work on their tasks.
Description - Allow users the opportunity to configure the row heights and column wrap/unwrap function on tasks/views. Why is this feature important to you - When there are a lot of updates on a task it's visually overwhelming and requires a lot of scrolling by the user.How would you like the feature to work - Give users the opportunity to set the number of lines for a row like in Outlook views, adjust the row height by dragging the grid line or right-clicking on the row and entering a numerical value, plus enable wrap/unwrap functionality on a column like in Excel. Have a visual indicator like an ellipsis so the user knows there's more information in that field than is being displayed. Use hover text functionality so that when a user hovers over that field, the hover box appears with the entire field contents.Current Behaviour - We can only adjust a column width so there's a lot of scrolling.
I have been a Marketo for many years, and have yet to figure out why there is no recipient time zone functionality for Default and Event/Webinar Program types (only for email) - is this something that is in the pipeline? Or am I missing something as to why this will never be possible?
Description - There is a helpful feature in Tealium IQ TMS where you can see visually in UI what is the exact order of operations of your various rules, and you can simply drag and drop to change their order. Why is this feature important to you - Helpful because we don't have to then go to individual rule to check the order priority we have set. We can see in UI directly and change it. How would you like the feature to work - A drag or drop interface for all currently enabled rules, which can be changed to different scopes easily.Current Behaviour - Rule ordering allows you to control the order of execution for rules that share an event. Each rule contains an integer that determines its order priority (the default value being 50). Rules that contain lower values for their order are executed before those with higher values.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.