Product Communities

As the Workfront Fourth Quarter Release is scheduled for next week (October 16th), this webinar highlights the new enhancements, including the New Requesting Experience, AI Reviewer, Workload Balancer updates, as well Planning and Fusion features, and so much more!  If you weren't able to attend - no worries! The links to the slide deck, recording, and transcripts are listed below. Be sure to review all of the release notes on Experience League, as not all features were covered in the webinar.   A HUGE thank you to the Product Management teams for joining and sharing additional details around these new enhancements! If you have any follow-up questions, be sure to post those as a reply to this discussion. (We've also included the discussions from the Q&A pod in the comments below.) Slide Deck PDF  Webinar Recording  Webinar Transcripts  Looking for what’s next for Workfront? Don't forget to register for Workfront 2nd Half 2025 Roadmap Webinar to

Introduction When it comes to integrating your existing Adobe Analytics Classifications to Customer Journey Analytics (CJA), you have two options to consider. The first option is to use the Adobe Analytics Classifications Data source connection to automate the migration of your classifications to CJA. By utilizing the source connector, you can connect your existing classifications from Adobe Analytics and import them automatically into Adobe Experience Platform (AEP), and ultimately into CJA. This option can save you time and effort, particularly if you have a significant number of classifications to migrate. Please note that you need to be an Adobe Analytics Product Admin to administer the Analytics Source Connector in AEP. The second option is to recreate the Adobe Analytics classifications in CJA. This involves going through each classification and recreating them within the CJA platform as a new dedicated lookup dataset. While this option may require more time and effort, it all

If you are in a large company where different departments separately purchased products that each group manages separately, and you all enable SSO for your products, how has your Workfront migration gone or how is it going? Our migration to SSO has been fraught - to put it mildly -  as the architecture of the Admin console places some serious limitations on our ability to manage our sensitive Workfront information independently --- far from the prying eyes of unrelated departments with whom we're suddenly forced to share the console.  I've already created a related submission under the Ideas forum, so I won't re-hash everything, but if you are experiencing similar pains at your company, I ask that you cast a "Like" for my idea in order for it to gain traction and help others who still have to complete their migration. And to summarize, here are our pain points with the ongoing Adobe Admin Console migration:We've learned the following from the Adobe reps who have been wor

Hi Folks,   Today, Adobe Workfront shared this announcement upon login:     We first learned of the upcoming change a couple of weeks ago (then, cited less precisely as "Sept 2025"), so have been working furiously to upgrade all of our solutions, and were delighted to make a similar announcement today in response:     As Workront's oldest partner, we had vestigial references going back to API v2.0 all the way up to current (v20.0), and as we tackled this upgrade, had to decide whether to:   use the "Latest" API by NOT specifying a version and instead "roll with it" whenever the official Latest version changes (so less maintenance, but more risk), or use the specific "v20.0" latest version to "lock in" that functionality, recognizing that someday the code will need to then be upgraded (deferred maintenance) We decided to go with the latter, and have teed up our tech stack to make future such transitions less onerous, but I am curious what others ar

Adobe Journey Optimizer Community Lens Newsletter  Your quarterly roundup of insights, events, and member highlights Subscribe to the AJO Community Lens Newsletter   Hello AJO Community!  Welcome to your quarterly roundup – a curated snapshot of what’s happening across the AJO Community. From standout member contributions and the latest product releases (including features you requested and the product team delivered) to trending questions, ideas, and on-going learning opportunities, this is your go-to guide to stay connected and inspired.  This newsletter will be published every quarter, bringing you the latest highlights and insights in one place.  We’d love for you to explore the threads, celebrate your peers, and share your own solutions and ideas. Your voice shapes the future of AJO. So, jump in, comment below, and keep the conversations going!    Member Spotlight  Thank you, SatheeskannaK, for everything you do to make this Community

We’ve got another Top 3 video with your “On-Demand Workfront CSM”! This time we’re talking about a commonly overlooked (but helpful) object in Workfront – Companies!    Check out the video below.      Looking at adding Companies into your mix? Here are some tips!  First things first – documentation and tutorials!  Create and edit companies  Create companies – short tutorial video  Create and modify a group’s companies  Test in the Sandbox first! See what your vision can look like without impacting your live, production environment.  The Adobe Workfront Preview Sandbox Environment  Build a Report or a View that lists the impacted objects you want to move. If it’s Users, then a User View/Report. If it’s Projects, then a Project View/Report. If possible, use Groupings to make it easier to organize the work.  Create a basic view  Bulk edit or inline edit to assign your new companies.  Edit Projects in bu

