Product Communities

A HUGE thank you to ​@MikeEngel  for sharing all his knowledge on the Unified Approvals transition! We realize there were a lot of unanswered questions from the chat so we are working on a consolidated Q&A that we’ll post here later, as well as discussing additional webinars to address these!  As discussed today, access to Unified Approvals will be based on your Workfront contract renewal date, but if you want to get access earlier, reach out to your account team to see if you can recontract early! Below are a summary, links to the slide deck, recording, and resources! Senior Product Manager Mike Engel shared updates on the new Unified Approvals experience, bringing enhanced review and collaboration tools for both video and non-video assets. Mike demo’d the new experience, including annotation and collaboration tools. He also discussed the transition, which will allow teams to adopt it in stages (using both legacy and new approvals, as needed) as well as potential future capabiliti

Hi Team,We have a custom object related to closed leads that we use for a nurturing campaign. Currently: The custom object is linked at the Account level. As a result, all contacts associated with the account receives the email. Our goal is to have only the specific contact associated with the closed lead receive the email. We plan to eventually update the custom object relationship to the Contact level. Interim solution:Since the custom object already contains a Contact ID, is there a way to: Match/filter the Custom Object Contact ID against the Marketo Lead/Contact ID, or Use another Smart List-only workaround to exclude contacts who are not associated with that specific closed lead ? Any guidance on an interim solution would be greatly appreciated.Regards,Akshat

A huge thank you to everyone who joined today's Champion Chat: Things We Changed Our Minds About with Workfront! And an extra special shoutout to our amazing Workfront Champions - Carol ​@CarolMajewski , Kellie ​@KellieGardner , Monique ​@MoniqueEvans , Olya ​@OK18 , and Tim ​@TimWy1 - for being so open about their lessons learned, sharing their real-world experiences, and helping make our community such a welcoming place to learn. We're incredibly grateful for people like you who are willing to keep it honest and help others grow!   Panelist Questions & Answers: What's a Workfront hill you used to die on that you've since climbed down from? Panelists said they’ve shifted from rigid, one-size-fits-all approaches to more flexible, practical use of Workfront. They also embraced "good enough to launch" implementations and accepted that Workfront isn't meant to replace every system. What's a feature or capability you initially disliked but now love? Custom forms, groups/group admins,

I’d like to propose a fairly simple idea. We create reports with many OR sections. I would say it takes some time to go back over time to remember what each section was filtering for. There could be a simple solution where there is a label and description box for each OR section.

The Problem: If your company uses Workfront Data Connect on the Ultimate plan, you know it runs on an Adobe-managed Snowflake Reader Account. Because customers don't have admin-level database privileges on these instances, we can't create custom Snowflake Row Access Policies or Secure Views. This creates a huge security roadblock when trying to restrict sensitive data by team, region, business unit, etc.The Solution: Adobe should give its top tier customers native row-level filtering capabilities for Data Connect—either by provisioning provider-side Secure Views/Row Access Policies based on customer specs, or by adding row-level governance controls directly within the Workfront admin interface.Why Vote for This? Unlock Broader Usage: Safely roll out Data Connect insights to more teams without exposing restricted or sensitive rows. Tighter Security: Meet strict enterprise compliance and data governance standards natively. No More Workarounds: Stop building complex, costly ETL pipeli

Been thinking about this a lot lately, and curious how other AEM teams are approaching it.For years, we've poured effort into hardening the perimeter around our AEM environments — VDIs, VPNs, SSO, locked-down repos, strict PR gates. Classic castle-and-moat thinking: keep the outside out.But here's what's nagging at me: with AI coding agents now part of the daily workflow, files like CLAUDE.md, AGENTS.md, and .cursorrules have quietly become some of the most information-dense documents in the repo. Dispatcher configs, content fragment models, component architecture, business logic — plain-English descriptions of exactly how the system works.And that's the actual problem: these files usually don't get the same treatment as code. They're committed casually, reviewed loosely (if at all), and often live at the repo root where any contributor — human or AI agent — can read them. Unlike obfuscated code or config buried three folders deep, this is a plain-English map of your system: auth flows

When a quick filter is set to Exclude, it looks like an include filter. It is confusing when looking at reports.To address this, when creating a quick filter that is an exclude, can this have a visual indication that it is an exclude?Maybe make it Red rather then Blue. But conscious that some other accessible (not just colour) indication would be best to have also.At the moment, it isn’t able to be seen unless the filter is opened for editing and it leads to confusion, as it looks the same as an include filter.This is in the workspace in Adobe Analytics and the workspace in Customer Journey Analytics. 

⭐⭐ Congratulations to ​@ghowell15, AEM Champion of the Month! ⭐⭐Gary is one of those Champions who doesn’t just support his greater AEM community, but shows up and shows out for his fellow AEM Champions. Whether it’s stepping up to lead a session at The Skill Exchange, partnering with other Champions and Adobe Product team members on Perspectives articles, or actively participating at a Champion social event, Gary is a true pillar within the Adobe Champion community, and we wouldn’t be as strong without his leadership, dedication, and positive attitude.Want to see Gary in action? Check out his Skill Exchange session, “Scaling Content Creation with Product Launch Accelerator and Generative AI" on Wednesday, August 12 at 10:30am PT: https://reg.adobe.com/flow/adobe/skillx26/landingpage?source=COMMUNITY&sdid=Y2KRGJ1X

🙌 Congratulations to ​@gkalyan, AEM Champion of the Month - June 2026! 👏 🏅 Kalyan has gone above-and-beyond in the last year as an AEM Champion, stepping into multiple leadership roles in the AEM User Group Program, internal Adobe product feedback sessions, and Community advisory. He regularly raises his hand to help mentor new and existing customers and serve as an advocate of the Adobe CX Enterprise ecosystem, including as a speaker at internal and external Adobe events like Adobe Summit. Please join us in congratulating Kalyan for this impressive achievement!

In AEM as a Cloud Service (AEMaaCS), the out-of-the-box (OOTB) CIF component Commerce Retriever APIs currently return Optional.empty() for both a successful GraphQL query that yields zero products and an execution failure (such as timeouts, HTTP 429s, or transient connectivity issues).Because both scenarios produce the exact same return value, custom implementations have no supported way to differentiate between them. This prevents us from delivering a tailored user experience, such as showing a "No products found" message versus a "Service temporarily unavailable" retry prompt.Proposed Implementation Approaches (Flexible):We leave the exact contract to Adobe Engineering's discretion, but viable options include:- Exposing a separate error object or status indicator.- Throwing a specific checked or unchecked exception on execution failure rather than swallowing it into an empty Optional.- Providing a metadata wrapper alongside the result.

Join Senior Product Manager, ​@LilitM  for this deep dive into one of the most impactful innovations in Workfront Planning: Global Record Types. This session walks through how global record types enable you to standardize key data structures across workspaces while still supporting the unique needs of individual teams. If you weren’t able to attend live — or want to revisit any part of the session — you can access everything below: Intro Slide Deck with Resources & Event Links Lilit’s Slides Webinar Recording One of the requests we discussed was gaining access to the companion spreadsheets that support the Adobe Summit - Marketing Planning and Metadata Strategy Lab. We’ve attached them as links below:Taxonomies Activities CampaignsAs Lilit mentioned during the session, we’d love to keep the conversation going here in the community. What questions do you still have?  Are there any use cases you'd like to explore further?  What features are you most excited about? Drop your thoughts,

Curious what actually goes on inside a Workfront user group session? Here's a taste. In a recent Workfront Central session, Deborah Baker (Marketing Workflow Leader) and Megan Lehman (Workfront Developer) walked through how they built a fully connected marketing system of record using Workfront Planning, Core, and Fusion, the kind of hands-on, behind-the-curtain walkthrough you won't find in the docs. This recap is the technical companion to their Perspectives article, Designing Workfront adoption for the long haul, which covers the strategy behind the build: people first, process second, system third. Here's how it comes together in practice.The challengeThe team set out to build an end-to-end template environment for a marketing-heavy organization, a major consolidation effort that condensed multiple separate intake requests into one streamlined flow. A request now comes in through Planning, spins out a program, a hero deliverable, and a request queue for one-off derivatives tied bac

