Build better products with our product team
The vast majority of users within our organization that utilize Workfront are not Project Managers and have little to no experience with project management tools but are looking for an easy alternative to Excel. As such, we don't expect these "non-technical" resources to dig into the differences between all of the available task constraint options or create flowing, linked task lists in which options like "As Soon as Possible" would apply. We always direct these users to change their task constraints to "Fixed Dates" when creating new tasks in order to have full control over "planned start" and "planned completion dates" of their tasks. This further complicates the process for already overwhelmed newcomers to the tool, and is the cause of a lot of strife for onboarding new teams. A great solution for this would be to create a settings option within "Setup -> Project Preferences -> Tasks & Issues" in which a system admin could set the default value system wide for the "Task Constraint" field.
Request for Feature Enhancement (RFE) Summary: Either enable copying the path to an asset within the AssetLink file details page or jump straight to the asset in AEM by clicking the path. Use-case: This feature would unlock all the information stored with the asset right from Asset Link. Current/Experienced Behavior: path can neither be highlighted and copied nor clicked Improved/Expected Behavior: as described above Environment Details (AEM version/service pack, any other specifics if applicable): InDesign 202217.0.1 AssetLink3.1.65 AEM 6.5SP9 Customer-name/Organization name: Spar ICS + Spar Austria Screenshot (if applicable): Code package (if applicable):
Please remember to hit the LIKE button to vote for this idea! Description - When the Key Metric Summary was first introduced, it originally displayed the metrics with the number larger, ON TOP, larger, with the percentage smaller, and ON BOTTOM, like this: Now that some significant changes have been made (sometime after the new year), and the feature has finally been repaired (after work I just completed with Customer Care), the formatting has also been changed so that the percentage permanantly displays OVER the number, with no ability for us to swap their positions. This is frustrating, because it used to display just the opposite, and we have no abilty to change how it's displayed. Consequently, I am proposing the following:Not only should we have choice whether to emphasize the percentage or the number, but we should ALSO have the option to decide which number displays on top, which means the display should be dynamic, based upon the user's choice.Why is this feature important to you - Data storytelling remains important, and the way numbers and other elements appear in a certain manner is relevant to the flow of anyone's Workspace. What may feel nitpicky to one will feel huge to another, and this was a big change! How would you like the feature to work - Adobe is already fairly close by providing us the choice to "Emphasize the number" vs. "Emphasize percent change." All they need to do is then add the option to say, "Show emphasized item on top," OR they could simply bypass that option and simply place the emphasized item on top automatically. Current Behaviour - Currently, the emphasized number or percent change displays larger, but they remain in place, which is not ideal.
We utilise Workfront to deliver projects to our customers utilising partners and our internal team. This means per project we have different Billing rates per role, but more importantly we have different cost rates per role. I need the same ability we have to manage billing rates but for COST rates, by role, per project for defined time periods. Otherwise I need to duplicate roles per partner per project resulting in potentially thousands of unmanagable job roles.
We've had the need to add tasks and Iterations to the Typeahead field in our organization, I believe extending the functionality to include other object types will be useful. Would this be a simple implementation for the future?
Description - We would like to enhance the filtering in the AEP UI. Why is this feature important to you - Having the ability to further drill down into filters via the UI, unlocks more capability for the users of AEP. How would you like the feature to work - Filter by audience on dataflow runs pages, adjust column sizing and filter for what is currently processing- Filter and sort by audience, start date, or end date on activation data page, and adjust column sizing. Current Behaviour - No current ability to do any of the above filtering in detail.
Request for Feature Enhancement (RFE) Summary: Please increase the upper limit of the number of workflows that can be executed simultaneously Use-case: There are cases where many workflows (No. 1, No. 2) occur simultaneously. 1.Publishing process Approval flows may occur simultaneously to publish multiple products at the same time on the same date and time. 2.Back processing Cyclic processing for linking with other systems (once/5 minutes) Approval flow in production work (movement, deletion approval) As a result, there is an issue of delays in publishing products with specified dates and times Current/Experienced Behavior: Insufficient increase in the number of workflows that can be executed simultaneously Improved/Expected Behavior: Increase the number of workflows that can be executed simultaneously. Environment Details (AEM version/service pack, any other specifics if applicable): AEM Release 2024.5.16461.20240524T172309Z Customer-name/Organization name: Panasonic Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Introduce a one-click configuration that syncs AEM DAM with Dynamic Media for asset deactivation and deletions Use-case: Today when an asset is unpublished from AEM, author has to manually unpublish from DM also using Tools --> Assets --> CDN Invalidation. Second, if asset is deleted from AEM, it NEVER automatically deletes from DM. Second asset in same name appends -1 numerals in DM urls. This forces developers to write custom implementations to maintain sync between AEM and DM. Current/Experienced Behavior: Asset unpublished / deleted from AEM does NOT unpublish / delete corresponding assets from DM. This causes flux, unsync between AEM and DM Improved/Expected Behavior: Create a DM configuration that can sync AEM with DM. So unpublish/delete from AEM should automatically perform same actions from DM as well. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS latest, likely affects any AEM version Customer-name/Organization name: SouthernGlazers Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Introduce a one-click configuration that syncs AEM DAM with Dynamic Media for accepted formats. Use-case: Today we have a AEM DAM delivery folder that is synced with DM. This DAM folder accepts ALL AEM compatible formats. But they fail to upload into DM, since DM allows only restricted formats. We found after certain assets failed in production. Now adding extra implementation to reject DM incompatible formats in AEM. Current/Experienced Behavior: AEM accepts more asset formats than Dynamic media. This causes AEM assets succeed at AEM, but fail at Dynamic media. Improved/Expected Behavior: Introduce a one-click config, when enabled, AEM should also reject DM incompatible asset. Reduces maintenance overhead. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS latest, likely affects any AEM version Customer-name/Organization name: SouthernGlazers Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Extend the "Explain Query" tool to capture graphql queries and suggest optimizations over gql queries Use-case: We are running multiple graphql queries on AEMaaCS and works in Production. Periodically some queries run longer time and sometimes heavy queries crashes the server. Current/Experienced Behavior: No tool to analyze and suggest optimizations for GraphQL queries. Improved/Expected Behavior: Build a tool similar to "Explain Query" for JCR queries that can suggest optimizations for graphql queries. Provide insights on execution time and cost for traverse and reference. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS latest, likely affects any AEM version Customer-name/Organization name: SouthernGlazers Screenshot (if applicable): Code package (if applicable):
Just a reminder to everyone, a LIKE means a VOTE for this idea.It always confuses me when I see tons of views for ideas, but hardly any "likes." Description - How many times have any of you spent creating a Workspace in Adobe Analytics, only to have any number of Visualizations that you would now like to format similar to one you have recently updated? What do you do? Do you delete the old ones, and copy the new one so you may then tie them to the data table? Or, do you simply proceed to each and use that new visualization as your guide to update the others?Why is this feature important to you - This would be a productivity UPLIFT. There are plenty of times when I'm adjusting components in a workspace that I would love to simply apply changes I just made to related items. How would you like the feature to work - For this specific feature, I would simply like to go to the Visualization I like, right-click on it, select "Copy Visualization," select the Visualization I wish to update, rightl-click on it and have a choice available that says, "Paste Formatting." When I do, the component/Visualization "snaps" to emulate the formatting of the component I just copied, with all of the data intact. EXAMPLE: AND THEN: Current Behaviour - At this time, there is no functionality provided to perform this kind of activity. I would either have to copy the new component multiple times and connect it to the appropriate data; OR, I would have to simply update individual components to match the new component I just updated, one at a time.
Description - Row level filtering from batch source connections Why is this feature important to you - Ability to filter out rows of data based upon specific filtering criteria. How would you like the feature to work - Utilize the flow service api to specify a row level filter parameter for all batch source connections. Current Behaviour - The ability to filter row level items is only available using Snowflake, Dynamics, Saleforce, and GBQ. https://experienceleague.adobe.com/en/docs/experience-platform/sources/api-tutorials/filter
Description -We'd really like to be able to lock down the ability to delete proof comments from certain users. Why is this feature important to you -We have our Compliance teams beginning to use Workfront and would love to be able to "lock down" this particular ability to meet regulatory requirements/guidelines. But we don't want to lock it down system wide/for other roles in other departments. How would you like the feature to work -Ideally I'd be able to toggle the ability to delete comments on or off a proof profile. Current Behavior -Currently you can only toggle this feature on/off system wide, there is no way to customize by user/etc.
Description - As far as I understand in the settings for an access level, I can restrict if users can only see other users from their company and additionally from the primary company. I would like to have the possibility to restrict users to see users from their company and other users, who are als members of any team / group these users are in.Why is this feature important to you - Users of companies other than the main company should be able to interact with users of other companies, but only with users with whom they have a specific defined connection.How would you like the feature to work - A third option under People in other companies should only view users from..., meaning "Groups / Teams they are also members of".Current Behaviour - Currently if the option Their Company is activated, only users of their company are visible. Setting the option The Primary Company extends this functionality to all users of the primary company.
Since Workfront changed the keyboard shortcuts to indent tasks from tab to Option+>, it's been really inefficient to quickly add new tasks to project templates. With the latest release, it's no longer possible to indent or outdent tasks during the creation of a task. A user now needs to add a new task, click out of it, then indent or outdent, which adds an extra step and slows you down. Aside from the keyboard shortcuts no longer working for templates, the indent/outdent options do not appear while you are creating a new task.
Hi Adobe Product team - this idea has been raised previously multiple times with no response so raising it again. While there are APIs available for Properties and Hosts, , currently there's no API that allows us to get names of workspaces. Workspaces are integral part of Adobe Target now and most of the other APIs return "workspace-IDs" in the response. End-users cannot understand the "IDs" which leads us to build custom solutions like a lookup table which is not an efficient solution. We'd like to have an API that returns: 1. Workspace IDs 2. Corresponding workspace name 3. Optional - all property-IDs where this workspace has been used Thanks in advance Regards Rajneesh
Description - Similar to how we can leverage the Blocklist to remove attributes or segments that should not influence AI models, it would be helpful if we could add 'weight' to other attributes/segments to help the model identify likely influential data. There are times when we think certain segments are likely to be a component to influence the models. My hypothesis is that by weighting these, it could help models that may be otherwise struggling to fully form.Why is this feature important to you - We have found in some situations where the AI was not able to generate working models with specific influential attributes and I'm wondering if this might help? I realize this may be slightly contradictory to how the model is supposed to workHow would you like the feature to work - Could work similar to blocklist via the APICurrent Behaviour - No current ability to add emphasis to attributes or segments for AI models
Description - We have been trialling a number of Auto-Allocate/Target activities and we have unearthed that due to our geographical position we are unable to separate specific market/environment activities from the default environment when there are multiple environments present. The attempts to trial market specific activities results indicate that AI does not have an impact and the added reports (Pers. Insights/Important Attributes reports) not present. With the current documentation outlining that any activity that incorporates the default and another environment that it outlines the hits and conversions are 'Considered' but essentially requests are all served by the default environment. Why is this feature important to you - It is important to be able to run the AI tools within Target that are not reliant on using and including the default environment which is a huge limitation for us. This enables market separation when launching a new AI delivered activity. How would you like the feature to work - When creating a new Auto-Target/Allocate/Personalisation activity having the option to determine which markets/environments for the activities models to be based on(Single or Multiple). Currently any test has to include the default, each of the activities should be dependant on the environment/market you want to run an activity on or on multi environment activities to select what environment is the decisioning source. Current Behaviour - We are currently using Auto-Allocate and Auto-Target, and whilst we have seen success in these tools we've observed and proven that the tools are not usable if you use within markets other than the default environment. For those users who work geographically and want to launch specific experiences for specific markets we are unable to without including the default environment, even then the data from the market is only 'Considered' as apart of the model not a decisioning element.
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.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK