Product ideas | Community
Skip to main content

10000 Ideas

LuckyPACNew Participant

is there a way to have Workfront cc or BCC to myself when I submit an update? or warn me that I haven't hit submit?New

Description - make WF CC or BCC me when I submit an update, or some kind of warning that I have "draft" updates... Why is this feature important to you - so that I know I actually hit "submit" after entering information that is intended to go out to the requestor or team- and that I don't come back to my desk Monday morning wondering why no one has responded, and then I open WF and dig into the request queue, and open the actual "updates" tab, and discover an unsent "draft" . but of course that's never happened. How would you like the feature to work - as above. either CC or BCC myself upon hitting submit, so I can see in my email that I sent a message... or a warning that I have unsent messages... or both.  Current Behaviour - if I navigate away from an update without hitting "submit" ... it just sits there. and if I go get coffee and start working on something else- perhaps I go to the "request details page to make sure I am not missing important details... and then go make sure the work is finished and saved in box, and then.. I get 7 steps away, and the goldfish that is my brain forgets to navigate back to "submit" and then... nothing. and I have no way to know that nothing happened except to randomly open that update tab again. help a goldfish out! send me a cc and a warning message... 

SrijeetMiNew Participant

Integrate AEP with Cross-Domain & Mobile User TrackingNew

Let me know your thoughts on cross platform / App tracking I have developed a Cross-Domain & Mobile User Tracking Platform 🧠📱💻In today's fragmented digital world, understanding our users across websites, apps, and devices is no longer a luxury—it's a necessity.That’s why I’m excited to share what I’ve built:👉 A privacy-aware, cross-domain + mobile user tracking platform Designed for marketing teams, data analysts, and tech-driven businesses that want a unified view of their users — no matter where they come from.🔍 What it does: ✅ Tracks users across multiple domains and platforms✅ Links mobile app sessions with web visits in real time✅ Offers a beautiful, customizable dashboard with rich filters, analytics, and export options✅ Supports GDPR-compliant tracking and real-time logs📊 Whether you're running multiple brands, client websites, or want to boost your personalization strategy — this platform puts identity resolution, event analytics, and domain insights in one place.💡 Use cases:B2B marketing with multi-domain funnelsAgencies managing multiple client propertiesSaaS products combining mobile and web trafficCustom CDP and CRM enrichment🔐 Bonus: I’ve built it with privacy and scalability in mind from day one.I am looking for early adopters, partners, and beta testers.👉 DM me if you'd like a demo, want to try it out, or explore white-label opportunities.Let’s make user intelligence smarter, not creepier. 🙌

StaciCo
StaciCoNew Participant

Collapsible Navigation Bars in Adobe Workfront HomeNew

Description of change you want to see:I would like the ability to expand or collapse the various top and side interface elements on the Adobe Workfront home page—specifically, the Adobe unified experience bar at the very top, the Workfront top navigation bar, and the "Home and Priorities" left-side panel. Currently, these elements take up significant vertical and horizontal screen space and cannot be hidden or minimized.Why is this feature important to you:This feature would greatly improve usability and workspace efficiency. The persistent interface elements reduce the available area for viewing and working on tasks, especially on smaller screens or laptops. Having the option to hide or minimize these sections would allow for a cleaner, more focused working environment and improve the user experience—especially for users who spend most of their time within the task list or dashboard views.How would you like the feature to work:I would like to see collapsible or toggle-able interface sections—similar to how the object navigation panel on the left side of object pages (like projects, tasks, etc.) can be expanded or collapsed. Ideally, there would be a small arrow, icon, or hover-triggered control to expand or hide each major UI section. The user's preferences (collapsed or expanded) could also be remembered across sessions for convenience.Current Behaviour:Currently, the Adobe bar, the Workfront top navigation, and the Home and Priorities side panel are fixed and cannot be minimized or hidden. This results in a cluttered interface and reduced usable screen space, which can make navigating and managing work more cumbersome.

AnkitJasani29
AnkitJasani29New Participant

Collaborative Audience Building with Version History and Comments in Adobe RTCDPNew

Description:Introduce the ability for multiple users to collaboratively build and refine audience definitions in Adobe Real-Time CDP with support for version history, change tracking, and inline comments.This feature would help cross-functional teams (marketers, analysts, data scientists) work together more efficiently while ensuring traceability and reducing errors in audience logic. Why is this feature important to you:Audience building often involves multiple team members, and right now, it’s hard to track who made what changes or why.Sometimes, edits overwrite each other or lead to confusion without proper documentation or context. How would you like the feature to work:Each saved audience should include a version history, showing what was changed, when, and by whom.Users should be able to leave inline comments on specific filters or conditions (like commenting in Google Docs).Rollback functionality should allow users to restore a previous version if needed.Notifications when changes are made would help keep teams in sync.Current Behavior:Audience building is a single-user experience with no built-in collaboration tools or history tracking.Teams must rely on external documentation or naming conventions to manage edits - which is prone to human error. Use Case:A global brand's marketing and data teams are collaborating on a holiday campaign audience.The analyst creates the initial logic, the marketer adds refinements, and both leave comments explaining choices.When the campaign under performs, they review the version history to identify what changed and when - leading to quicker iteration.