Hi,We have a requirement, where we upload a image on the publisher, and the same should reflect in author also.When raised a Adobe support ticket for the same, this is the reply we got."I would like to inform you that unfortunately reverse replication (from Publish to Author) is not supported out‑of‑the‑box in AEM as a Cloud Service. -This is a fundamental architectural change: unlike on‑premise and Managed Services deployments, AEM Cloud Service does not support the traditional reverse replication agents. The cloud model expects content to be authored at the Author instance and then pushed (forward replication) to the Publishers.Although Sling Content Distribution (SCD) is available for content transfer, the Sync Distribution configuration meant to mimic reverse replication is not feasible in AEM as a Cloud Service. -Because the traditional reverse replication mechanism is absent."Is there any workaround to achieve this functionality?

Hosted in partnership with Enterprise Architecture, this webinar shared best practices, tips, tricks, and secrets to improve the oversight and operations of your Workfront instance. With a focus on governance (think naming conventions), execution (processes & automations) and adoption (layout templates, views, filters, and groupings), this session was jam packed with helpful hints to ensure you are set up for success with Workfront!  If you weren't able to attend live, no worries. Links to the slide deck, recording, and additional resources are listed below:  Slide Deck PDF  Workshop Recording  Summary & Resources from the chat: Governance requires establishing a committee with system administrators, group admins, and other leaders to oversee instance management across multiple organizational units. Download the Governance Blueprint here. Governance committee size can be based on the number of groups, departments, and the complexity of workflows rather

Each month, teams across Adobe Workfront host FREE webinars, interactive workshops, customer panels, and open Q&A sessions on various topics for System Administrators.    If you want to learn best practices, ask questions and collectively brainstorm solutions, or connect with other system administrators to build your network, sign up for one or all of the following events:    October 2 at 10:00 a.m. PT – Wake Up with Workfront: Scaling with Advanced Features & Fusion- Part 2  October 3 at 9:00 a.m. PT – Admin Chat for Marketing & Creative  October 8 at 11:00 a.m. PT – Workfront Pro-tips for Governance, Execution, and Adoption  October 9 at 8:00 a.m. PT – Adobe Workfront Fourth Quarter Release Webinar   October 14 at 8:00 a.m. PT – Admin 101: Getting Started with Workfront  October 16 at 10:00 a.m. PT – Inside Mayo Clinic: How Workfront Fusion Helps the Humans  October 20 at 6:00

We're running AEM 6.5.19. We would prefer not to use workflow approval inbox/email chains and instead rely solely on content permissions. However, some of our editors are seemingly subject to certain approval workflows when they attempt to replicate, edit, move, or delete content. For example, I might have full permissions on a node (except for edit acl), yet if I attempt to replicate this page, an approval workflow winds up in the admin user's inbox. We've been deleting these workflows but are worried user's requests wind up in a workflow black hole of sorts. The user may be expecting someone to act on the request.We would prefer for a user who does not have the correct permission on a node to be unable to take the action. We do not want to trigger a workflow that winds up in the admin user's inbox. We would prefer that the action just not be possible for a user without the corresponding permission. In a different case, some of our users seem not to

Hello,We're on a AEMaaCS and have a requirement to create a custom workflow to publish Content Fragments with below use cases. 1.When an author makes a change, they can send the fragment for Review and Activate to a reviewerThen approver reviews the content and accepts to activate - this then publishes the fragment 2.When an author wants to deactivate a fragments Then approver receives the content and de activation request and accepts to deactivate - this then unpublishes and deactivates the fragment 3.When an author makes a change, they can send the fragment for Review and Activate for a specific timeThen approver reviews the content and accepts to activate at the requested time - this then publishes the fragment at the specific time 4.When an author wants to deactivate a fragment at a specific timeThen approver receives the content and de activation request and accepts to deactivate - this then unpublishes and deactivates th

when I worked on a AEM setup usng managed services, Cloudfront inserts extra response header that will tell me if the page is getting served from CDN or from origin.Because it managed service, I can login to the dispatcher and I can manually check if the page is already cache in the dispatcher or needs to be fetched from the publisher.How can I do both of these on AEMaaCS?

