Skip to main content

Filter by idea status

10000+ Ideas

Adilos-Cantuerk
Adilos-CantuerkNew Participant

Optimizing the Download optionsNew

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):  

Admin-console: Being able to assign permissions to groups for Administrator-Roles and "AdobeIO Developers" - and to enhance permission handing in AdobeIO-DeveloperConsoleInvestigating

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):