Product Communities

Adobe DITAWORLD 2026Join us for Adobe DITAWORLD 2026Three days. One global stage for the future of technical content.Join us at Adobe DITAWORLD 2026 for three days of inspiration, ideas, and innovation — featuring a stellar lineup of speakers from the world's leading brands. From real customer success stories to the latest in AI-powered authoring and structured content, there's something here for every technical communicator, content strategist, and CCMS leader.Why you won't want to miss it:Hear how global enterprises are scaling content with Adobe Experience Manager Guides Explore the role of Generative AI in technical communication — from drafting to delivery Discover best practices in structured content, DITA, and omni-channel publishing Connect with peers, partners, and the Adobe Technical Communication teamRegister for freeCan't attend live? Register to receive the recording.

Learn how Direct Counts Configuration in Oak helps improve AEM query performance by reducing expensive repository traversal and optimizing query result counting for trusted service users.#AEM #AEMaaCS #ApacheOak #AEMPerformance #QueryOptimization #OSGi #AdobeExperienceManager  Read More :- https://www.aemcq5tutorials.com/tutorials/how-direct-counts-configuration-improves-aem-performance-and-reduces-node-validation-overhead/ 

 You’ve got a simple Velocity token {{my.credits remaining}} to calculate a subscriber’s current credits based on a couple of fields:#set( $creditsRemaining = $math.sub( $lead.monthlyAllocation, $lead.creditsUsed ) )${creditsRemaining} credits remaining this month So you figure you’ll pop that in the native Preheader area:Trying to use {{my.tokens}} in the Preheader Oops! That won’t work. {{my.tokens}} aren’t treated as tokens in the built-in Preheader. Technically you can paste ’em in there, they just get treated as literal curly braces with some words inside:You think it’s a {{my.token}}, but to Marketo it’s just text! A simple workaroundYou should know by now that a Marketo email is one big Velocity template. Even with no user-authored Velocity code, the system still uses Velocity to render emails. (No coincidence that email ${variable} syntax resembles Velocity ${reference} syntax!) To elegantly combine userland token code with internal system code, Marketo uses “multipass” Velocit

Why third not second? 

