Build better products with our product team
Request for Feature Enhancement (RFE) Summary: Versions must be created in AEM upon using Manage Publication. Use-case: Manage Publication is commonly used feature within AEM and versions not being created with Manage Publication can cause issues while restoring content. Current/Experienced Behavior: Versions are not created in AEM upon Manage Publication and versioning works only if Quick Publish option is used. Improved/Expected Behavior: Versions must be created in AEM upon using Manage Publication. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as Cloud Service latest release Customer-name/Organization name: Abbott Screenshot (if applicable): Code package (if applicable):
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 Open Summary. Both options have more clicks and actions than Users need to take, and can be simplified.
LOVE the new UI Beta. The ideal next step for the UX is to enable Marketo users to be able to copy/clone flow steps and smart list filters from within the same smart campaign or smart list. This will help save us significant time in building smart lists and workflows.
The native sync currently hinges around the core objects of Lead/Contact/Account/Opportunity. I do come across use cases more and more frequently though where the Account-Contact Relationship in SFDC manages more complex relationships between a contact and multiple accounts. Use cases range from external consultants / influencers on more than one company, several sites in different countries within a customer being logged as separate accounts and a stakeholder playing a role in more than one, etc. The set-up in SFDC prevents the contact being entered more than once to indicate their role in every account effectively, so is really great in avoiding unnecessary duplicates. It would be great if the data model in Marketo would also incorporate this added complexity.
One of the challenges we're trying to address is the amount of manual effort required for users to complete and submit multiple intake forms in Workfront at a time. To help streamline this process, we are exploring a solution that would leverage a custom web service and Workfront APIs to help automate the completion and submission of custom forms. The goal is to enable users to submit multiple intake requests programmatically while still adhering to the business rules and user experience defined within the Workfront custom forms. As part of an enhancement feature, would it be possible to allow API access to the display logic (e.g., cascading rules/conditional visibility) and/or other methods to retrieve the display logic within the custom intake forms?
The new green pop-ups at the bottom of the screen when task status is modified, such as if you click work on it the pop-up says “You’ve started working on this. The status is now in progress.” or when you remove your assignment it says “You’ve stopped working on this, the status is now new” are persistent and must be manually dismissed by users even after navigating to other objects. While having the pop-up is helpful for confirmation, we need the ability to have those auto-dismiss after a few seconds or at least have it disappear when moving to a different object in Workfront.We have users who are moving quickly through the system who now feel disrupted by having to click another item to dismiss after already clicking to change the task. They often move on quickly until these pile up at the bottom of their screen, then have to dismiss each individually. Which a large volume of work as is, any extra clicks are cumbersome to users. Thank you so much!
Marketo Engage users who have significant investment in email assets build in the legacy email designer need a “push button” way to convert old email assets to the format used by the new email designer. Adoption of the New Email Builder is being hampered because New Email Designer assets are fundamentally different asset types, and switching to the new email editor for organizations that have significant investments in nurture programs are akin to doing a full Marketing Automation migration, which is not to be desired.
Description - Before the migration to Adobe console, we were able to have two email addresses associated to each Workfront account. One email (FedID) is what our users used to login through SSO and the other (Username) is where their email notifications from Workfront went. With console this is now no longer possible and support has been unable to suggest a workaround. Would love to see this functionality restored! Why is this feature important to you - Some of our users need their notifications routed to a shared inbox for coverage purposes/so it is easy to jump in and help each other with workloads. How would you like the feature to work - I would like to be able to have a field on the user profile again where I can input an email to send Workfront notifications to. Current Behavior - Functionality no longer exists.
Currently in Realtime CDP, using tracked event data that is also evaluated in Adobe Analytics, it is not possible to segment profiles based on the number of visits (as metric “Visits” in Adobe Analytics) that they have since there is no “visit-id” that is exposed on the UI or even the possibility to select audiences based on “count unique” [element]. The number of visits in a given timeframe is an important KPI for our department and we would like to select profiles in different intervals of it.Thanks!
Description - Would love to have the option to attach a file to a request in Planning.Why is this feature important to you - We thought we had a solution to our public facing request problem through Workfront Planning's ability to create public request links. However, the inability to attach files makes it a non-viable option for us.How would you like the feature to work - Just like in Workfront Core, we would like to have the option to attach files to requests.Current Behaviour - Currently there is no file attach option in Workfront Planning.
SummaryOur team uses Claude connected to the Workfront MCP server to answer resourcing questions in natural language. Planned Hours are fully and reliably queryable today. Remaining Available Hours — the metric the Resource Planner itself calculates (schedule capacity minus time off minus existing commitments) — is not exposed through any MCP tool, and cannot be reliably reconstructed from what is exposed. We're requesting this data be made queryable so a team's full capacity picture (Planned + Available) can be surfaced through natural-language requests, not only through the Resource Planner UI.What Works TodayPlanned Hours are cleanly queryable via the insights_find_workfront_data tool, using fields such as assignment.assignment_workRequired and task-level planned hours, grouped or filtered by user, project, or date range. This lets Claude answer questions like "how many planned hours does each person on this team have this month" accurately and immediately.The GapThe Resource Planner's own Available Hours (AVL) value — schedule capacity minus time off minus hours already budgeted across all of a user's projects — is not exposed as a field through insights_search_fields or any other MCP tool we've found. The raw inputs needed to approximate it are also incomplete: user.user_workHoursPerDay and schedule.schedule_hasNonWorkDays are queryable, but time off is only exposed as a boolean flag (user.user_hasReservedTimes), not as actual date ranges or hours. There is no queryable list of a user's specific time-off periods or schedule exceptions. As a result, Claude cannot reliably reconstruct "remaining availability" even by combining multiple queries — any approximation would overstate availability for anyone with time off on the books, since those dates aren't visible to any tool.What We're RequestingPreferred: expose the Resource Planner's calculated Available Hours (AVL) value itself as a queryable field — per user, role, or project, scoped by date range — mirroring what already displays in the Resource Planner UI. Minimum viable alternative: expose the underlying time-off / schedule exception data (specific dates and hours per user) as queryable fields, so Available Hours can be reliably approximated by combining it with the Planned Hours data that is already accessible.Why This MattersCapacity planning conversations need both halves of the picture — what's already committed, and what's actually left. Today, getting the Available Hours half requires manually opening the Resource Planner and checking user-by-user, project-by-project, which doesn't scale and can't be surfaced through natural-language tools like Claude. Closing this gap would let our team ask capacity questions the same way we already ask planned-hours questions — directly, without a manual UI detour.
Both the Section Headers and Table Of Contents have been good additions for making reports easier to read and navigate through - though have got a couple of thoughts on how they might be able to be improved further. 1) Add the full set of right-click functionality to Section Headers - At present, the only way that the Section Header visual can be interacted with is changing the text; the right-click menu that exists with other visualisation types isn’t there. However, I think it would be good to change this for two main reasons. ‘Edit description’ - This could be used to enable the adding of a short description or subtitle, between the main title and the line underneath the visualisation. ‘Get visualisation link’ - It would be good to be able to link directly to a Section Header. As a user who often adds an Introduction or Contents section to tell users what they can find in a report, it’s nice to add links in, but currently you have to link to any other visual that’s close to the Section Header instead. Although doing this ‘Contents’ part does overlap with the Table Of Contents feature, I find a) many more ‘casual’ users are still unaware it exists, and b) this written text is far easier to quickly understand due to the next point… This right-click menu exists on other visualisation types, but not Section Header. Distinguish Section Headers in the Table Of Contents - In the below image of the Table Of Contents on the left, you can’t instantly see which lines are Section Headers. As a result it’s a lot more tricky to find what you’re looking for and understand what’s in the panel. Some possible changes (as per the right) that could improve this may be adding bold text to Section Headers, indenting any text that isn’t a Section Header, or even adding in icons to distinguish the visualisation type next to each line. At the moment I often find myself adding colons to the text of these visuals only, or adding extra Section Headers with ‘-’ as the title to create a space, as something of a workaround to get them to be somewhat visually identifiable. The left image shows how the current Table Of Contents displays, while the right image shows how this could look using bold text for Section Headers or indented text for other visuals. With these changes though, hopefully it would make dashboards easier to read and navigate.
In the new unified approvals, when an approval template is created, there is a field for “workdays until due date”. We need this number to exclude weekends, or at least have the ability to associate with a schedule that excludes weekends, so that approval due dates do not fall on weekends without manually adjusting the due date with the calendar feature.
Marketoのメールアセット一覧とメールコンテンツ取得に関して、現在の検証結果として下記だが、v2仕様は公開情報となっていない。また、メールアセット一覧取得に関して、v1で旧エディタでの作成分と新エディタ作成分（ただしレスポンス内容の不足あり）という状況だが、この状態が正式仕様となるのかも公開情報となっていない。 APIを利用したシステム構築を行ううえで正式な仕様情報がなく、設計が困難なため早期に仕様の確定および公式情報として公開を頂きたい。 《検証結果》■メールアセット一覧取得 v1：旧エディタに加え、新エディタで作成したアセットも取得可能。ただし新エディタ分は、一部Subjectが含まれないなどレスポンス内容に不足が見受けられます。 （https://developer.adobe.com/marketo-apis/api/asset#operation/getEmailUsingGET） v2：新エディタで作成したアセットのみ取得可能。 （https://developer.adobe.com/marketo-apis/api/asset#operation/filterContentUsingGET_email）■メールコンテンツ取得 v1：旧エディタ作成メールのみ取得可能 （https://developer.adobe.com/marketo-apis/api/asset#operation/getEmailFullContentUsingGET） v2：新エディタ作成メールのみ取得可能 （https://developer.adobe.com/marketo-apis/api/asset#operation/getContentUsingGET_email）
It would be great if the Date field could be customized, such as being able to block or highlight specific dates when the calendar pops up.
Link is https://experience.adobe.com/#/experiencemanagerBut it returns a 404.
Currently when you unassign a user from a task/issue, it automatically fills in the assignee with that user's job role. My company has never used this feature and it just creates extra work and confusion to either remove that job role or to see it in the assignments. It would be great if this is something we could disable in the setup area.
Currently, Salesforce sync errors can only be reviewed manually through Admin > Salesforce > Sync Errors in Marketo. While the UI provides valuable information about job-level and record-level synchronization failures and allows exporting data as a CSV file, there is no supported REST or SOAP API endpoint that exposes this information programmatically.For organizations that rely on centralized reporting, monitoring, and BI platforms, this limitation makes it difficult to automate the collection and analysis of SFDC sync issues.Provide a supported API endpoint that allows customers to retrieve Salesforce synchronization errors programmatically, including:Sync error timestamp Error type/category Error message/details Lead ID and/or SFDC record ID Sync job information Resolution status (if applicable) Ability to filter by date range Pagination support for large datasets
Request for Feature Enhancement (RFE) Summary: <Issue> An issue occurred where the publishing operation failed on the holding company's corporate website. <Cause> The cause was that a file uploaded to Assets did not comply with the naming conventions. However, the current version of AEM Assets allows files that do not adhere to naming conventions to be uploaded without displaying any error messages or warnings. <Request for Improvement> We would like a feature that checks file naming conventions during upload, displays an error or warning for non-compliant files, and controls the upload process. We believe this will help prevent issues upon publication and reduce the operational workload. Use-case: A specification that checks naming conventions during file upload, displays an error or warning for non-compliant files, and controls the upload process. Current/Experienced Behavior: With the current version of AEM Assets, it is possible to upload files with names that do not comply with naming conventions, and no error messages or warnings are displayed when doing so. Improved/Expected Behavior: We would like a feature that checks file naming conventions during upload, displays an error or warning for non-compliant files, and allows for control over the upload process. We believe this will help prevent issues upon publication and reduce the operational burden. Environment Details (AEM version/service pack, any other specifics if applicable): asahi-kasei-corporation-program-prod Customer-name/Organization name: Asahi Kasei Corporation Screenshot (if applicable): Code package (if applicable):
Description - After a thorough implementation, we decided to use the Request Queues built directly in the projects. The functionality is great. We have a project template set up with Queue Topics, Groups, Forms etc. The issue is that when creating requests directly in a project there is no Autosave or Drafting functionality that we know of. Our users are becoming increasingly agitated by having complex requests easily deleted at the unfortunate click out of the request window or accidental refresh of the page. Why is this feature SO VERY important to you - Our current solution is to submit requests without auto-routing to a traffic team so the work can be saved. Leading to needing to save as you go, something that is antiquated in this day and age, especially knowing that autosave exists in many other places in Workfront, including the Global Request Queues area. How would you like the feature to work - simply autosave as you go with a Drafts section built into the Request area of the Project. Or a new section called Request Drafts. Draft autosaves until the Submit Request button is clicked. Current Behaviour - User begins a request, fills out info and has to Submit the Request in order to save it and continue working on the request, and they must click save as they progress. If users haven't submitted the request yet or haven't recently saved, it is very common for users to accidentally click out of the window, closing the request and clearing all the info. Leading them to have to painstakingly recreate the request they could have spent many hours on. Please prioritize this, WF.
Adobe recently announced Sub-Hit analysis for Adobe Analytics. However, this feature will be limited to the Products variable, according to the documentation.Since many customers are using List Vars and List Props, support for Sub-Hit analysis for these dimension types is needed. Please extend this feature to those dimension types.
A new feature that would be great to have is the ability to test marketing channel rules as you’re creating/saving them. Similar to what we have for classifications, where you can put in a test string and it will show how that string would be classified. It would be great to have this with marketing channels. How it should work:There should be an option to run a test where you can manually put in a URL, referrer, and other components (based on what components you’ve used to set up your rules). Either have it show up with all of the fields you’ve used and the option to populate them/leave them blank, or have dropdowns where you can select which fields you want to enter info for.Then have it run what you’ve entered against all of your rules and tell you which marketing channel it would get classified into. Why it’s important:Right now when making marketing channel processing rules, there isn’t currently a way to test them. It can be hard to mentally go through all of the rules and figure out how a hit would get classified, especially if you have a lot of rules. The value of being able to test specific types of hits can let users know if their rules are working correctly or not. Especially for Adobe Analytics, where retroactive changes are not possible, this could save data from getting misclassified after rules are set up.
Add function to API to add nonWorkDay (NONWKD) without needing to nest beneath an object with all other nonWorkDays. Right now to add a nonWorkDay to a schedule all existing nonWorkDays must be collected first as an array. Then the array must be added to with new dates to an edit call on the parent object. The longer the schedule is used the larger this array becomes the harder it is to confirm no errors or missed dates.
Users need to be able to filter and organize their timesheet page. The current filter option is very limited. We'd like users to have the ability to filter, view and group on the timesheet page, similar to functionality available in other sections, where standard choices are provided and the user can add, customize and share as needed.
There should be a setting in the new launch to be able to track s.products without going to the custom code to build the product string.Kind of like how the old GTM had a checkbox to enable e-commerce tracking and it would just read the dataLayer Enhanced Ecommerce (UA) Developer Guide | Google Tag Manager for Web Tracking | Google Developers
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
