Build better products with our product team
Description - The widgets home page is too complex for some users who only want to see just a full list of their work. The Priorities view provides a great option for this with an enhance user interface that has just what these users need. Though a report can display most of the same info as the Priorities view, the report does not look as pleasing.Why is this feature important to you - Many users still prefer the old home interface and this is a great compromise between the old and the new.How would you like the feature to work - Go into a layout template and set Priorities as the home landing page.Current Behaviour - Priorities is not an option to to select for the home landing page
Description - Please refer adobe support ticket of Dell company "ase Number 00438765 - In proofing, where to check when a user is created and by whom ?"Why is this feature important to you - To know who and when created a account.How would you like the feature to work - Show created by and date for Guest and Member accounts in Proofing Current Behaviour - Currently Proofing showing, Created Date only for User accounts. It is not showing for Guest and Member accounts. And Proofing not showing Created By or Triggered By for any account.
DescriptionWe are requesting a feature in Workfront that enables users to filter updates on issues, tasks, and especially projects, programs, and portfolios based on specific fields that were changed. This would help users quickly locate historical changes tied to a particular field (including custom fields), rather than having to sift through a long list of general updates. Why is this feature important to youProject and portfolio managers need efficient access to field-level change history to ensure accurate tracking, decision-making, and reporting. This is particularly important when reviewing how project details have evolved over time, supporting transparency and accountability. Additionally, being able to present this data to executives is critical in portfolio-level oversight and governance. How would you like the feature to workWe envision a filterable audit log within the Updates or Journal area that allows users to select a specific field (e.g., “Planned Completion Date” or a custom text field) and view a history of only those changes, including timestamp, user, and old/new values. Ideally, this functionality would also be exportable or easily reportable to support executive summaries or audit reviews. Current BehaviourCurrently, Workfront provides a general log of updates with timestamps, but there is no way to filter changes by specific fields/dates/etc. Some limited history can be pulled through custom reports, but this does not apply to all field types (e.g., custom text fields), and the reporting itself is constrained and difficult to create/use for this purpose. As a result, reviewing historical data for key fields is almost impossible, time-consuming and often incomplete.
We (Marketing) works with some teams in IT and other vendors that use Jira. The WF Plugin for Jira is extremely valuable in letting the PM assign work to these times in a specific Jira board and have visibility over it alongside other tasks/projects we have in WF (as sometimes our projects involve both teams). We have a Jira Cloud instance and another vendor that uses Jira Data Center. We wanted to start using this for our Data Center instance and apparently this was discontinued. According to WF, "we lost the integration with Data-Center in January of 2022. This happened because Jira updated their requirements for Data-Center Plug-ins. At this time we have not made any changes to align with the new Data-Center Requirements and the integration has been moved to a 'Not-Supported' state. They have requested that the idea be submitted to the innovation lab so that they can better gauge how many of our customers are looking for this integration." Please bring back the ability to use this WF Plugin for Jira to Data Center Jira instances.
Description - PLEASE add functionality for us to connect an issue with a project that has already been set up. Why is this feature important to you - We Forecast a good portion of our work so that we have placeholders during our heavy seasons. When we receive issues for these requests from a queue, it won't allow us to connect the two while bringing over the custom form and attachments. How would you like the feature to work - When converting the issue to a Project, an option should be "convert to established project" and we should be able to add to the project we already have set up but also bring over the custom form and attachments from the Issue. Current Behaviour - this doesn't exist. As a workaround, I'm having to convert the issue to a new project, clearing out the timeline that populates, copy Forecasted timeline over to the new project then I have to delete the project I had in Forecasted. Very cumbersome workaround.
We would need different levels of permission for access in the offers tab. For example, one access to create the offers but not be able to approve them, and another access that can both create and approve.We want to prevent those who are supposed to only build the offers from activating it incorrectly without supervision/approval.currently the same employee who builds the offer is able to approve it.
Here is a list of uses cases where I would have loved a product-scoped container in the segment builder:https://analyticsdemystified.com/adobe-analytics/product-segmentation-gotchas/Here is a description of how it might work:https://analyticsdemystified.com/adobe-analytics/a-product-container-for-christmas/Here are other related ideas:https://forums.adobe.com/ideas/8709https://forums.adobe.com/ideas/10245
When building landing pages in Marketo, we often focus on elements like the form, content, and design — but one crucial aspect is often overlooked: Meta Open Graph (OG) tags.These tags play a silent yet powerful role in how your landing page is displayed when shared on platforms like LinkedIn, Facebook, or Slack. What Are Open Graph Tags? Open Graph (OG) tags are small snippets of metadata that go into the <head> section of your page's HTML. They control how your content appears when shared on social media — ensuring your link previews show the right title, description, image, and URL. Without OG Tags, Your Shared Links Might:An outdated or irrelevant imageA vague or incorrect titleMissing or unoptimized descriptionNo branding or keyword contextSince Marketo doesn’t automatically inject OG tags into landing pages, so you’ll need to manually add them to your Landing Page Template or through a Custom HTML block in the page.Here is the basic example:<head><meta property="og:title" content="Title of Page" /><meta property="og:description" content="Add Description about Page" /><meta property="og:image" content="Main Image URL of Page" /><meta property="og:url" content="Page URL" /><meta property="og:type" content="website" /></head>Adding these tags helps ensure your landing pages are visually aligned with your brand and perform better when shared on social platforms. Hope this helps you make your Marketo pages more social-friendly and on-brand!
Today, when you install Marketo Sales Insight with Salesforce, the managed package automatically creates the required fields for syncing over a variety of items, such as those around Last Interesting Moment. In particular, Last Interesting Moment Description is a textarea field--but it is limited to 255 characters. Marketo does not enforce any sort of field length limit beyond its maximum on the backend. As a result, it is exceedingly common to create Interesting Moment Descriptions that exceed 255 characters, especially if something like trigger URL is being replicated on an IM like "Clicked Important Email". My current understanding is that these fields are NOT directly referenced in the Visualforce components of MSI and thus there would be minimal impact to accepting larger items. For example, when looking at a MSI Visualforce component on a client instance, I can see a description of 285 characters is successfully displayed. As a result, I would like the ability to optionally increase the textarea field character limit within reason to accommodate these behaviors without encountering sync issues. You should be able to modify this in a straightforward way in the package schema by changing the field's manageableState to SubscriberControlled.
Description - When adding permissions for user you can currently give them Analytics Workspace access and the ability to create Segments and/or Metrics, however this same permission allows them to share reports, segment and metrics with anyone else. The suggestion is to split off the share permission as a separate permission(s). Why is this feature important to you - We're more than happy for users to create their own reports, and to create segments and metrics in order to complete whatever reporting or analysis they need. However these may not be documented properly or defined correctly so we want to impose governance and check reports/segments/metrics are defined correctly and are not copies of existing company wide segments/metrics, etc before anything is shared. Adding this feature allows us to reduce confusion around which reports/segments/metrics to use, guarantee they are correct, and give end-users greater faith then the data they see is correct. How would you like the feature to work - Remove the ability to share from the current existing user permissions for Workspace, Segments and Metrics and either create a new single permission for Sharing anything, or three new permissions for sharing reports, segments and metrics. Current Behaviour - Adding Analytics workspace access allows users to share any reports they create there, and adding the ability to create Segments or Create Metrics also allows them to share segments/metrics
An email notification should be sent when a user reacts to a comment. Our team often uses reactions—especially to indicate agreement or a "yes" response—but the original commenter is often unaware of the reaction.
Would love to use Engagement Map even for email program smart lists as it's the easiest way to see the smart list criteria fully and ability to copy and paste the smart list criteria is valuable. Currently engagement map is only available for smart campaigns.
Description - We have the ability to generate a shareable link of a workload balancer filter, which is great! But it'd be great if we could add additional filters on the top of the shareable link.Why is this feature important to you - sometimes we want to generate an organization shareable view, but they'd would still want to filter it down.How would you like the feature to work - If I generate a link for the Design group, bu still want to filter it down by specific job roles (e.g.: senior designer, creative director or ux designer), I could be able to add a filter on the top of that.Current Behaviour - on a shareable link, I can't add any additional filter.
Description - We would like to have functionality to move tasks to the backlog from the project level while in the project schedule. Why is this feature important to you - We work in agile mostly and many tasks have to be removed from iteration back to the backlog. How would you like the feature to work - Select the tasks, click on three dots, select move to from drop-down and have backlog as an option of where we are moving the tasks to.Current Behaviour - No option to move tasks a backlog from a project.
There could be a visual cue (like name initials) when people are inside the ticket checking it. Like for example when we open a proof that shows whomever is in there by displaying the initials on the top right side of the screen
Description - Fix how the "favorites" bar works Why is this feature important to you - It's bad UX and after 6 of those apps the menu gets truncated. it's not really favorites since it keeps any app that has a module placed in the canvas How would you like the feature to work - If it's "all apps used in this scenario" Don't name it "favorites" If it's "favorites" Don't remove apps when not used in a scenario Same faves across all scenarios (ie, user-based) In either case App bar should be scrollable The + (add) should be always visible (currently it moves outside the viewport) The popup menu of the app's modules should be placed so the right edge is within the viewport Current Behaviour - one icon per each app in scenario (whether connected or orphan) not "favorites" but specific to scenario re-generated when going into edit mode (apps that are not used in the scenario get removed) length of favorites bar grows with window width as apps fill bar the popup menu becomes unusable due to placement
Taking the actual hours and then only planned hours from today forward.
Ability to templatize a Workfront Planning table and attach it to a project for easy asset tracking like they do in AirTable.
Librarian would like updates in AEM to synced back to WKFT to mitigate a disconnected communication experience.
Differentiate between user cost to role cost and ability to put a freelancer on any task and override with the freelancer cost.
Description - We would love to be able to freeze columns in a workfront report Why is this feature important to you - while teams need all columns, they want to be able to quickly view key columns that change priority quickly and easily How would you like the feature to work - be able to turn on and off freezing easily and adjust which column freezes Current Behaviour - we are aware of creating separate views, but freezing would work much better for the users
Description - Block access at the proof level and only allow those listed to proofWhy is this feature important to you - we've had some requesters find their way from the Document section and interject before the asset is ready to share out.How would you like the feature to work - Allow access from the Workflow level for the versionCurrent Behaviour - Anyone with project/task access can navigate to a proof from the document section and start commenting. Once they are in a version (accidentally) they are added to the the Workflow in a new stage. We can set the Requester access level and restrict it for all but it would be nice to do it from a proof/version level especially during internal proofing before the asset is shared back to the Requester/stakeholder..
We currently have teams that create a strategy document that includes information for many teams. The Creative Team is requesting the teams make requests in WF with only Creative needs and not the whole strategy doc attached. The requestors provide screen snips of images and text describing their needs in the document. Not all information is relevant in the document for the Creative Team so we moved to custom fields in the Custom Issue/Request form. There is not a custom form field format to capture this information in the request. I opened WF support case #00390925 "Ability to copy/paste images and add to a custom form field" and was told the functionality doesn't exist and to enter an Idea. See attached examples that were also included in the WF case. The requestors would also like to add information in the custom form fields in a table format that is much easier to read, interpret and digest vs. adding fields for each row of a table. See attached doc with an example. The data captured in the new fields, especially the table, will need the ability to run reports on those fields whether within WF or exported out of WF. Description -Why is this feature important to you -How would you like the feature to work -Current Behaviour -
Request for Feature Enhancement (RFE) Summary: Publish all content fragment live copies in one go Use-case: Currently we are able to rollout a fragment 300+ Live copies but to publish the same fragment we have to go to all 300+ live copies and manually publish which makes impossible to do. Current/Experienced Behavior: Currently we are able to rollout a fragment 300+ Live copies but to publish the same fragment we have to go to all 300+ live copies and manually publish which makes impossible to do. Improved/Expected Behavior: An option to publish content fragment similar to rollout. Environment Details (AEM version/service pack, any other specifics if applicable): AEMasCSAdobe Experience Manager 2024.9.17689.20240905T073330Z-240900 Customer-name/Organization name: Bread financial Screenshot (if applicable): NA Code package (if applicable): NA
Description - Why is this feature important to you -Business wants to understand the profile count for reporting in advance without actually triggering communications (Email/DM/SMS) but custom action can work as intended. This is mostly because of condition checks added in the journey and, to gauge the journey's behavior given the high volume. How would you like the feature to work -1. Do not want this journey step events data going into the steps events schema as this is just a dry run. OR even if it writes it, expire the data after couple of hours. Given the high volume it is not ideal to write it (so toggle option to write or not would be good).2. Mock the Email/DM/SMS activity - Real communications must not be triggered except for test profiles.3. Produce a report to share with the business. Current Behavior -1. There is no dry run capability.2. Test Profiles option does not help much.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
