Product Communities

In this post, I walk through a generic Proof of Concept (POC) for extending the AEM Assets user interface using Adobe App Builder. The goal is to demonstrate how you can build a custom Assets View UI Extension and integrate it with AEM Assets to provide a more tailored user experience.🔹 What you'll learn:• How AEM Assets UI Extensions work• Setting up a simple App Builder project• Creating a custom Assets View experience• Connecting the extension with AEM Assets• Understanding the overall extension architecture• Key considerations for building a production-ready solutionThis POC can serve as a starting point for organizations looking to build custom asset views, specialized DAM workflows, or tailored authoring experiences on top of AEM Assets.📖 Read the complete tutorial: https://www.aemcq5tutorials.com/tutorials/building-simple-aem-assets-view-ui-extension-adobe-app-builder-generic-poc/ 

Another Mega-WUG is almost here!If you haven't had time to watch the August 2026 Workfront Skill Exchange recordings yet, you're not alone — and September 16th is here to help.Think of it as the trailer, not the movie. Five of our Skill Exchange speakers will each give a "sneak peek" recap of their session, then sit down for rapid-fire Q&A with a Workfront practitioner from the community. It's your fast-track intro to the caliber of content across the whole event — and a preview of what's waiting for you in all 8 recordings.One hour, five previews, eight sessions worth exploring. Hope to see you there!📅 Sep 16 | 12:00–1:00 PM EDT | Virtual🔗 RSVP https://usergroups.adobe.com/events/details/adobe-user-groups-workfront-michigan-chapter-presents-mega-wug-workfront-skill-exchange-highlights-reel/

As implementer or Workfront admin, have might have come across an ask that that you just can't realize in core Workfront. For example, you can't display the Documents of all child projects at the Program level (you see the files attached to the specific program). Sometimes WF Reporting just doesn't offer what you'd need.  Here's a way to leverage Fusion to create an external page that can be accessed in a WF custom dashboard. With this approach you could implement the "impossible" asks. [Apologies in advance: This will feel like web tech from ~2000]  This is not something I invented - and it was the examples I saw from my colleagues at IBM iX that got me thinking. There were a handful of cases where I wanted a tool that pulled data from the Workfront API and presented it to me visually instead of just the raw API output. After tinkering with this I ended up with an approach I keep coming back to. It emulates what an app server might do (receive a request, look up some da

🚀 New AEM Test Series is now live!Practice with structured quizzes across key AEM topics like AEM as a Cloud Service, Cloud Manager, Dispatcher, Assets, Forms, Security, Performance, and more.Whether you are preparing for interviews, upskilling for real-world projects, or strengthening your AEM fundamentals, this test series is designed to help you learn faster and test your knowledge effectively.Start practicing here: https://www.aemcq5tutorials.com/test-series/✅ Topic-based quizzes✅ Beginner to advanced levels✅ Practical AEM learning✅ Great for interview prep and skill refreshhashtag#AEM hashtag#AdobeExperienceManager hashtag#AEMDeveloper hashtag#AEMCloudService hashtag#AEMQuiz hashtag#AEMInterview hashtag#AdobeExperienceManagerDeveloper hashtag#CMS hashtag#Java hashtag#DigitalExperience hashtag#ContentManagement hashtag#Learning hashtag#CareerGrowth hashtag#TechSkills hashtag#InterviewPreparation hashtag#AEMCommunity hashtag#Adobe hashtag#WebDevelopment hashtag#QA hashtag#Developer

It would be great to have more flexibility when designing custom forms, particularly around field layout and presentation.Suggested enhancements:Greater control over field height and width, rather than being limited to the current sizing options. More freedom to position fields exactly where required on the form. Additional formatting options such as: Custom colours for sections, headings, or fields Text formatting (bold, italics, font size options) Highlighting important information or mandatory areas Visual styling to make forms more engaging and easier to navigate These improvements would help administrators create more intuitive, user-friendly forms, improve the overall user experience.Business benefit: More visually appealing and structured forms can improve adoption, reduce user error, and make complex request forms easier to complete. 

