Build better products with our product team
Currently some of the smart list options have inconsistencies in the queries available for different data types.For example: Member of program: "Progam" has options "Is", "Is not", "Any". Program Status Was Changes: "Program" has options "Is", "is not", "Starts With", "Not Starts With", "Contains", "Not Contains", "Is Any".Another example Person Score: "Person Score" has options "Is", "Is not", "Between", "Greater Than", "less than", "At Least", "At most", "is Empty" "is "not Empty"Score was Changed: "Change" has options "Is", "Is Not"All fields should have a set field type String, Date, Integer,... All fields of the same type should have the same options available. By this my suggestion is to add the missing options (rather than remove available options)
It would be great if Workfront added to the roadmap (maybe as part of the transition to Adobe Experience League/Admin Console) an alternative to the .cmd extension used for SSO users. Our network blocks the use of .cmd extensions in browsers for regular SSO users. This is usually not an issue since most SSO connections do not use the .cmd or provide alternative ACS URLs due to the security risks presented by .cmd extension being allowed in a browser. Our team has reached out to Workfront support on this already and there is no current alternative so we hope this innovation lab idea will help start the process.Here are links to the previous support cases for reference:Case: 00308693 (workfront.com)Case: 00312618 (workfront.com)
The current Adobe CC & Photoshop Extension only allows users to add documents to tasks (and issues). We prefer working from the project level and lose out on core functionality.
I use folders to organize thousands of offers. I don't always remember what folder a piece of content is in.The search only works within the directory you are currently in - I need for search to search the entire library of offers. Without that function, it is pretty worthless. Thanks.
We are looking into Workspace reports’ usage. The goal is to have visits or pageviews of each report (Dashboard) we have in Workspace in order to classify them by importance and then delete the ones that are not used. This would be very useful for reporting teams in the long term.
Prevent issues/requests from being converted into tasks/projects:I would love for a setting that completely prevents users from converting certain request types (ones I select as an admin, not all requests) into projects? Despite our attempts to educate users on specific work processes, some users convert requests into projects, even though they are to be managed only as requests.Add option to lock issues from editing after they are converted to task/project:Our users have a habit that's hard to break in which they will continue to update an Issue that's been converted to a Project, rather than update the Project. They just don't realize the difference between the two objects, and I realize part of it is ongoing training even though this has been communicated over and over. I know that in Project Preferences > Tasks & Issues there is an option to delete an issue once it's been converted to a project but we do not want to have the original issue deleted. Could we add an option so that issues can be 'locked' from editing after conversion?
Description - On the Projects page, the user should be able to filter the projects for any tags and have the full list be relevant to the chosen values, instead of a combination of all pinned, and then the results afterward.Why is this feature important to you - I have any number of projects at the top of my list that I have pinned for ease of use when I come into Adobe Analytics, and requiring me to scroll past them every time I go to filter for a report I need to open is frustrating and a productivity killer.How would you like the feature to work - Upon entering the first tag, the ENTIRE LIST of projects is filtered according to the value listed in the TAGS.Current Behavior - All favorite/pinned projects remain visible at the top of my results list, regardless of the tags I have entered into my filter, and then I am forced to scroll past my pinned projects to find the results I am filtering to find. EDIT: Aside from all this, I really do appreciate all of the changes that have been made to the Workspace Projects page so far. It's definitely better than it was before.
The Text Field with Formatting is a great new display type that we'd love to convert a lot of our existing fields to. This display type can only be selected when creating a new field, so existing fields can't enjoy the benefits of text formatting.
Description - Adobe provided playground environment for developers and admins to practice skills learned throughout training.Why is this feature important to you - While the examples provided during training cover the basic skills necessary to operate within the platform, those are based on the OTB offerings. A playground environment for training would allow a safe space for practice outside of training especially for those of us whose Prod environments are highly customized.How would you like the feature to work - It wouldn't need to be a direct copy of each users' Prod environment, rather a playground environment which you can use for all trainings and always have available for further practice outside of training.Current Behaviour - Currently our account has a QA environment which is doubling as a playground.
It is very often when the legend part of the visualization requires manual edit for making the chart look cleaner and easier to read. It would be very helpful to add a new setting that would allow to not include Metrics and Metric Filters (column names) in the legend labels. This is how it looks when a metric is filtered by dimension, segment, date range or their combination. The legend becomes too heavy that is especially critical for dashboards. This is a desirable way of how the legend should be displayed that today requires manual update of each label. Here is how that new setting could look in the settings popup.
Being able to set labels in our visualizations is great, we can immediately see where the label is going and how it will look... but the problem comes when the freeform table has the slightest change (like the dimension breakdown, which doesn't impact the columns), forces the labels to re-populate with the default value. Let's take a simple example. I create a freeform table with Referrer Instances at the top, and that broken down into columns by Referrer Type. Then I use Day as my dimension. When I visualize this, what do I get:Referrer Instances [Referrer Type: Search Engines]Referrer Instances [Referrer Type: Typed/Bookmarked]Referrer Instances [Referrer Type: Social Networks]Referrer Instances [Referrer Type: Other Websites]Since I am going to label my visualization and add a description of what this data is, I don't need it repeated in this fashion all through the legend labels. I want them to be clean, not this ugly version: So here is where renaming comes in, great! Love that I can rename them. (Search, Direct, Social, Other - done) But here's where the issue of the default comes in... let's say I want users to be able to select a set of rows from the table to focus on one part of the overall data.... the labels on the visualization reset to the default values... Or if I want to duplicate a table to do a different dimension... I want my columns to have the same visualization labels, but I have to rename every iteration. So in some cases I am wasting time on every report re-labeling the same sets of columns to make the report look presentable... or having to leave the defaults in there because once users start selecting rows it makes no difference cause I can't control what shows... There is obviously a need for these default generated values (something that we can always revert to), but I would love to be able to also set "actual values" or even "defined how the auto-label should populate" at the column (or even report level - even if it's take the "top" or "bottom" value (metric or segments, etc) on stacked value, or concatenate in this order, etc (I'm sure there are a lot of options that could factor into this). The modify at visualization level would then take priority over that.So it would be (in order of prioritization):1. Visualization Level Set Value2. Column Level Set Value (new)3. Report Level Custom Generated Values (new)4. Standard Default Generated Values Providing more control on how our labels are generated could save so much time on creating and styling our reports, and make the interactivity of the reports work better and more consistently with what our users would want to see (ease of reading)
It would be helpful to see achievements in the user profile update feed such as completion of tasks and requests as well as proof decisions.
It would be very helpful to have an interactive filter (magnifier) at top of report list on report screen rather than having to create a filter for every search term when looking for a specific report or key word
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