Product Communities

Please add the ability to export email using the new email designer from the main view. Currently this can only be done by going back into edit mode. This is useful to have after the email had been published.

With our consolidated B2C, B2B & B2P instance/sandbox currently in production which includes Salesforce and Marketo account data via the native Marketo connector as well as batch ETL ingestion from our datalake. The result of this is duplicate account profiles with multiple/different primary & external source keys. Currently we have two options to manually correct for these duplicate account profiles: Option 1: Fix the Mapping Change the mapping on the Marketo side so that the “primary key” field (account key) for accounts brought in from Marketo uses the same format as the Salesforce/account data brought in via other sources. Example: If Salesforce/S3 uses 001xxxx...@salescloud.redhat as the account key, configure Marketo’s field mapping to use the same convention instead of the out-of-the-box 001xxxx...@<OrgId>.salesforce. This aligns the account keys from Marketo and Salesforce/S3, allowing AEP merge policies to recognize them as the same account and unite/stitc

DescriptionEnable OpenFeature providers (https://openfeature.dev/docs/reference/concepts/provider/) for the API/SDKs/languages you currently support. This would speed up the installation of Adobe Target server side by working on multiple platforms.Why is this feature important to youWe have built an Experimentation tool wrapper around the OpenFeature specification. We have multiple feature flagging tools across the enterprise and through leveraging the OpenFeature specification, we can bring the same context and tracking to all the tools. Also, we primary use Adobe Target for digital marketing experimentation, primary on the front-end. By supporting OpenFeature, other channels would be able to subscribe to Test & Control with minimal effort. Currently Target is not in the convo to support feature flagging and experimentation for other channels like IVR, Chat and App.How would you like the feature to workSee the OpenFeature specs: https://openfeature.dev/specification/Current Behavi

In Planning, connected fields have Record Filtering Rules. When you are in a table and you click to select from the connected records in that field, you are only shown the ones that meet the criteria for those rules. Great feature!  However, it does not apply to a Request Form built for that table. The filtering does not apply. AI Coworker confirmed this and said the best workaround was to manually filter your data set. That’s not good enough.  I badly want to be able to apply filtering rules to connected fields/records in Planning. It seems like an oversight that we can’t do this now. 

Pretty self-explanatory. I have a batch smart campaign that I need to run every hour on a daily basis with no end date. Since "hour" is not a frequency option, I had to create 24 recurring batch smart campaigns to achieve this result. I'd much prefer to manage this through on smart campaign, as opposed to 24!

Description - Would love to have the option to pin and unpin a certain update to the top of the updates thread. This would allow for easy visibility on the most up to date items, etc. Would also love the option to filter updates by date, time, etc. to quickly search through and locate a certain update.  Why is this feature important to you - This would increase productivity within the Workfront platform tremendously and would avoid confusion and clearer communication with cross-functional partners looking for information via updates. How would you like the feature to work - A button that says "Pin" next to "Reply" and " Like" - Once pinned there would be an option to "Unpin" For the filter, some sort of filtering option at the top right of updates then you can click and customize certain date, time, latest comments, etc)  Current Behaviour - Updates are ordered in the time in they are posted, and all replies and updates are not able to be customized at thi

Problem StatementCurrently, Workfront hour reports and views provide visibility into who updated an hour entry, but there is no native field to easily identify the user who originally created/entered the hour entry and the timestamp.Why This MattersAudit trails require knowing the exact origin and timestamp of an hour entry. Without a "Entered By" and a "Timestamp" field auditing and troubleshooting time tracking discrepancies become unnecessarily difficult.Example: We have integrations that enter hours from Salesforce to Workfront, which a user can later update. So, it is important to have both the information (entered/updated). I can use a Journal Entry but that is a waste of time and becomes difficult to explain to process owners.Proposed SolutionAdd the following native fields to the Hour Report: "Entered By": Displays the user who initially submitted/generated the hour entry record (independent of who last updated it). "Date Created / Timestamp" (Journal Date): Displays the exac

