Product Communities

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.

Velocity’s quirky treatment of null could drive a mortal mad. As a language aimed at web developers rather than “real” developers, VTL attempts to smooth over Java’s strict typing: it allows comparison across types[1] and blends false and null into a form of falsiness. We can work with or around those features. But it gets weirder: in versions including Marketo’s install[2], Velocity also prohibits creating new null references at runtime. There’s no real workaround for this one; ironically, to avoid related bugs, you must follow poor programming practices! Take a person with a single Opportunity:Field Datatype Value LodgingType String "commercial hotel" Host String "  Zaan Hotel  " PointsProgram String null City String " Amsterdam " Meals Boolean false  (Whitespace around the LodgingType and City is deliberate. And null is really null, not an empty string.) Here’s the raw output of ${OpportunityList}:{LodgingType=commercial hotel, Host= Zaan Hotel , Poin

Your Adobe Journey Optimizer experience could win you $50. 🎁We're gathering feedback from Journey Optimizer customers, and we want to hear from YOU, whether you're in the platform daily or driving the strategy behind it.Two short surveys are live now:✅ Practitioners: Tell us how you use Journey Optimizer's channels, capabilities, and workflows day to day (~5 min)✅ Decision Makers/Leaders: Share what drove your investment in Journey Optimizer and the business impact you've seen (~4 min)👉 Practitioner Survey: https://lnkd.in/gMqTBS85👉 Decision Maker/Leader Survey: https://lnkd.in/g9aJv--cYour input directly shapes what we build next. Every completed survey is entered into a random drawing for a $50 gift card.

Hi Real-Time CDP Community!Looking to sharpen your Adobe skills, discover new ways to work smarter with AI, and learn directly from Adobe experts and customers? Skill Exchange 2026 registration is officially open! 🚀  Adobe Real-Time CDP (alongside Adobe Experience Platform and Applications (Journey Optimizer and Customer Journey Analytics) sessions will be held on August 6th, with sessions across 7 Adobe products throughout Aug 5th-13th. A couple sessions you can expect to learn from: One Platform, One Customer From Insight to Impact: Building a Next-Generation Experimentation Program Building an Intelligent Activation Layer and Orchestration Drives Results See full Adobe Experience Platform and Applications session list here  Join us this August for: ✨ Expert-led sessions across 7 Adobe products 🤖 AI-powered tips and innovations 💡 Real customer stories 🎬 Live demos and practical takeaways you can apply right away 🤝 Opportunities to connect with fellow Experience Makers  Whether y

Description - While viewing all Project Tasks, having a dedicated Field/Column for logging Task HoursWhy This Feature is Important - Having the ability to log hours directly from the Project Tasks page and not needing to navigate to either the Task itself, or the Open Summary tab would be incredibly helpful. This would reduce User effort in logging time, while also removing any possible confusion for new Users navigating to the Task, and back to the Project, or navigation within the Open Summary tab.How the Feature Would Work - Added Field/Column to the standard Project View as a place for Users to log hours. This could be done via a button similar to the Status Icons that directly opens the ‘Log Time’ panel (without leaving the Project page). Alternatively this could be a Field where Users enter a numerical value that is then added to their Actual hours, and then removed from the Field. Current Behavior - Currently, Users need to navigate to the Task itself to log hours, or use the Op

In plenty of spaces in Workfront, when you search a list of objects, it feeds you all objects (active and inactive). This is particurarly true for filtering. I understand why we get everything and the kitchen sink, however it can be confusing and overwhelming. It would be helpful to visually represent what is active versus inactive. Some options:Gray out the names of inactive objects Add a symbol like an asterisk to the beginning of the object name (but not the end because these dropdown windows sometimes truncate names)

Hey Community! 👋If you’ve been looking for a dedicated tool like add_smart_list_rule_constraint in the Marketo MCP server to update the existing or a new smart list by applying the “Add Constraints” you won't find it listed in tool searches in the Marketo Engage MCP operations list.However, the capability is fully functional and easy to use it’s just absorbed into update_smart_list_rule. 🔍 How It Works Behind the Scenes There is no separate callable tool for constraints. add_smart_list_rule - Creates the rule shell. update_smart_list_rule  - Handles the constraint via its constraints array parameter. 📌 Important Note: While the Marketo UI allows empty constraint values, the Marketo API requires at least one value when saving. Passing a default value (like 'Web service API') satisfies the API requirement and can easily be updated later!Has anyone else been experimenting with the Marketo MCP server? Let me know in the comments! 👇Take a look on the discussion I had with the Claude

Under the Hood: Comparing the Official MCP Toolset to the REST APII’ve lived and breathed the Marketo REST API for years. In fact, I was so deep in the weeds that I actually built my own custom Marketo MCP before the official one existed. Back then, I was limited strictly to standard REST endpoints, since that was the only systematic way to work within in Marketo. So, when I finally got my hands on the official beta, I was dying to know: how does this new AI toolset actually stack up against the "old reliable" REST API?Whether you’re looking to supercharge an AI assistant for your team or just trying to figure out which integration path won’t break your workflow, understanding these gaps is huge. Let's dive into where they overlap, where the REST API still reigns supreme, and those cool spots where the MCP pulls off tricks the REST API can’t do at all.Just a heads-up: all of this is "as of now." Since the MCP is currently in beta, things can, and most likely will, change. Knowing the a

Canvas Dashboards are more than just another reporting option in Adobe Workfront. They offer a powerful way to visualize, understand, and take action on your work. However, since they function differently from traditional reports, many teams either avoid using them or never fully realize their potential.View the interactive, practitioner-focused session featuring Skye Hansen, Lead Functional Architect at Merkle, and Matt Mitchell, Principal Product Manager at Adobe. Discover how to use Canvas Dashboards effectively with clear, practical guidance, without getting bogged down in configuration details.Skye and Matt will explain how Canvas Dashboards fit into the broader Workfront reporting landscape, highlight their advantages over other report types, and show you how to build dashboards that people actually use. Specifically, you’ll learn:How Canvas Dashboards integrate with the Workfront reporting landscape and the unique capabilities they offer beyond standard reports and dashboards. W

 Update (September 2026): Detach and Rejoin each now have a second(improved) way to trigger them — Detach edge is available directly from the "+" menu, and rejoining can be done with Select from canvas instead of searching a list. See the updated sections below. What We're Hearing? Since rolling out the new canvas experience, one piece of feedback has come up more than any other: connecting and rearranging nodes feels harder than it used to. "I'm unable to select and move a branch." · "Once I disconnect the in-between node, I cannot connect it again." · "Joining nodes is harder in the new experience." The common thread across these comments is drag-and-drop. In the previous canvas, you could grab a node and physically drag it onto a connection point to rewire your journey. The new canvas — rebuilt for better performance and a cleaner layout — replaces that single drag gesture with two explicit actions: Detach and Join.They're not hidden, but they also don't look like what you're used t

With the announcement of the beta program to leverage an MCP server to your preferred AI tools, I was curious if any users have started to leverage this for their organizations yet? I am looking forward to trying the beta but need to receive signoff from our internal teams before we get the greenlight.     

Trade desk integration enhancements that connect paid to own.Adobe and The Trade Desk are helping brands bridge the gap between paid media and owned customer experiences by bringing advertising exposure data back into Real-Time CDP. By connecting paid media engagement signals with customer profiles, organizations can gain a more complete understanding of customer behavior and use those insights to improve audience segmentation, personalization, and future marketing efforts.Why It MattersToo often, paid media insights remain isolated within advertising platforms. By turning media exposure data into actionable first-party intelligence, brands can create richer customer profiles, improve customer experiences across owned channels, and make future campaigns more effective. This connected approach helps organizations move beyond campaign reporting to continuous audience learning and optimization.Learn MoreSee how Adobe and The Trade Desk are helping brands connect paid media performance wit

In your experience, what are the main reasons a Marketo lead scoring model fails to deliver expected results?

As a light/contributor/standard user (Reviewer and/or Approver), I want to be able to tag in a comment another user who is not in the workflow. This person should then be able to comment the proof but not make any decision

It would be very helpful to me as an admin to be able to prevent users from creating objects with the same name (IE multiple projects with the title “Project 1”). We have a lot of users who will duplicated projects or other objects and name them the same thing as their counterparts, which causes confusion among team members. We also have users who have accidentally duplicated objects without realizing it, then can’t determine which was the original.

As an online shopping enthusiast, I'm always looking for ways to save money, and Revounts Australia has been incredibly helpful. It offers best discount codes and deals as well as seasonal discounts for 2,000+ Australian and international brands. Whether you're shopping for everyday essentials or premium products, Revounts Australia makes it easier to find great deals and maximize your savings.  

Join us on Wednesday, August 5 from 12:00–3:00 PM EDT for the next Workfront Skill Exchange, featuring two parallel tracks packed with practical, real-world insight from Workfront customers, partners, and Adobe experts. This edition kicks off with an opening keynote from Angela Zhang (Adobe), followed by two tracks running side by side:  Workfront Learn Track (Emcee: Becky Barus, Qualcomm) WF101: Build for the Bot — Designing Workfront for Automation & AI (Kaylee Richard, Accenture)  WF102: Streamlining Planning with Workfront AI (Autumn Earle, Perficient)  WF103: Workfront Reporting Hidden Gems: 10 Tips That Will Save Time and Impress Leadership (Daniel Clarke, EMMsphere)  WF104: Mastering Workfront Admin Basics: Tips To Accelerate Your Onboarding (Jen Mancini, Aramark) Workfront Grow Track (Emcee: Jenna Martinez, Adobe) WF201: Tackling Workfront for User Adoption (Danielle Johnston, Adobe + Kellie Gardner, EMMsphere)  WF202: Your New AI Teammate: Mastering Workfront's Brand Revie

First a client expressed this desire, then a community member asked about something similar so I wanted to see how/if this works.  And it does!   Set up the template I wanted to create a project overview page, so I just started with the fields I wanted to display on the page. Not an actual Word template but simply a docx file with placeholders for data.    Open up MSWord (or an editor that writes docx files) and let's get started. Note the field names don't have to be related to the actual Workfront field - you set the template placeholder name and map it to the value you want to display (more on that later). For now, We Just write out what we want to see, and format it accordingly. Each placeholder is wrapped with double-curly braces. Example:   In some cases, we don't want to have extra space or a label on the page if we don't have a value. We can use a rudimentary IF tag. you determine the tag name, and the start gets a pound sign, the end gets a slash

Introduction Personalized content is one of Journey Optimizer's strengths — but it is also one of the hardest things to test before you publish. A single email can personalize the subject line, branch on loyalty points and marital status in the body, and use fallback copy when attributes are missing — all in the same template. Simulate content variations gave you a dedicated screen to preview multiple variants and send proofs without the Adobe Experience Platform test profile workflow. That was a real step forward. But it still left the hardest part on your plate: figuring out which test variants you need, and building each one by hand. The Content Simulation Skill takes that job off your plate entirely. It reads your content, analyzes every conditional branch and personalization field, works out the minimal set of variants needed to cover each branch at least once, and uses AI to fill in realistic profile, context, and target attribute values that satisfy those branches. You preview t

We sometimes see people trim()-ing Strings in Velocity before comparing them, like:#if( $lead.Region.trim().equals("Northeast") ) Without evidence that leads or apps have added extra whitespace around values, worrying about trim() here is likely overkill. If data is validated via picklists or reliable apps (e.g. you can easily trim Marketo form fields before submission[1]) you’re just forcing Velocity/Java to allocate memory for new Strings. Some people trim() before isEmpty(), in case a value consists of only spaces:#if( $lead.LastName.trim().isEmpty() ) The real flaw in both cases isn’t the concept of trimming, it’s that the types of whitespace trimmed by trim() are very limited and don’t represent the real-world whitespace that janks up databases. For example, U+00A0 NBSP isn’t covered by trim() since it only removes ASCII whitespace! In my experience, NBSP is a bigger wtf-how-did-that-get-in-there offender[2] than basic spacebar, so you want to catch it. So rather than trim(), use

Great turnout for our July roundtable — 27 attendees and 82 chapter members and counting (23 new members since our June 1 meeting!). We had folks register and join from across the country, plus one respondent all the way from London, spanning system admins, Fusion developers, marketing operations leaders, and end users.Our main topic was a live demo of the Workfront MCP Server and an overview of current Workfront AI capabilities, presented by David Kershaw of Techmera. David walked us through the three AI paradigms available in Workfront today, then showed the MCP Server in action against a live instance.AI Assistant. The in-Workfront chatbot. Best for summarizing what's on the current page, answering documentation and configuration questions, and (usefully) helping with calculated fields without the hallucinations you'd see from a generic LLM. AI Collaborator. Embeddable AI agents that plug into workflows. The Content Reviewer is generally available today — think of it as an AI teamma