武彦高田New Participant

Request to add functionality to make the default workflow package name unique to prevent collisions when multiple users execute "Publish Now" simultaneously.New

Request for Feature Enhancement (RFE) Summary: Request to add functionality to make the default workflow package name unique to prevent collisions when multiple users execute "Publish Now" simultaneously. Use-case: When multiple users manage publication using the "Publish Now" option at the same time, the default workflow package name is duplicated, causing conflicts. This results in publication failures and error messages displayed to users. Current/Experienced Behavior: A conflict error occurs because the same workflow package is used in multiple requests when they are made simultaneously. As a result, the following errors occur:  - "Not enough to manage publication" is displayed to users Improved/Expected Behavior: The expected improvement is to ensure the default workflow package name is unique, preventing conflict errors. For example, the workflow package name could include the user name and current UNIX time to guarantee uniqueness. Environment Details (AEM version/service pack, any other specifics if applicable): Environment: cm-p121411-e1208866 (Production) AEM Release ID: 20133 (Current Latest Lease) Customer-name/Organization name: Panasonic (Org Name: panasonicglobal) Screenshot (if applicable): Code package (if applicable):   We are currently in the process of migrating from On-Prem to AEM as a Cloud Service, and only about 10–20% of the migration has been completed so far. Encountering this kind of issue at such an early stage raises serious concerns about the stability and feasibility of the full migration. Once the migration is complete, approximately 620 users are expected to use the system. It will be virtually impossible to communicate and enforce the current workaround across such a large user base.

Tethich
TethichNew Participant

AEM Author Bookmarks featureInvestigating

Request for Feature Enhancement (RFE) Summary: Ability to bookmark things in AEM Author Use-case: All types of Touch UI activities Current/Experienced Behavior: Not often you can find yourself working on mid or long term implementations of features if you are a developer, or often working on a specific set of pages and assets if you are a content author, or continuously doing regression testing on specific points of the solution as a tester, or purely having to do only with a small portion of "everything" and not usually go in the entire content or solution all the time.In these often situations I found that the person working on that specific area tends to have lots of browser tabs opened, trying to go back and forth between them to do their work, to do investigations, trying or find things out, oftenly doing mistakes or forgetting where things were, and spending lots of time to untangle stuff and to make sure he is looking in the right place each time before actually addressing the actual underlying need he has. Improved/Expected Behavior: I propose that AEM would provide the possibility to create shortcuts/bookmarks lists within AEM. Different points in AEM should contain a Bookmark button (which points ?, that is something to be analyzed further). Clicking on this button should open a simple Dialog containing two fields for the user to fill in: name, which will be the visible label of the bookmark and group which will be the bucket list where the bookmark will be added to. Environment Details (AEM version/service pack, any other specifics if applicable): I believe this will beneficial as it will increase and boost productivity once the user can create his own lists of places to rapidly go to, not waste time to find same things each time and also avoid doing mistakes as it may happen that he might not go or look at the right place at some point. Example:Assuming I am working on some Dynamic Media implementation, and I often need to go to Tools, to the Dynamic Media cache invalidation page. In the same time I have a huge content of tons of sites but I only need to work on few 5 to 10 pages within the entire content hierarchy. Same for Assets, I only need to work with some specific assets, lets say some Content Fragments that I need to edit, save and publish. Plus, I have some config files stored in JCR and managed through some custom Coral UI tool built in-house. All of these places require for me to navigate to them each time and also take an action on them. Would be good to have a Bookmark button on each of these places so that I can save a bookmark of it. And then visualize all the bookmarks from a single place in AEM. And from there I can always quickly navigate to where I need.Below I added some example screenshots. But I imagine the Bookmark button to be available in way more places within AEM. Customer-name/Organization name: tethich.com Screenshot (if applicable):     Code package (if applicable):  

User Expiry after 6 months of no loginNew

In the Omniture Legacy UI,  there is an option to expire a user after a set amount of days (I have a screenshot I can provide). It would be helpful to be able to utilize the same functionality within the Admin Console, specifically Adobe Analytics, to ensure that external users are expired after a certain number of days (ideally 6 months), but ONLY if they haven't had any activity in the last 6 months.By having to expire every external user after 6 months, we are facing many users being locked out every 6 months, requiring our User Admins to unlock them, as well as not allowing them within the tools in the interim. If we changed the solution to only expire the inactive users, we would prevent time lost and would properly expire only those who required it. ----------------------------------------------------------------------------------------------------------------------------The customer, General Motors, requested a product enhancement for Adobe Analytics to automatically expire users after 6 months of inactivity. This feature is available in the Omniture Legacy UI but not in the Admin Console for Adobe Analytics. The current process causes unnecessary user lockouts and administrative overhead.**Customer Impact:**- Users are being unnecessarily locked out every 6 months, requiring administrative intervention to unlock them.- Only inactive users should be expired to prevent time loss and ensure proper user management. JIRA: [AN-369787] User Expiry after 6 months of no login - JiraSupport Ticket: E-001545785