Build better products with our product team
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 this time making it difficult to find important updates.
Description - It would be much nicer the Edit Text Mode button enabled editing in the main windows instead of having to put it in the tiny popup window that appears. Why is this feature important to you - The edit popup is so small you can't really use it. You have to do your editing in an external editor and past it into the popup How would you like the feature to work - upon clicking "Edit Text Mode" the main window where you can see the code should be enabled for editing.
Description - If your text mode code includes a long line(s), the window widens to the point that the Edit Text Mode button isn't visible on the screen, making it easy to think that the button doesn't exist, especially since the code wraps in the edit popup window. Why is this feature important to you - multiple times we've had users think there was a bug because they couldn't find the button How would you like the feature to work - The button should always be visible on screen
Description / Current behaviour:If a Task has Revenue Type = Role Hourly [With Cap / Plus Fixed] setting, the Planned & Actual Task revenue is calculated with the Billing Rate associated with the Assignment Role(s) of the Task.The Billing Rate applied may be the default one set on the Job Role, or one that is set on the Company / Project for that particular Job Role.If a Task has multiple Assignments, revenue is calculated for each of them separately (using Assignment Role) and then summed.For User Assignments (as opposed to Role Assignments), the Assignment Role (labelled as "Assignee's Role" on the UI) can be (only) one of the Job Roles associated with the assigned user.The following business problem exists with this scenario:A task is planned with Job Role X and sold to a client at a price calculated with Job Role X.Given task is assigned to a user with Job Role Y (since a user with Job Role X is not available)The Assignment Role will be Job Role Y, i.e. the Job Role of the User.Workfront calculates the planned / actual revenue of the Assignment using the Job Role of the user (Job Role Y).Consequently, the planned/actual revenue of the assignment (and of the Task and Project) is incorrect, since the correct figure would be calculated using Job Role X.How would you like the feature to work?When editing Assignments of a Task, any active Job Role can be specified as "Assignee's Role" not only the Job Roles associated with the assigned user.The planned / actual revenue for the assignment is calculated with the Assignment Role (as it is now).Role Hourly revenue can be calculated with any role, not only with one of the assigned user's own roles.For convenience, project level default assignment roles can be defined for each project team member.If a project level default assignment role has been defined for a user, when that particular user is assigned to any task on that particular Job , the "Assignee's Role" (Assignment Role) on the new Assignment will automatically be set to the user's project level assignment role.It should be possible to manually change the Assignment Role to any Job Role.When setting a project level assignment role for a user, the Assignment Role of this user on this project on existing Assignments is not changed.Configuring project level default assignment roles can commence either on the "People" tab of the project or in a new Column labelled as "Default Job Roles".Project level default assignment roles can't be date effective. They apply to the project regardless of the date.The proposed way of working will be really critical to our new core design!
Description - Currently deleting archived cards is a method to improve board performance. Rather than manually deleting one-by-one there could be a setting that controls what & when archived cards are auto-deleted by the systemWhy is this feature important to you - It takes time to manually delete a card one-by-one, and one has to remember to do so.How would you like the feature to work - This feature would mimic the existing archive setting where you could control when a card gets deleted (# days, # weeks etc) (see screenshot)Current Behaviour - There is no automation.
We'd like to have the option to apply contouring (i.e. edit the distribution of the allocated hours per day/week/month) to tasks & issues in the "Unassigned Work" section of WLB. The UI would be the same as that in the Assigned Work section. A task's resource needs fluctuate during the span of the task and it is often known before a user is assigned but can't be captured via the Workload Balancer UI at the moment. This would make resource planning easier and more real-life.
Description - I want to create additional rules for marketing channels but it says rule 4. Even if i create one more it says Rule4 only. It might be a bug. How can I reference these if names are same.Why is this feature important to you -Even if i create one more it says Rule4 only. It might be a bug. How can I reference these if names are same.How would you like the feature to work - add edit option to rename the ruleCurrent Behaviour - no edit option
Description: The Search UI has recently changed in Workfront removing both the ability to simply close window when finished searching to return to the page you were on and the ability to have your search filters per object type persist.This change impacts our user base negatively enough that we assumed it was a bug and I put in a support ticket. I've received the following response: What Changed in the Workfront Search UI?Full-Screen Search: The Advanced Search is now a full-screen experience. When you open the search, it overlays the entire page.No Close Button: The new design does not include a close (X) button to exit search and return to your previous page. Instead, you must use the browser’s back button.Navigation Impact: If you perform multiple searches or add filters, each action adds to your browser history. Returning to your starting page (e.g., a project) requires multiple clicks on the back button, which can be cumbersome.Consistency: This behavior is the same across Chrome and Firefox, on both Windows and Mac. Why Was This Changed? According to Adobe Workfront’s official documentation: The Advanced Search is now full screen. You must navigate away from the page rather than closing the dialog.This update is part of a broader interface modernization effort to make Workfront more consistent with other Adobe applications. However, it has unintentionally reduced usability in this area. Known Limitations and User ImpactThere is no way to simply “close” the search and return to your previous context. The filter is not prepopulated and does not persist after a refresh. The only way to return to your previous page is to use the browser’s back button, which can be tedious after multiple searches or filter changes. This affects all users and is not browser- or OS-specific. Workarounds & RecommendationsUse the Back Button: For now, using the browser’s back button is the only way to return to your previous context. Open Search in a New Tab: As a workaround, right-click the search menu and choose “Open link in new tab” (if available), so your original page remains open. Why is this feature important to you: Being able to simply close the search window when done searching is the simplest most efficient user journey especially if you are trying to eliminate user clicks as much as possible. Right now, with the update in place, if you perform a search and then add multiple filters in order to narrow down your search you will have to have either remembered to open a new window/tab for searching alone or will be forced to click the back button in your browser multiple times to return to your original page. Filters you set no longer persist to the next search which necessitates this multiple iterations in the search window every time you use it unless you want to use a simple, very generic search and not drill down past the first page of results If this is aligned to how search works in other adobe products, search should be updated across their whole product offering because this experience is terrible.How would you like the feature to work:1) Primary concern: Bring back the close button so you can simply close the search window at any time to return to the page from which the search window was opened2) Secondary concern: Allow filters to persist in the search window
Description:Adobe Campaign Classic (ACC) does not currently support the <amp-img> tag used in AMP mailers when uploading HTML content via the Browser folder option in the Email Delivery template. As a result, image paths are not updated to hosted URLs correctly, causing issues with rendering AMP emails.Why is this feature important to you:We are increasingly using AMP mailers to deliver richer and more interactive experiences to our customers. Manual conversion of <amp-img> tags to <img> tags is time-consuming, error-prone, and not scalable for larger teams or frequent campaigns. Supporting AMP-compliant tags like <amp-img> natively in ACC will streamline our workflow, reduce turnaround time, and improve accuracy.How would you like the feature to work:We would like Adobe Campaign Classic to automatically recognize and process <amp-img> tags when AMP HTML is uploaded via the Browser folder option in Email Delivery. The platform should update the src attribute in <amp-img> tags in the same way it currently handles <img> tags, enabling proper hosting and rendering of images in AMP emails.Current Behaviour:Currently, ACC only processes standard <img> tags for image URL rewriting. When uploading AMP HTML containing <amp-img>, the image paths remain unchanged, which breaks proper rendering in the final email. As a workaround, we manually replace <amp-img> with <img> before uploading, which enables URL rewriting but compromises AMP standards and is not ideal for production use.
Description - After Adobe Admin Console migration, external users created in Workfront need to be approved by system administrators, otherwise their accounts won't be active, and they won't be able to use Workfront. This is very time-consuming especially for larger organizations with 6k+ users. So, we would benefit from having an "action" available in Workfront Fusion that would automate the approval process for us.Why is this feature important to you - This will eliminate the manual effort of approving every user created in the system on daily basis. It will save time for the system administrators to look for the approvals daily and approve. It will also save the waiting time of the user, so they don't have to wait for approval to be able to use Workfront.How would you like the feature to work - an Action should be available in Workfront Fusion in the Update record -> "User" record type, so it can approve the users automatically.Current Behavior - at the moment when external users are created in Workfront, they stay deactivated until an admin goes and manually approves them, only then they become active and can start using Workfront.
Request for Feature Enhancement (RFE) Summary: Introduce the Apache mvnd (Maven Daemon) wrapper in Adobe Cloud Manager so that the build step can reuse a long-lived JVM, parallelise module compilation, and dramatically cut cold-start overhead. This change targets only the build phase; the deploy phase likely remains untouched. Use-case: Large, multi-module AEM as a Cloud Service projects (often 10 + modules) can spend several minutes just starting Maven and resolving plugins for every pipeline run. In busy CI/CD setups (feature branch builds, frequent merges, scheduled quality gates) these wasted minutes quickly accumulate, slowing feedback loops and consuming CI minutes. Current/Experienced Behavior: Cloud Manager invokes the stock mvn CLI in a fresh container for each build. Each invocation spins up a new JVM, scans plugins, and builds modules sequentially. Typical build duration for a representative 10-module project: 9–11 minutes, of which ~1-3 minutes are Maven start-up and plugin scanning. Developers compensate by using mvnd locally, but must still wait for slower pipeline feedback. Improved/Expected Behavior: Cloud Manager containers start an mvnd daemon once, then execute build goals through the daemon for the lifetime of the build step. Parallel module compilation (default --threads=auto) and reused class-loaders remove the repeated start-up cost (potentially the resources of the build-pod(s) need to be increased to provide more CPUs to work with in parallel). Anticipated build-step time-savings: 25-40 % on typical AEM multi-module projects (confirmed in local benchmarks and community posts). No impact on deployment logic; output artefacts (all-, ui.apps, ui.content) remain identical. Environment Details (AEM version/service pack, any other specifics if applicable): ---- Customer-name/Organization name: ---- Screenshot (if applicable): ---- Code package (if applicable): ---- Maven-Deamon (mvnd): https://github.com/apache/maven-mvnd Article: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-blogs/speed-up-local-development-in-multi-module-aem-projects/ba-p/738507
Occasionally, we have a situation where a lead is accidentally deleted or merged with the wrong record. When this occurs, we can restore most of the data including acquisiton program and date, program memberships with successes and dates, etc. However, we cannot restore the cookie association because the cookie ID is not exposed on the lead record (or its exported data). Please expose the cookie ID, so we can use the technique described by Jep in the Discussion item (Is there a way to reassociate a cookie with a lead record without the lead taking another action?) to reassociate their cookie with the restored lead record.
I've had a couple of clients now go to delete a My Token on a program only to be told the token is in use. Unfortunately there's no easy way to determine how the token is being used.This is increasingly important since tokens can now be added to Guided Landing Page templates and as long as the template is in place and approved it will prevent the deletion of the token.It would be nice to have a "Used By" column for My Tokens, just like any other asset in the design studio.
It turns out program tokens can be in use in very strange ways, which makes it a necessity to have the "used by" functionality for program tokens. A use case I came across today: Original token is set up in a campaign folder. Someone erroneously made changes to the inherited token in a program that was stored inside that campaign folder. The program with the incorrectly overridden token was then cloned to an entirely different campaign folder. The cloned program retained its reference to the erroneously overridden token in the source program. Therefore, when we tried to remove the token this was not possible as it was still in use. We needed Marketo Support to trace where that was, because in the UI it was impossible to figure out. Although it can be argued that the link to the original overridden token should be broken in the cloning, providing visibility on where a program token is used prevents this confusion already quite well.
It would be great to see a list of places throughout a program where your program tokens are being used.Even if there was some way to run an audit to do the same thing that would work as well.This would help to know if tokens are no longer being used or to see if there are any other places it is being used that are not initially apparent.
WorkFront has no ability to 'undo last action' - in some cases this can be very troublesome - as it is quite easy to make a change to basic project behaviour, critical path and end dates. An 'Undo' last change function would be very useful if the Project owner has in-advertantly made a change that has caused multiple activities to be impacted. Even a - revert to last saved version function might be useful - at least allowing the project owner to go back to a version that they have already reviewed and approved with their team.
Usually name of variables / metrics / segments, but also their value, are something really technical. That kind of values absolutely do not suit the needs of top management who cannot read technical description.Also, when we do complex workspace the name of column is hidden because no space available in layout. So, why dont allow to overwrite and change color of any string we have into column/row head or cell?
Description - Add field to capture the entry date of a report similar to the entry date of a issue, project, task, or user. Why is this feature important to you - This is important because I need to know how long a report has been available to be used. This helps tell the story of high quality reports that can be duplicated/copied for other users across my instance and peer customers of Adobe Workfront. If a report has been around for years and was recently modified that highlights importance and emphasizes need to secure it and have it monitored for quality control. The reports in Adobe Workfront are often used to drive key business decisions and knowing every aspect about a report is critical to data governance and management. How would you like the feature to work - Users should be able to add the field as a column (view), filter or grouping in similar manner as an entry date for a project, issue, or task. Current Behaviour - The field is not available in Workfront UI or API Explorer. @skyehansen
Description - The new calendar interface doesn't allow users to view as many rows as the old interface in each calendar day when in Month view. This is causing important information to drop off and have to be accessed by hovering over More.Why is this feature important to you - Our team prefers to have all items visible or at least be able to prioritize what they see.How would you like the feature to work - Allow them to reorder the items that appear in each day by dragging the important ones to the top of the list.Current Behaviour - Overflow tasks on each day default to More view and they have to hover over or click on them. The number of items also seems inconsistent. Some have 3 or 4 visible but others don't have any and default them to the more heading.
Description - Allow the option to hide the hourly breakdowns on weekly calendar view or expand the collection of calendar items in the top portion of the calendar Why is this feature important to you - We have many tasks that pull into a calendar view and the many tasks are now all scrunched together at the top. When the list is super long, a scroll bar appears and you can scroll within the tiny area. There is not a way to hide the hourly blocks below or expand the top portion to have better visibility into the items like the current/old calendar weekly view. How would you like the feature to work - Add a toggle button to hide the hourly blocks and/or a way to expand the top portion of the calendar to be able to see more items on the screen. Current/Old Behavior - New Calendar -
Please add the ability to grant to users view-only access to Admin sections. We need to grant to other users to see, for example, Report Suites's list and related information, variables, events and other useful sections, but this isn't possible at the moment - users with access to these areas automatically receive edit permissions.
Hi,when I create calculated metrics or segments for one data view, they also appear in other data views of my sandbox, if they are based on they use the same underlying schema. At first glance this looks good if you consider setting up a dev and prod data view and you only need to setup the calculated metrics and segments once. However, if the one data view based on which the calculated metric or segment was setup is modified or deleted, the calculated metrics and segments are not working anymore in the other other data view. Thus, it is required to setup the same calculated metric and segment in both data views. The issue here is that both calculated metrics and segments show up in each dataview in the workspace. However, for the analyst who creates a report the calculated metrics and segments of other data views are irrelevant.Please develop the option to show the calculated metric or segment only in the data view for which it was created. This would be much more user friendly.
Description -In Adobe Experience Platform's Event Forwarding, there is a requirement that OAuth2 tokens must have a minimum expiration time of 8 hours. However, the system we use internally for authentication only allows tokens with a maximum expiration time of 1 hour. This creates a compatibility issue, as we are unable to use our tokens with Event Forwarding due to this restriction. Why is this feature important to you -This limitation prevents us from integrating our internal authentication system with Adobe Event Forwarding, which restricts our ability to automate and scale our processes. Removing this requirement would enable us to fully utilize Event Forwarding in our workflows. How would you like the feature to work -We would like Adobe Experience Platform Event Forwarding to support OAuth2 tokens with expiration times shorter than 8 hours. Ideally, there should be no minimum expiration requirement, or at least support for tokens with a 1 hour expiration, which is standard for many authentication systems. Current Behaviour -Currently, Event Forwarding enforces a minimum token expiration time of 8 hours for OAuth2 tokens. Tokens with shorter validity periods, such as those generated by our internal system (maximum 1 hour), are not accepted by the platform.Configuring Secrets in Event Forwarding | Adobe Data CollectionDocumentation reference:An OAuth secret requires at least four hours between refreshes and must also be valid for a minimum of eight hours. This restriction gives you a minimum of four hours to intervene if problems arise with the generated token.For example, if the offset is set to 28800 (eight hours) and the access token has an expires_in of 36000 (ten hours), the exchange would fail due to the resulting difference being less than four hours.
The current 'Filter' in the Workload Balancer has limitation for the following functionalities whereby these are available in other objects type such as Projects, Tasks, and Requests.Select the Filter condition for "Include if all are true" or "Include if any are true". (Currently defaulted to ‘Include if all are true’ and not editable)Select 'Add Filter Groups' for filter operators 'AND' or 'OR'.Switch to Text Mode interface.It would be great if these functionalities to be made available in the Workload Balancer Filter to allow Resource managers to build complex filters for accurate resourcing.
Description - While using the HTTP Fusion module with the Basic Auth feature, the system creates a key (in the Keys section) for the credentials added. There is no option to update an existing key which was created in a case where the credentials were changed. We use many such connections to our internal services where the credentials are rotated periodically and to update them in Fusion, someone needs to find the usage of the credentials in the whole list of scenarios and update them manually after creating a new key.Why is this feature important to you - It takes a lot of manual effort to find and update every scenario, even with the use of the connection switch tool within the Fusion dev tools where a person needs to look through all the scenarios and update the HTTP modules.How would you like the feature to work - It would be nice to have an option to update an existing key from the Keys section where the users cannot see the existing credentials but are able to provide and save new ones. With that, the system should be able to switch to new credentials on every scenario instead of needing to do it manually.Current Behavior - The system only allows you to delete an existing key, and not update it. To change a credential for an HTTP module, the user has to create a new one and update all the scenarios manually.
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.