Hi team, I've encountered an error while using Adaptive form fragment (with core component). When I open the Form Fragment Container component, it shows that Resource dumped by HtmlRenderer Resource path: /apps/core/fd/components/form/container/v2/container/cq:dialog/content/items/tabs/items/dataModel/items/formmodel/items/selectformmodel/items/optionConnectormodel/granite:rendercondition Resource metadata: {sling.modificationTime=-1, sling.characterEncoding=null, sling.parameterMap={}, sling.contentType=null, sling.creationTime=-1, sling.contentLength=-1, sling.resolutionPath=/apps/core/fd/components/form/container/v2/container/cq:dialog/content/items/tabs/items/dataModel/items/formmodel/items/selectformmodel/items/optionConnectormodel/granite:rendercondition} Resource type: /libs/fd/af/connectors/rendercondition/marketo Resource super type: - Forms version: 1.1.64Service Pack: 6.5.21

Rename/Move an AEM Asset programmatically and Update References  by Aanchal Sikka   Overview Renaming or moving assets in AEM while keeping all references intact is a common challenge for developers. Basic APIs like AssetManager.moveAsset() can rename or relocate assets but do not update references across your site, often leading to broken links. This blog breaks down two approaches: Using AssetManager.moveAsset() for simple moves without reference updates. Alternate way with CopyMoveCommandBuilder, which renames assets and automatically updates all references, ensuring content consistency. The blog includes sample servlet code demonstrating how to implement the CopyMoveCommandBuilder approach.  Link to blog: https://techrevel.blog/2025/10/07/rename-move-an-aem-asset-programmatically-and-update-references/    Q&A Please use this thread to ask questions relating to this article

Use this thread to ask any questions related to the Implement Adobe Experience Cloud in mobile apps  tutorial on Experience League. Experts are monitoring this thread to ensure your questions are answered.

Your feedback matters! Share how you're using AI today and what support you need.   This short survey helps us design the right training to support your work. This survey is for marketing practitioners who are using or plan to use AI tools (Adobe or non-Adobe).   Complete the survey here

Your feedback matters! Share how you're using AI today and what support you need.   This short survey helps us design the right training to support your work. This survey is for marketing practitioners who are using or plan to use AI tools (Adobe or non-Adobe).   Complete the survey here