This article makes the case for setting up a lightweight Workfront release management process, and shows how it's easier to implement than most people assume.Key points:The problem: Untested changes going live in Workfront can catch teams off guard and erode trust. The fix doesn't need to be heavy: Release management just means having a repeatable way to plan, test, approve, and communicate changes — not a bureaucratic approval chain. Two sandboxes, two jobs: SB02 (Sandbox 2) is where technical building and testing happens; SB01 (Sandbox 1) is where real users validate changes before go-live. Keep sandboxes fresh: Regular refreshes (SB02 more often, SB01 before major testing cycles) keep testing environments realistic — stale sandboxes give false confidence. Environment Promotion moves things along: Workfront's built-in packaging tool lets you move configuration changes (forms, fields, templates) between environments reliably, instead of manually rebuilding them each time — build → com

Please build API where you can store the user activity from 12 months to var node and so that based on that we can able to identify the how many active users are there from past 12 months. 

Thank you to Jyothitha Chandran (Product Manager) and Mayank Gaur (Senior Product Manager), for a great session exploring how AEM Dynamic Media and Adobe Journey Optimizer work together to deliver personalized experiences at scale. We appreciate all the insights, demos, and roadmap updates! Session SummaryMayank and Jyothitha demonstrated how teams can create and manage Dynamic Media templates and bring them into AJO to build personalized, reusable content for omnichannel campaigns. The team showcased how AJO can combine profile and external data for real-time personalization, dynamically tailoring elements such as product names, prices, images, and regional content. Mayank shared a look at the product roadmap, including deeper Dynamic Media integration within the AJO email designer, expanded open-time personalization, and AI-assisted workflows, while gathering customer feedback to help shape future capabilities. Session MaterialsSlide Deck Webinar Recording Consolidated Q&A Additi

 Feature Request: Timed & Milestone-Based Comment Access 💡 OverviewCreative reviews happen in stages. Early on, teams need private space to draft assets and give feedback without outside eyes. Later, final reviewers need to see past comments to understand why decisions were made—without gaining permanent access.This feature adds a smart visibility gate that automatically reveals past comments to later reviewers only when their turn begins, and locks access once their review is done.👥 Who Is Involved? Audience 1 (Core Team / Project Leads): Runs the project, manages review stages, and makes final calls. Audience 2 (Creative Partners / Vendors): Works privately with Audience 1 during initial creation. Audience 3 (Final Reviewers / Business Stakeholders): Steps in at the end to review the work and provide sign-off. ⚙️ How It Works Keep Early Work Private Audience 1 and Audience 2 work together in a private space. Audience 3 cannot see drafts or internal comments during th

From Audiences to Insight: Identifying Your Most Valuable Customers If you're running Adobe Real-Time CDP, you've already done the hard part. Your data sources are connected. Identities are stitched. Profiles are unified, and your team can build an audience and activate it across channels in minutes.So, here's the question worth sitting with: open your audience builder right now. Can you segment on how much each customer is actually worth to your business, ranked, current, and ready to activate today?Most Real-Time CDP teams can't. And the reason isn't a gap in Real-Time CDP. It's that the attribute you'd need to segment on doesn't exist on the profile yet.The limits you've probably already hitReal-Time CDP gives you computed attributes, a genuinely useful way to aggregate event-level data up to the profile. If you need a count of purchases in the last 30 days, that's exactly the right tool.But computed attributes work within the boundaries of the Profile Store. They operate on a pre-d

Text in a Rich Text custom field in a custom form isn’t displaying when this field is added to a board card. The ask is that custom Rich Text fields are supported for direct display on Workfront Board cards.