As a marketing operations manager, I want to de-dupe my database when a duplicate record is identified via CRM sync by merging the identified record with duplicates in the database, and leveraging rules prompted in a callable agent to determine.Winner/loser criteria based on create date, last modified date, last marketing touch in the activity log, etc.  Rules for competing scores and/or lifecycle stages Concatenation rules (combining notes) for merged records.  

When using the 'updates' function or tab, it would be useful for our teams to be able to utilize this space in a fashion similar to email. IE- to add colored text to responses, in order to differentiate between users. Also, it would be helpful to allow certain updates to be 'pinned' to the top of the page so they don't get lost. OR to categorize them as "bulletins or job notes" of some kind to set them apart from the back and forth threads.

We get a lot of the busy projects with multiple comments and updates posted daily. Some system comments or Summaries or updates are super important and we want to be able to PIN them and Highlight or have a way to view Important notes only. 

In the current email builder, when you want to send a sample, it keeps a dropdown list of Previous Recipients that you’ve sent samples to recently.In the new email builder, it doesn’t seem to have that functionality. It’s just an empty field to enter in the email address with no dropdown.It would be great if it could remember previous email addresses that we’ve sent proofs to recently, and let us pick from that (in addition to typing in a new address if needed).Thank you!

When entering tags (the free text keywords, not tags from a fixed list), e.g. “engineer, female, tech, big data” in the meta data schema, there ae only options available where you enter one tag, hit Enter, type the next tag, hit Enter etc. This process is time-consuming, especially as many assets are supposed to have lots of tags. While AI tags can help with search, we can’t control them and you also cannot copy them to the main tag field to work with them. That means it is still necessary to enter tags manually. It would be way better to be able to copy/paste or type a list of comma-separated tags, e.g. “engineer, female, tech, big data” into ONE metadata field, and then hit Enter, whereas the system recognizes the tags as individual entities separated by comma and turns them into individual items automatically. 

When an image is uploaded in the comment section of an issue or request, it should be automatically replicated and remain visible after the request is converted into a project. This will ensure that all relevant visual information and supporting documentation from the issue-level comments are retained and accessible at the project level.

