Product ideas | Community
Skip to main content

Ideas

Filter by idea status

10000+ Ideas

Enhancing Workfront Search Functionality for Improved Project DiscoveryNew

DescriptionThe current search functionality in Adobe Workfront can be improved to enhance efficiency when searching for past projects, especially when looking for work done by other team members. Users who frequently need to locate previous projects based on specific owners or project types often face limitations that slow down their workflow.This enhancement proposal focuses on two key improvements:Expand the search functionality to display all potential project owners when searching by name, rather than restricting the results to only the top 10 suggestions. This is especially critical when dealing with common names, as it limits visibility and makes it difficult to locate the correct project owner.Allow users to filter by both "Project Type" and "Project Owner" simultaneously. Currently, selecting a project type disables the ability to also search by a person’s name. Enabling both filters at once would streamline the search process and significantly reduce the time spent manually sifting through results.By addressing these limitations, users will be able to locate past projects faster and with greater accuracy, improving productivity and efficiency.Why is this feature important to you?The ability to quickly and accurately locate past projects is crucial for productivity and knowledge-sharing within teams. Many users, including myself, frequently search for past work done by other team members to reference best practices, locate assets, or gather insights for new projects. However, the current search constraints make this process cumbersome and time-consuming.For users dealing with common names, it is frustrating to be limited to the top 10 results, as it often excludes the actual person they need. This results in extra steps, like manually scrolling through project lists or reaching out to colleagues to track down information.For users who need to filter by both project type and owner, the inability to do so forces them to either search by project type alone (which results in too many projects to sort through) or by owner alone (which doesn’t always narrow down the search enough).These inefficiencies contribute to unnecessary delays, impacting overall productivity and collaboration across teams. By implementing these search enhancements, Workfront can provide a more seamless and intuitive experience for users handling large volumes of projects.How would you like the feature to work?To improve Workfront’s search functionality, I propose the following enhancements:Expand Name Search Capabilities:Instead of limiting search results to the top 10 project owners, Workfront should allow users to type in any name and display all matching results.A potential solution could be an "expand results" button that reveals additional names beyond the top 10.Alternatively, Workfront could enable a scrolling list of names or allow users to enter a full name (first + last) for more precise filtering.Enable Dual Filtering for Project Type and Project Owner:Users should be able to select both a "Project Type" and a "Project Owner" simultaneously in the search function.This would allow users to refine their search criteria efficiently, leading to more accurate and faster results.A dropdown or multi-select filter for project type, combined with the improved name search functionality, would optimize the experience.With these enhancements, users would be able to locate past projects more effectively, reducing the manual effort currently required to find relevant information.Current BehaviorCurrently, Workfront’s search function has the following limitations:Limited Name Search:When searching for a project owner with a common name, Workfront only displays the top 10 matches.Users cannot type a full name to refine their search or see all possible matches.Restrictive Filtering Options:If a user selects a "Project Type" filter, they cannot also filter by a specific project owner at the same time.This forces users to choose one filter or the other, resulting in longer search times and difficulty in pinpointing the correct projects.By addressing these challenges, Adobe Workfront can significantly improve its usability and help teams work more efficiently. Enhancing Workfront’s search functionality with expanded name search capabilities and the ability to filter by both project type and owner will have a meaningful impact on user productivity. These changes will enable users to quickly locate past projects, improving workflow efficiency and collaboration across teams. This feature aligns with Adobe’s commitment to providing an intuitive and powerful project management platform that evolves to meet the needs of its users. 

Archive audiences and profile scripts and filter their listsNew

Description - 1) Add the ability archive audiences and profile scripts in Adobe Target. 2) Add the ability to filter achieved, inactive and active audiences and profile scriptsWhy is this feature important to you - We have hundreds of audiences and profile scripts from both Adobe Target and Adobe Target Classic. We cannot delete Profile Scripts because they are used by in-editable Audiences and Audience can't be deleted because they are used in in-editable campaigns. It makes it hard to find the right profile script, especially if debugging an emergency. How would you like the feature to work:Edit Profile script:  Add an archive/unarchive button with a confirmationProfile Script list: add filter button next to the "Search profile scripts". Clicking the filter button would show the ability to filter on status with 3 checkboxes for active, inactive and archived. Active and inactive would be checked by default and inactive uncheckedFix the STATUS sort: when you click on the header,  it should sort by status not name.Edit Audience: For Adobe Target and Adobe Target Classic Audience Only, add an archive/unarchive button with a confirmation Add to Audience Library filters the ability to filter by status: active and archived. Active would be checked by default and archived unchecked.Current Behaviour: Audience search only allows you a simple contains search with the ability to filter by source (Adobe Target, AEP, etc).Profile Scripts only allows a simple contains search. The order by "STATUS" doesn't order by status, but by "NAME"No ability to filter by status for either