How AI Put a Reliability Promise on Every AJO ServiceGiving nearly every service behind Adobe Journey Optimizer a measurable reliability commitment — at a speed and scale that manual work could never have reached. In our last post, From Gut Feeling to Grade Point, we walked through the Service Scorecard — the automated grade every AJO service earns across four dimensions of quality. One of those dimensions is Reliability Against Our Commitments: how much reliability margin a service is holding against the target it's promised to meet.That dimension is only as strong as the reliability targets behind it. Today, with an SLO defined for 90%+ of AJO services, we have clear, standardized visibility into exactly what each service is expected to deliver — and how much margin it's holding against that target.This is the story of how AI got us there — giving nearly every service behind AJO a precise, measurable reliability commitment, at a speed and scale that would have been out of reach any o

Enhance the Dark mode so that the entire Workfront background can be made dark instead of limiting it to the navigation menu.

Just been going through some of the announcements from Adobe Summit 2026 around AEM as a Cloud Service and wanted to get a real-world pulse from folks actually building on it day to day.A few things I’ve been thinking about after working on enterprise AEM Cloud implementations:The Edge Delivery Services push is getting louder but I’m curious how many teams are actually migrating existing Sites implementations versus greenfield only. In practice the replatforming effort is significant and I haven’t seen a clean story for brownfield migrations yet.Universal Editor is getting a lot of attention but author adoption in enterprise environments has been mixed in my experience. Has anyone actually rolled it out to a large non-technical authoring team and how did that go?On the pipeline and CI/CD side, Cloud Manager has improved but environment promotion still feels like it needs work especially around content variable management across stages.Would love to hear from others are these things you

You’re invited to The Skill Exchange 2026, a free virtual event running August 5-6 and August 11-13. Looking to sharpen your Adobe skills, discover new ways to work smarter with AI, and learn directly from Adobe experts and customers? This is the event for you! Skill Exchange 2026 registration is officially open! 🚀  Join us for:✨ Expert-led sessions across 7 Adobe solutions  🤖 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 AEM Sessions are on Wednesday, August 12th!Whether you're just getting started or looking to level up your expertise, there's something for everyone. 🎟️ Save your spot today: [Register Now]  

Hi Marketo Community!I was a speaker at the Skill Exchange sharing about how you can prepare your Marketo Engage for AI (and how you can use AI to help you in this work). The link is here, but I’m also curious to learn how the community is using the new AI features and what you have implemented so far!

Currently AEMaaCS does NOT offer an efficient way to create a set of pages from different hierarchies of the website which should be sent to translation in multiple target languages.If you have one page you can use the SITES console to create a translation project, also here the option is to include their subpages. But if you need to create a package of pages which are stored in different hierarchies of the website structure, you need to go to Projects > Translation Project and you need to add those pages to EACH target language that you have. Let’s say you have 30 languages of your website - so you need to do this adding of pages 30 times!This manual task is NOT efficient at all and takes a lot of time!AEMaaCS as an enterprise CMS should offer a smart way so that you have to do the selection just one time and then just select the target languages that apply. Current situation is more than disappointing!

💡This solution uses the same tech as toggling images in Email Editor. I’ll omit some details you can read about over there. You might be surprised that WebFonts (via CSS @font-face) are supported in Apple Mail for desktop and mobile. Those apps comprise at least 20% of email opens; using some methodologies, as much as 60%. Even the low end, IMO, doesn’t match the common take that “few” end users will see your fancy fonts! Yes, you must fallback forcefully for Outlook. But it’s totally doable: this month (August 2026) I’ve seen WebFont-enabled emails from CDW, Dolby, London Review of Books, Malwarebytes, Mural, Salesforce, Verizon, and Zapier. As with toggling images, you can easily add a WebFonts toggle to Email Editor 2.0:A little Email 2.0 template code high up in <head>:<meta class="mktoBoolean" id="enableImages" mktoname="Enable WebFonts" true_value="http:" false_value="'none'" default="true" /> <meta http-equiv="Content-Security-Policy" content="font-src ${enabl