Hi everyone,We are trying to better understand the actual behavior of the “Trigger after batch audience evaluation” option in AJO, because in our case it does not seem to behave the way the documentation and UI tooltip suggest.From what we have observed, if the first run of a daily journey happens before the export job for that day is available, the journey ends up using the previous day’s snapshot instead of waiting for the current day’s audience evaluation/export to complete. After that, each subsequent run appears to keep following the same pattern, since it only checks whether a newer snapshot is available compared to the one used in the previous execution.That makes us wonder whether this feature is really behaving as expected. In practice, it seems that if the first run happens too early, the journey can stay one day behind indefinitely, which makes the configuration much less useful for daily journeys than we would expect.The behavior we are expecting is that the journey should

What happens todayThe Workfront MCP Connector refuses to write any object name containing a colon, forward slash, double quote, or curly brace. This applies to both workflow_create_any_object and workflow_update_any_object.Workfront itself accepts all of them. The UI saves them, the database stores them, and the connector's own read path returns them intact. Reads pass. Only writes are blocked.Where it standsI raised this with Support. The engineer reproduced it and took it to Product, who confirmed it is a known, open discussion covering all Workfront object types with no decision yet. It is currently treated as a feature request rather than a bug, on the basis that the validation follows OS-level filename restrictions.That reasoning is worth a second look. The blocked set does not match any OS restricted set, curly braces are blocked but are legal in filenames on Windows, macOS and Linux, while several genuinely reserved characters are not blocked at all. And object names are not fil

What a fabulous discussion yesterday! Many thanks to Darrel Smith from WK Kellogg and Emily Kellman-Kessel from Adobe.com for sharing their experiences and insights on Generative Engine Optimization (GEO), as well as to our moderator, Karthik Muralidharan, for keeping the conversation flowing and engaging!If you missed it or what to revisit any part of the session, you can access everything below:Slide Deck PDF Webinar Recording Also, don’t miss out on our follow-up session on August 20. AI Search and Discovery Forum: Inside the Future of Brand Visibility. We’ll review the roadmap, recently released capabilities, customer success stories, and give an exclusive look at Adobe Brand Visibility. Register now! We’re looking forward to continuing these discussions and learning more from you. What are you seeing in the world of GEO? 👀

Dear AEM Community,Your time is precious, and we understand the importance of efficiency when it comes to troubleshooting issues with AEM.That's why we're excited to again bring you our carefully curated collection of Top KCS (Knowledge-Base) Articles for July 2026, designed to help you resolve common challenges swiftly and effectively.Our Top KCS Articles are your shortcut to:Quickly identifying and resolving recurring issues. Accessing expert insights and best practices for AEM. Streamlining your troubleshooting process for maximum productivity. Empowering yourself with the knowledge to tackle any AEM-related problem head-on.Why spend hours searching for solutions, when our Top KCS Articles have already done the heavy lifting for you?Let us help you save time so you can focus on what truly matters – empowering you to provide a truly personalized experience to your customers with AEM.Start supercharging your problem-solving skills today by exploring our Top KCS Articles!Take a look:An

Dear Adobe Campaign Community,Your time is precious, and we understand the importance of efficiency when it comes to troubleshooting issues with Adobe Campaign.That's why we're excited to again bring you our carefully curated collection of Top KCS (Knowledge-Base) Articles for July 2026, designed to help you resolve common challenges swiftly and effectively.Our Top KCS Articles are your shortcut to:Quickly identifying and resolving recurring issues. Accessing expert insights and best practices for Adobe Campaign. Streamlining your troubleshooting process for maximum productivity. Empowering yourself with the knowledge to tackle any campaign-related problem head-on.Why spend hours searching for solutions, when our Top KCS Articles have already done the heavy lifting for you?Let us help you save time so you can focus on what truly matters – creating exceptional campaigns with Adobe Campaign.Start supercharging your problem-solving skills today by exploring our Top KCS Articles! Take a lo

Analytics has always had a lot of tools to answer questions. However, what has been lacking is a coworker that collaborates with you on the problem.Introducing agentic analytics in Adobe CX Enterprise Coworker! This isn't just another agent to query and forget; it's an intelligent partner that retains context, reasons through each step, and accompanies you from the initial question to the root cause.This represents a significant shift towards complex analysis, worked side by side.See it in action here: 