Force Workfont to display a project timeline in the project's defined time zone, rather than the user's time zoneNew

Description -  Currently, Workfront utilizes the time zone on the user's computer to determine the times and dates for tasks versus the setup time zone within Workfront for the user. It also ignores the time zone schedule of the project. We are finding issues with this in a few locations within Workfront. For example, in the Time Off section, if the user's setup time zone within Workfront is not set to the same time zone as their computer, it will select 2 days when trying to select 1. Another example, if a user is located on the West coast and their computer is set to PST, but their Workfront time zone is set to CST, it will override the CST and use the computer's time zone. This is especially difficult for Planners that are setting up due dates and times for tasks within a project. We'd like Workfront to stop referencing the "computer" time of users and set all users to CST, regardless of where are they are located in the world.  Configuring user accounts with their actual time zone doesn't work, either. Our default schedule in Workfront is set to CST so when a Planner goes to schedule tasks and their time zone is set to something other than CST, the planner hours fall over different days, messing up the Workload Balancer. Why is this feature important to you - Times are showing up different for users depending on their physical time zone which is causing a great deal of confusion across our global company.  How would you like the feature to work - The system should display times in the time zone schedule assigned to the project, or, Workfront should not reference the time zone of the user's computer and refer only to the time zone configured in their user account. Also, time entered in PTO should be entered as CST so that the PTO doesn't incorrectly affect the workload balancer or planner. Current Behaviour - Our default system schedule and projects schedules is CST. If a person in another time zone enters a full day of PTO for a single day, it places the time off over two days in time off calendar and adversely affects the workload balancer. All of this refers to original support ticket E-001557318, which was rejected by Adobe Workfront Support, that it is "not feasible within the current scope of our work".

achepurnyLevel 1

Enhance Data Elements with JavaScript Promise SupportNew

Summary:Expand the capabilities of Adobe Launch Data Elements by enabling them to return JavaScript Promises. This feature will allow asynchronous data retrieval and processing directly within Data Element configurations, enhancing flexibility and power for dynamic data handling.Problem Statement:Currently, Adobe Launch Data Elements are limited to storing static or computed values within the confines of Rules. While they are invaluable for capturing and managing data on web pages, their functionality is constrained by synchronous operations. Asynchronous tasks, such as API calls or event-driven data retrieval, require external code, limiting the tool's potential for multisolution integration and Extension Development. Proposed Solution:Introduce exiting functionality with Rules where Data Elements can return JavaScript Promises. This will enable asynchronous operations directly within Data Element configurations, allowing users to handle dynamic and async data retrieval without leaving Adobe Launch's interface. Key Features: Promise Return Option:Add the ability or an option in the Data Element configuration to specify whether it returns a synchronous value or a Promise.Asynchronous Functionality:Allow users to define asynchronous functions within Data Elements, enabling tasks like API calls or event handling directly from the Data Element setup.Code Snippet Support:Provide fields for embedding code that defines how the Promise is created, making it easier to handle complex async operations.User Experience Enhancements:Include templates and examples for setting up Promises within Data Elements, ensuring a smooth transition for users familiar with asynchronous programming. Benefits:Enhanced Capabilities:Users can perform advanced tasks like API data fetching or waiting for events directly within Data Elements, making tag management more dynamic.Extension Development:Give the Developer the ability to leverage Browser APIs in their Custom Extension Development. (Shoutout to @yuhuisg)Simplified Workflows:Reduce the need for external code by handling async operations natively in Adobe Launch, streamlining the development process.Backward Compatibility:Existing users will see no changes unless they opt-in to use Promises, ensuring a seamless transition and minimal disruption.

bjoern__koth
Community Advisor and Adobe Champion
bjoern__kothCommunity Advisor and Adobe Champion

Improved Search in LaunchNew

Description Currently, the search in Launch is barely useful, since it returns a very fluffy set of results, that quite often do not help finding what you are looking for. Quite often, the results just show a "... more" in the results list, but without actually giving you a chance to find what you are looking for.   This leads to developers rather not changing any DE names once in use to not break anything.   It would be awesome to be able to have more search features like "exact match" "regex match" case sensitive yes/no etc. Also, a optional dedicated search detail page that lists all the other results would be great! Ideally with a preview of the match.   Out of this need, external tools like the "Perpetua Digital Launch Assistant" are being developed, just addressing these shortcomings.   Why is this feature important to you Everybody knows you cannot just rename data element in Launch without potentially breaking things. Hence, whenever I want to rename a DE, I open the website first and search for any occurrenced of the DE in the rendered Launch library, to get a clearer picture where to start digging go back to Launch and rename there based on my findings Essentially, I never use the Launch search feature.   How would you like the feature to work more search options as described above a dedicated search page that lists all results   Current Behaviour it is hard to find what you are looking for depending on the search term, many "other..."  results fluffy search, returning false positives that do return results that do not match the search term