The standard repository ACL model is not sufficient for the business authorization requirements. Access decisions needed to consider both user attributes and asset or content metadata rather than relying solely on static permissions (https://lnkd.in/gnxwYfmT).With complex, dynamic group permissions and a large volume of assets or content, relying solely on static permissions or Role Based Access Control (RBAC) becomes difficult to scale and maintain.Using Adobe Experience Manager (AEM) and Apache Jackrabbit Oak, we designed a hybrid RBAC + Attribute Based Access Control (ABAC) authorization model that evaluated:User context: Roles, organization, region, and contractual entitlements.Asset context: Domain, business rules, exclusivity, and folder visibility.The core principle was simple:Access = User Eligibility + Asset Eligibility + Business RulesBy integrating a custom PermissionProvider into Oaks security architecture, we established a centralized enforcement point for evaluating these

Just like we can delegate project/task/issue approvals, and with 22.3 can delegate task/issue assignments, PLEASE have the ability to delegate proof approvals! There are other ideas for this with 'Not Planned' labeled, hoping power in numbers can help sway this bc this is something WF really needs. Hoping it is part of near-future proof enhancements.

Current state, only AND condition available Idea:Currently, when building automations in Workfront Planning, trigger conditions across multiple fields only support AND logic. This means all conditions must be met before the automation runs.It would be extremely valuable to have the ability to use OR conditions as well.Example: Trigger an automation when:Status = Approved OR Priority = High OR Type = Urgent RequestToday, the only option is to use AND logic, which significantly limits flexibility and often requires creating additional automations or workarounds to achieve the desired outcome.Business Value:Reduces the need for duplicate automations Simplifies Planning configurations Supports more real-world business use cases Makes automations easier to maintain and scaleAs organizations start adopting more complex Planning setups, OR logic would make automation capabilities much more powerful while keeping configurations simple and intuitive.Use Case: A marketing operations team wants t

There should be a way to archive records that have a certain status, like Completed or Canceled, for example. Once an organization moves beyond test use cases, the records of a real enterprise start to add up. To my knowledge, Planning comes without a way to move/remove ‘archived’ records from record types, especially connectable record types. My solution for now is to just put ‘z_archive’ on the front of each records name. I could probably build an automation for this but I’d rather this be a feature of Planning.

We'd love to use Workfront Planning for asset tracking and management, but currently there's no way to store files or images directly within a record, aside from the thumbnail.Adding an attachment/document field that supports multiple files and images, similar to Airtable's attachment field, would make Planning much more useful for asset management. This would allow teams to keep asset details and supporting files together in one place instead of relying on external links.Interestingly, Workfront AI Assistant already suggests that this functionality exists, making it feel like a natural addition to the platform.

With the way Workfront Planning is expanding, do you think there is a need for a separate topic specially for Workfront Planning within Workfront product community? 

One of the interesting aspects of integrating Adobe Workfront with AEM as a Cloud Service using the native connector is designing the right metadata model and synchronization strategy.For the implementation, I used Workfront Custom Forms to capture business-specific metadata that is not available through the standard Workfront fields.Workfront allows custom forms to be attached to different objects, including Projects and Documents. This provides a flexible way to maintain metadata at different levels of the content hierarchy.Project Custom Form → AEM Folder MetadataThe first custom form is attached to the Workfront Project.The Project represents the business context and folder structure for the content. The custom form captures metadata that needs to be associated with the corresponding folder in AEM.For example: Brand Business Unit Region Market Campaign Language Content Category Folder DescriptionThe metadata captured at the Project level can then be mapped to the appropriate AEM fo

With Internal Lookup fields replacing Typeahead fields in Workfront, I would like to suggest an improvement to how dropdown options are displayed within reports.Previously, Typeahead fields allowed users to easily view the full name or description of each dropdown option without requiring excessively wide report columns.Currently, Internal Lookup fields display dropdown options within a limited width, making longer names or descriptions difficult to read. Increasing the column width to accommodate this information takes up valuable space and negatively impacts the overall report layout.Proposed Enhancement:Allow Internal Lookup field dropdown menus to automatically expand beyond the report column width, similar to how Workfront's native fields (such as User fields) currently function.This would allow users to view the complete names or descriptions of dropdown options without having to widen report columns.Benefit:This enhancement would improve readability, usability, and reporting eff

DescriptionCurrently, Adobe Analytics 1.4 API provides several powerful endpoints that allow administrators to manage report suite configurations programmatically. These include the ability to:Fetch and update eVars, props, events, and classifications.Retrieve configured processing rules for a given report suite.Adobe has announced that the 1.4 API will be deprecated in favor of the 2.0 API next year. However, these configuration-level features are not yet available in the 2.0 API. Once 1.4 is removed, these critical capabilities will be lost.For many enterprise-scale implementations, this functionality is not just convenient — it is essential. Proposed ideaExtend Adobe Analytics 2.0 API to include endpoints for:Variable Management: Create, update, and fetch eVars, props, events, and classifications at the report suite level.Processing Rules: Fetch and (if possible) update processing rules for a given report suite.Cross-Suite Comparison: Provide efficient ways to compare variable

Description:The Upcoming Campaigns panel in Marketo Sales Insights (shown in the Salesforce contact view) lists scheduled email campaigns for the next 30 days. It also says these are "not limited to qualified leads."Problem:Our Marketo instance supports multiple businesses and brands. Sales reps see campaigns from other businesses in the panel and assume the contact is about to receive those emails. This causes confusion and unnecessary escalations. Reps think the contact is being mis-messaged, when in fact the contact doesn't qualify for those campaigns.Requested enhancement:Add an admin setting or user toggle, such as "Show only campaigns this lead qualifies for", that filters Upcoming Campaigns to campaigns whose smart list and filters the lead actually meets. If full qualification evaluation isn't feasible, allow admins to filter the panel by workspace, program channel, or tag, so each business sees only its own campaigns.

Convert the programs page into a widget that can be added to WF Home. This would allow convenience of accessing that page without leaving Home and allow project managers to quickly search for programs they need to access

Our team has a need to make the filter selection in the My Approvals widget sticky. We have multiple team members that submit work to others for approval and receive work from others for approval. Having to reset the filter each time to show only “My Approvals” instead of “All” wastes a few clicks of time and makes it more difficult for us to work through time-sensitive approvals.