Building a Decisioning rule or a ranking formula is only half the job. The harder question is always the same one: will it actually behave the way I think it will?Until now, the honest answer was “let’s find out in production” — you’d wire the rule into a decisioning strategy or a campaign, push it out, and watch the results trickle in. That’s a slow, nervous way to work, and it’s an expensive one when a subtle logic error means the wrong offer reaches the wrong profile.Simulation changes that. You can now test any rule or ranking formula against sample or AI-generated data before you put it to work — right inside the authoring experience, in a few clicks, with no hand-built data and no guesswork. This post walks through both: simulating a rule to confirm it qualifies the right profiles, and simulating a ranking formula to confirm it orders your offers the way you intend. The UsecaseConsider a common scenario. You’ve authored a rule that should only apply to profiles whose favorite cat

At the request of some other posters here in the Community, here are some learnings from my first build of a custom Workfront to Jira integration using Fusion. All comments reference Jira Cloud, and reflect my candid, hopefully amusing, learnings from this trial project.    Why did we not use the native Workfront to Jira integration? This article is what I send out to our internal teams when they ask if I’ll configure it for them. https://www.putitforward.com/how-to-integrate-workfront-and-jira#toc-challengeswhenconnectingworkfronttojira  Also: Per Adobe Support, the connection user must be a full admin account and I operate on the principle of least-privilege. Unmonitored accounts should never be administrator level. (That’s my soapbox, and I’m staying on it.) 20/20 Hindsight – What would I do differently? Build a bigger POC – When I did my initial feasibility assessment, I thought I’d be able to use the existing connectors included in Fusion that are pre

Test

Thank you to everyone who joined our latest Content Supply Chain User Group meeting! We were joined by Lilit from the Adobe product team for a live demonstration of Workfront Planning and a great discussion about how it works alongside Workfront Workflow.Here are some of the main takeaways:Workfront Planning as the strategic layer. Planning brings ideation, campaign planning, prioritization, and portfolio-level visibility into Workfront, while Workflow remains the primary place for managing project execution. Flexible structure and governance. Teams can create workspaces and record types to represent campaigns, tactics, events, products, or other types of work. Global record types allow operations teams to define a consistent structure that can be used across multiple workspaces, while leadership gets a consolidated view across teams. Connecting Planning and Workflow. Planning records can be connected directly to Workfront projects without Fusion, and the connection is visible from bot

Problem: the OOTB Content Fragment component makes every field of a referenced fragment editable in the Universal Editor. There's no supported way to expose some fields (title, body) while protecting others (slug, featured image, metadata owned by other teams). This is the default behaviour, not an edge case.I went down a deep rabbit hole and tried several approaches: The Field Contract Pattern worked: A proxy component whose editables point at the component's own node (so the rail resolves a model I control, not the CF schema), reading the fragment live for display and writing approved fields back via a ResourceChangeListener. Hidden fields simply aren't editables anywhere — enforcement by construction.Full writeup with code: Selective Content Fragment Editing in AEM Universal Editor: Building a Field-Level Editing ContractOpen question for the community and Adobe: is there a supported way to scope the CF schema returned to /details per editing context, or a cancellable pre-persist ex

Issue Description:While testing the Marketo UI Beta, I noticed an inconsistency between different rich text editing experiences. When creating a new Snippet, the editor continues to display the legacy Rich Text Editor toolbar and icons. However, Rich Text Tokens are using the updated Rich Text Editor experience with the new toolbar design and iconography.Current Behavior:Snippet editor continues to use the legacy Rich Text Editor UI. Rich Text Tokens use the updated Rich Text Editor experience.Expected Behavior:The Snippet editor should use the updated Rich Text Editor experience, consistent with other rich text editing areas such as Rich Text Tokens.Question:Is this expected behavior because Snippets are not yet included in the Rich Text Editor migration, or should this be tracked as a UI Beta issue? Impact:Creates an inconsistent editing experience across Marketo UI Beta components.  

We have just enabled Adobe storage and frame.io for approvals/reviews. we have noticed quite a few oddities, but one that should be easily fixable is changing the email that gets sent out to approver/reviewers.  We noticed that when sending to gmail, and probably other services, the email displays very large:Hi ____, _________ wants you to review the following for approval:[Message clipped]  View entire message This is not a great experience for the reviewer and forces them to click the link to actually get to the review link.According to a search, gmail does this for messages over ~100kb in size. I downloaded my email and it was ~300kb.  It seems like an easy change to modify these emails so they display properly.