We all know Outlook blocks images by default, yet there’s no native way to preview without images in the Marketo UI. Turns out it’s super-easy to add a toggle to Email Editor 2.0:Only takes a little Email 2.0 template code high up in <head>:<meta class="mktoBoolean" id="enableImages" mktoname="Enable Images" true_value="http:" false_value="'none'" default="true" /> <meta http-equiv="Content-Security-Policy" content="img-src ${enableImages}"> And this <style> right after:<style>:root:has(meta[http-equiv="Content-Security-Policy"][content="img-src 'none'"]) { --images-disabled: "images";}:root:has(meta[http-equiv="Content-Security-Policy"][content="font-src 'none'"]) { --webfonts-disabled: "webfonts";}:root:has(meta[http-equiv="Content-Security-Policy"][content="img-src 'none'"]),:root:has(meta[http-equiv="Content-Security-Policy"][content="font-src 'none'"]) { body:before { font: small-caption; display: inline-block; padding: 6px; content:

Hello Adobe Workfront Support Team,We would like to submit a product enhancement request for Adobe Workfront Request Queues.Current situationWe have one Request Queue project containing multiple Queue Topics. Occasionally, users need to copy an existing issue from one Queue Topic to another Queue Topic within the same project.The copied issue must retain its existing information, including: Issue name and description Custom forms and custom-field values Documents Assignments Updates, where permitted Primary Contact Relevant permissions The standard Copy to functionality allows users to select the same or another project, but it does not provide an option to select a destination Queue Topic. The Copy and Submit as New process requires users to open the copied request form and manually select the destination Queue Topic before submitting it.Requested enhancementPlease consider adding a native option that allows users to: Select an existing issue. Click Copy to. Keep the s

Has anyone upgraded to the Planning API v2?What is your most valuable result/use case after doing so? We’re working to estimate LOE against budget and trying to decide if there’s bang for the buck there. Was it a huge lift to upgrade/implement? I’m told we have little to nothing on v1, so hoping this means it will be fast and somewhat easy.

Hello,I am trying to work on allowing the Adobe Creative Cloud on our network and am looking for the minimum required list just to authenticate via the Creative Cloud and use Premiere Pro. Our network & security teams are very strict on what gets whitelisted and will question if there are 10+ domains added to a request.What is the bare minimum to just allow us to log into creative cloud and use Premiere Pro?Thank you

Are you tired of chasing your marketing ops team for every audience, or new to the team and want to get hands-on fast? Adobe CX Enterprise Coworker lets you build audiences yourself without being the data expert.Here are two easy ways to get started.1. Directly ask Coworker to build it.Give it the targeting criteria you already have in mind, a high-level campaign goal, or both and Coworker will strategize with you.Try simple natural-language prompts like:"Build an audience of recent cart abandoners." "Build an audience of homeowners in California." "Build an audience for a new member welcome campaign." "Build an audience for Black Friday Sales, recommend a target strategy first." "Build an audience for a member upgrade nudge campaign, targeting silver loyalty members close to upgrade with recent engagement."Coworker acts as your thinking partner: surfacing reusable audiences, relevant attributes and events, and explaining its recommendations so you can make informed choices. Ask follow

Would love to have a button in WF that takes me to a text mode cheat code library vs. searching community or using AI. Any Workfront user could submit a cheat code and it gets added to a database behind the scenes. This would help all users be able to have quick access to effective text mode that works. This would speed up being able to implement solutions for reporting for businesses.

I’ve been experimenting with Playwright for testing the AEM authoring experience — not just the rendered pages.A few interesting issues surfaced that component/rendering tests simply wouldn’t catch:Dialog validation that didn’t match the field description A field that silently accepted an invalid configuration Rich-text input losing characters Test cleanup failing because of browser/API session differences Shared/included dialog fields that were easy to miss in component-based test coverageThese bugs lived in the authoring interaction — the clicks, typing, dialog state and sequence of actions an author actually performs.I wrote up the lessons learned, including some of the Playwright patterns that worked (and the ones that didn't 😄):👉 Testing the Click, Not the RenderCurious how others are approaching automated testing of the AEM authoring experience. Are you testing the editor UI today, or mainly the rendered output?