Since the launch of Blueprints in 2021, the solutions represented in the catalog have primarily all been focused on Project Templates. We are excited about recent developments in the Blueprints product capabilities that now allow the creation of Custom Forms, Reports and Dashboards, Projects and Queues, and a variety of other configuration objects.    While Blueprints product features will continue to follow the normal quarterly release patterns that we rely on for other product features and capabilities, new Blueprints solutions will be added to the catalog on an on-going basis as new content is ready. This means that the normal communication channels for releases are not the best mechanism for us to highlight and announce new Blueprints solutions.    The purpose of this blog post is to provide Adobe Workfront customers visibility into the catalog contents that are being released. As we release new content to the Preview environment, we will make an announcement as

  Overview of the List Import Process   There are 4 key steps when importing a list into Marketo Engage: Prep your list/scrub the data outside of Marketo  Prep work within Marketo Import the list  Validate and QA   Step 1: Prep List & Scrub Data   Move your data into an evergreen list import Excel template for all imports that should be created by your admin. Admins: Include required and optional fields as columns, matching Marketo field names for easy mapping with... Mandatory fields (e.g., Email) should be clearly highlighted - lists cannot be imported without these values!  Exclude unsubscribe-related fields; ensure field updates are blocked on Trusted/Untrusted List Imports. Each column = one field; align with your data dictionary. Use dropdowns/picklists within the excel for consistency and ease of use to the end user (e.g., Boolean fields with “TRUE”/“FALSE” only Delete records without email addresses. Remove duplicates on your l

      In the world of marketing automation, data is everything. But not all data is created equal—especially when it comes to list imports in Marketo Engage. If you've ever wondered what the difference is between a trusted and untrusted list import, you're not alone. Understanding this distinction is key to maintaining data integrity, compliance, and campaign performance.   What Are List Imports in Marketo? List imports are one of the most common ways marketers bring external data into Marketo—whether it's leads from a tradeshow, webinar registrations, or from external systems. But how that data is treated once it enters your instance depends on whether the import is marked as trusted or untrusted.   Trusted List Imports A trusted list import is one where the data source is considered reliable and compliant with your organization’s data policies. These imports typically come from: First-party sources Known partners or integrations Internal teams with verified

Applications frequently face scenarios where the single standard datastream setup isn't sufficient to meet specific use case requirements. Whether it's refining data consumption, integrating custom processing logic within mobile apps, or managing the mobile app code release cycle, adjustments are often necessary. This discussion explores methods for modifying and overriding default datastream configurations by leveraging Data Collection (Tags), eliminating reliance on the mobile app code push cycle. As a result, updates to the datastream override can be implemented rapidly without going through the mobile app release process. The key benefit is the ability to configure datastream overrides at the Data Collection (Tags) level, rather than within the mobile app itself.  Additional Use Cases: There are various scenarios where your app may require adjustments to its datastream or dataset override configuration. In this blog, I will highlight a few key use cases to demonstrate when and

10 Unique Marketo Token Use Cases You Might Not Be Using Tokens in Marketo are one of those features that seem simple on the surface, but the more you work with them, the more powerful they become. Most teams use them for basic personalization (like adding a first name in an email), but that barely scratches the surface. With a little creativity, tokens can save hours of work, reduce errors, and make your campaigns more scalable. Here are 10 unique and practical token use cases you might not be using yet. At their core, Smart Campaigns are rule-based workflows that allow marketers to automate actions such as sending emails, updating data fields, scoring leads, or triggering notifications.Think of them as the "if this, then that" engine of Marketo. Here are some common use cases: 1. Dynamic CTA Text in EmailsTired of rewriting the same button across multiple emails? Store your CTA text as a program token. Update it once and it changes everywhere. It’s also an easy way to test variations

Have you ever used Marketo Engage Program Member Custom Fields? How about syncing Program Member Custom Fields (PMCFs) to Salesforce Campaign Member Fields (CMFs)? Yeah, that’s a mouthful. In this blog post, we’ll cover the specifics of how PMCFs sync to CMFs, some key considerations, and expected behavior so you can take advantage of this new powerful feature.    Pre-Requisites  Enable the Salesforce Campaign Sync in Marketo Admin  Create Program Member Custom Fields in Marketo  Create Campaign Member Custom Fields in Salesforce – NOTE! These fields would live on the Campaign Member Object, not the Campaign Object. Think of it this way: the Campaign Member Object contains data pertaining to the Campaign Member Record (i.e. the Lead or Contact), whereas the Campaign Object has fields that relate to the Campaign itself.     Setting Up the Sync  With the above complete, you can now map Marketo Program Member Custom Fields to Salesforce Campa

Are you responsible for training new Workfront users? Creating enablement materials can be time-consuming, but we’ve lightened the load by curating project templates to assist you with training new users in Workfront.We’ve created three project templates by persona:  Project Managers Workers / Assignees  Contributors / Requestors / ReviewersEach template provides links to foundational Workfront training for new users to utilize Workfront in accordance with their role. Feel free to add or remove links to help train users on functionality specific to your organization. When a user completes their assigned training project, they should have a solid understanding of Workfront and be ready to execute their work.Learn how to install a blueprint How to use the templates: Copy the template so you have the original to reference, if needed.Set your template task view to "Training Template," which is included in the blueprint.Customize to fit your organization s

Welcome to the latest Expert Insights!  I’m Cynthia Boon, your “On-Demand” Workfront CSM and for this episode we have Workfront Text Mode Jedi, Katherine Lanning @katherinela, Workfront Solutions Engineer from IQVIA!  During this episode, Katherine shares her story, her passion for all things Text Mode Reporting, and demos how she built her “Sanity Management” Dashboard!  Check out the video here!  Text Mode can be challenging, but the rewards are amazing.  Just remember Katherine’s advice!  “If you can see it, you can change it.”  Flip into text mode on standard reports to see how columns are built.  Learn by tinkering.  Add fields, switch to text mode, and experiment to understand what drives the data.  Use plain language.  Title columns as questions or clear statements so non-admins can interpret them easily.  Add descriptions.  Customize hover text in text mode to explain data and guide users.  Make