AEM Multi-tenant Website: Restrict cq:tags for User Groups   by SourcedCode.com (Brian Ka Sing Li) Overview Of most common multi-tenant websites, user groups are used to determine what AEM content authors can make changes to. The most popular requirement for a multi-tenant website is the ability to only edit tags for a specific brand. In this case, the way you can achieve this is by permissions. In this blog, we will ensure that all “WKND Members” will be able to create, read, update, and delete nodes under /content/cq:tags/wknd-shared, while these members will not be able to read any other tags listed under /content/cq:tags/*. Click here to learn more: https://sourcedcode.com/blog/aem/aem-multi-tenant-website-restrict-cqtags-for-user-groups  

Congratulations to ​@Wilson-Faure for your recognition as our AEM Champion of the Month for April! 🙌 🤩Wilson has one of the most loyal fan bases of any AEM expert I know. On top of being wicked smart with Adobe Experience Cloud products, his generosity with his time and kind personality make him a true force within the community. As a Champion, he always goes the extra mile by hosting a User Group meeting, sharing best practices with customers, and, dare I say, "stealing the show" at the karaoke bar?!Wilson, thank you for being you. We’re so happy to have you as an Adobe Champion! 👏  

While exploring Adobe Analytics MCP integrations, one question that came to mind was around method-level access control and governance.For teams directly connecting MCP with tools like Claude or ChatGPT:Is there currently any way to provide granular access to specific MCP methods? For example, can access be restricted so certain user groups can only use selected MCP tools/methods?This becomes more interesting from an enterprise perspective, especially if future MCP capabilities expand toward:creating reports modifying variables deleting configurations other administrative operationsCurious to know how others are currently thinking about:MCP guardrails monitoring MCP usage internal governance approval workflows controlled MCP integrationsI was also exploring an OAuth/API-based MCP approach where an internally hosted middleware layer could potentially help with additional monitoring, validations, logging, or custom guardrails before executing MCP methods.I also created a small document w

Is anyone else experiencing issues with updating Report Builder queries this morning? I keep get an error message saying that “Segments are currently available”

 Welcome to the VERY FIRST edition of the Workfront Wire!   This is your new monthly roundup built just for Workfront customers. Think of this as your one-stop-shop for the latest news, updates, events, and everything happening across the Workfront world. Each month, we’ll bring you what’s new, what’s next, and what you should know to get the most out of Workfront, without having to dig for it. Let’s get into it, and we’ll see you again next month for the next edition of the Wire.  Adobe Summit: 4 Key Workfront Announcements You Should Know  Last week at Adobe Summit, Workfront announced FOUR key updates focused on AI-driven workflow execution, enterprise operations, and more connected planning and review experiences:  Workflow Optimization Agent: AI that turns ideas and documents into structured plans, automates updates, speeds approvals, and delivers cross-system insights in Workfront.   AI Collaborators: Invokes an existing agent to execute work, leveraging instructions and context,

Hi Marketo Community!👋 I recently worked on implementing Marketo's Predictive Content and wanted to share my learnings, challenges, and use cases — hoping this helps others who are exploring the same! --- 🎯 WHAT I IMPLEMENTED:1. Recommendation Bar on Landing Pages2. Email ContentAI3. Rich Media Widget --- 📋 SETUP — KEY REQUIREMENTS:✅ RTP Script — Must be placed in <head> tag, after <meta> tags✅ Content Discovery — ON✅ URL Patterns — Map URLs to Categories✅ Domain Configuration — All domains must be added in Admin → Web Personalization✅ Content Pieces — Minimum 10 approved pieces recommended✅ Algorithm — Set to Clicks or Conversions --- 🔴 CHALLENGES I FACED & HOW I SOLVED THEM:1️⃣ Bar not showing after initial test → RTP won't re-fire for same visitor → Fix: Test in fresh browser session2️⃣ URL Domain mismatch → Sandbox domain (mktoweb.com) was not added → Fix: Added domain in Admin → Web Personalization → Domain Configuration3️⃣ viewedTypes was empty → Visitor had n

I’ve been running SEO and backlink experiments for DentPrime using different platforms within the Adobe ecosystem — including public project pages, shared assets, PDF links, portfolios, and other Adobe-hosted content.The issue is that none of the backlinks I created through Adobe applications appear in:SEMrush Google Search ConsoleEven after waiting for indexing and checking crawlability, these links still don’t show up.This raises several technical SEO questions:Are Adobe-generated backlinks automatically tagged as nofollow, ugc, or otherwise ignored? Does Adobe block crawler access through robots.txt or JavaScript rendering? Could these links exist in a way that Google can crawl but chooses not to report? Are SEO tools like SEMrush unable to detect links inside Adobe-hosted environments? Do Adobe apps create temporary, sandboxed, or non-indexable URLs? Has anyone successfully tracked backlinks from Adobe Express, Behance, Adobe Portfolio, Acrobat shared documents, or similar services

During a recent AEM implementation, we found an interesting scenario involving Content Fragments, Live Copies, DAM localization, and translation workflows.The setup was simple in theory: Content Fragments were created in a blueprint structure, and live copies were generated under localized DAM paths by language. Later, the blueprint Content Fragment was sent for translation into a target language, where the translated Content Fragment matched the same localized DAM structure used by the live copy.In our implementation, we observed that after the translation process, the translated Content Fragment appeared to no longer preserve the expected field inheritance between the blueprint and its live copy.This is an important behavior to be aware of when combining MSM/live copies with Content Fragment translation workflows. In these scenarios, teams should validate not only that the translated content has been generated correctly, but also that the expected inheritance between the blueprint an

Current ProblemCurrently, when downloading the database from the production environment to the pre-production environment, it only gives you the option to download the author database.This causes the content that was published to become corrupted since it only appears in Author but with the metadata in the CF as if it were published, which in turn prevents this content from being published.Request to AdobeThe optimal approach when downloading production databases is to allow downloading both author and publish, thus ensuring that the content in the source and destination environments remains identical.-------------------------------------Is this issue reproducible?: YesSteps to Reproduce: Current ProblemCurrently, when downloading the database from the production environment to the pre-production environment, it only gives you the option to download the author database.This causes the content that was published to become corrupted since it only appears in Author but with the metadata i

We would like to thank the 550 customers who registered for this event.The objective of this webinar was to provide a "sneak preview" and a look under the hood to discover what our engineering and product team are working on.Watch the recording of our May 12 webinar here:  Agenda:Major UI releases: Insights Home Page, Allowlist URLs, Flicker Manager, CDN Experimentation SDK Sum up of main Roadmap Features Experimentation Accelerator 🎉 Big Announcement: Adobe Target MCP server is generally available! Adobe is officially connecting your Adobe Target environment directly to your favorite AI assistants. More information here  Slides are attached to this post and can be downloaded as a PDF attachment 👇For customers who want to share their feedback, you are welcome to submit the following MCP Form multiple times as new ideas or feedback come up. Thank you for helping us shape the future of Target.The Q&A file for this event is available here.CC: ​​​​​​@VittoriaZocco for visibility 

Let’s get certified in August! 🚀I’ll be moderating this learning group and preparing for my next certification myself. As an Adobe Workfront Project Manager Certified Professional - AD0-E911, Adobe Workfront Core Developer Professional - AD0-E912, Adobe Workfront Core Developer Expert - AD0-E907, and Adobe Workfront Fusion Developer Professional - AD0-E902, I really believe certifications are one of the best ways to grow, challenge yourself, elevate your carrier, open up new opportunities, and connect with the community.Would you like to know which certification I’m aiming for next? Any guesses? Join this conversation and share your chosen certification goal so we can stay on course together, support each other, exchange tips, and celebrate progress along the way. Better together! 💎

Hi all—looking for some ideas/best practices here!I’m exploring how to automate task completions in Workfront based on proof decisions. From what I understand, this requires the document to live at the task level. If that’s the case, I’m curious how others are handling version control across multiple rounds of edits.Do you typically reuse the same task for each round, or create new tasks for each version? Trying to avoid things getting messy while still enabling automation.Example of what I’m trying to achieve:Design R1 – Designer uploads file to the task and marks complete Creative Review R1 – Proof is created and routed for approval Approved → completes Creative Review and moves to execution Changes Required → completes Creative Review and moves to Design R2 → Creative Review R2 This cycle would repeat until final approval.Would love to hear how others are handling this—especially if you’ve found a clean way to manage versions + automation together. Thanks in advance! 

Ready to take the next step in your Workfront journey? On June 18, 1–2 PM EDT, WUG-Philadelphia is hosting a live virtual panel — Building Your Workfront Career: Learn From the Experts — featuring career-savvy Workfront experts and community advocates who are passionate about helping their peers grow and thrive in the field.Open to all Workfront users and members across all Workfront User Group (WUG) chapters — admins, project managers, power users, and all practitioners — expect honest conversations about building long-term expertise, incorporating AI into your professional toolbox, positioning yourself for new opportunities, and the lessons that shaped their careers.This is community-powered learning at its best. Come ready with questions.👉 Save your spot today

Planning API: Field Search and Mapping LimitationsThere is no straightforward way to search or filter fields by name in the Planning API. Field IDs are not exposed in the Workfront UI, requiring additional API calls just to identify them. Mapping a field ID to its record type then requires chaining multiple searches, when this should ideally be handled in a single call. Planning API: Create/Read/UpdateFrom a Fusion developer perspective, it would be beneficial to support full programmatic create, read, update, and delete operations for record types and their fields. It would also be valuable to officially support patching individual record options. While we were able to accomplish this through an undocumented approach, having it formally available in the public API would significantly improve reliability and long‑term supportability.

Preserve Connected Record Picklist Values in AutomationsIn Workfront Planning, I’d love the ability to create a record and send it to another record type, either within the same workspace or across workspaces, while preserving picklist values from connected records.Right now, when using automations, those picklist values don’t carry over if they come from connected records. For teams using a central taxonomy model, this becomes a real challenge. We end up having to rely on Fusion to handle what feels like a core in-app use case, including working through complex JSON structures and API calls just to pass multi-select values. It works, but it adds a lot of unnecessary complexity for something that should be native. Automatically Associate Projects to Portfolios and ProgramsThere’s also a related gap when creating portfolios and programs through automations. While you can create them, there’s no way to automatically associate the projects generated from those automations back to the port

Ready to take your automation game to the True North of efficiency with ​@RowvillBh1 and I?Join us for an exciting, hands-on exploration of how to bridge the gap between Adobe Workfront and OpenAI using Fusion. Whether you’re based in the GTA, dialing in from across Canada, or joining us from south of the border, this session is designed for anyone ready to work smarter—not harder.In this deep dive, we’ll prove that you don’t need to be a developer to build world-class automations. Our guest speaker, Kaylee Richard, will showcase a live, practical scenario: transforming raw text from a Workfront request into actionable intelligence via OpenAI.What’s in it for you? See it in Action: A front-row seat to a live Fusion + OpenAI integration. Demystify AI: Learn how to make OpenAI accessible and straightforward within your existing Workfront environment. Connect & Grow: Network with a community of fellow enthusiasts and Certified experts who are leading the charge in work management.

Dark mode has become a normal part of the email experience, which means marketers need to think about more than just how an email looks in the default inbox view.The tricky part is that dark mode does not behave the same way across email clients. Some inboxes support custom dark mode styling, some apply their own automatic treatment, and some ignore custom settings altogether. That can make testing feel inconsistent unless you know what to expect.With the new Email Designer in Marketo Engage, you can now do more to prepare for dark mode. Marketo lets you:preview dark mode behavior define custom dark mode styling for supported clients adjust text, background, and button colors swap in alternate assets when needed test rendering across clients with Litmus integrationThat said, it’s important to set expectations correctly: Marketo Engage cannot control how every email client ultimately renders your message.Once the email reaches the inbox, the email client still has the final say. That’s

With network maintenance coming up on one Marketo pod, I was asked whether any features wouldn’t be affected during the maintenance period. First instinct: Nope. Everything uses the network, after all: outbound sends, SFDC sync, inbound LPs and forms, API calls and webhooks, etc. But one feature was unclear: unsubscribes driven by the List-Unsubscribe-Post SMTP header. Don’t think anyone looked into this before (like, anywhere). As you probably know, MAPs like Marketo comply with major email providers’ List-Unsubscribe requirement for optimal inboxing. They include a List-Unsubscribe-Post=One-Click header, plus a List-Unsubscribe header with a unique <https:> URL. Optionally, the old-school <mailto:> URL can also be included. Here’s an example:List-Unsubscribe-Post: List-Unsubscribe=One-ClickList-Unsubscribe: <https://click.example.com/u/NDEwLVhPUi02NzMAAAGhsh1UUD4gY6H_B7Njx0Jc6yQJgFRnh79OM35fojpoyZioqvs37SuRJd8HZ1U99J58MdA5RZg=?emailAddress=NDEwLVhPUi02NzMAAAGhsh1UT80Ef

If your AEM multifield saves correctly in Preview or Publish but loses data in Edit mode, it's almost never a caching issue. Here are the three root causes to check in order.1. Missing composite PropertyThis is the most common cause. Your multifield node needs `composite="{Boolean}true"` otherwise AEM writes flat properties instead of child nodes, which behaves inconsistently between edit and publish rendering.<items    sling:resourceType="granite/ui/components/coral/foundation/form/multifield"    composite="{Boolean}true">2. Sling Model Reading Wrong StructureWith `composite=true`, AEM stores items as child nodes not a String array. Your Sling Model needs `@ChildResource` not `@ValueMapValue`:// Use this for composite multifield@ChildResourceprivate List<Resource> items;3. WCM Mode Hiding Output in Edit ModeCheck your HTL for `wcmmode.disabled` conditions that might be hiding rendered output specifically in edit mode.Fastest Debug StepOpen CRXDE after saving the dialog. If

Adobe has become much more than just a creative software company. Over the past few years, Adobe Advertising and the broader Adobe Experience Cloud ecosystem have played a major role in helping businesses deliver personalized customer experiences across multiple platforms. ()One thing I find particularly interesting is how Adobe combines analytics, audience targeting, AI-driven insights, and cross-channel campaign management into a single ecosystem. This gives marketers the ability to better understand customer behavior and create more relevant advertisements instead of relying on generic campaigns.At the same time, I think there are still challenges for newcomers trying to learn Adobe Advertising products because the ecosystem is very large and enterprise-focused. Many users in online communities mention that there is a steep learning curve, especially for products connected to AEM and Experience Cloud. ()I’d love to hear from others in the community:What has your experience been with

A question that comes up frequently when working with shared Field Groups: does marking a field as Primary Identity in one schema affect other schemas using the same Field Group? And how do you handle required fields that don't apply to your specific dataset?These are two separate concerns that get conflated because they both live in the schema layer.Primary Identity is Schema-LocalMarking a field as Primary Identity is a local decision scoped entirely to that schema. It has zero upstream impact on the Field Group definition or any other schema using it.Identity designation and field group constraints are completely separate layers in AEP's Schema Registry:- Field Group = shared blueprint with structural rules (required, data type)- Schema = local implementation including identity role assignmentsField A stays required everywhere because that constraint is defined at the Field Group level. Field B being Primary Identity in Schema X doesn't change anything for other schemas.Handling Req