I've been working with the new experience for several weeks now. I'm finding some odd behaviors with dashboards - specifically dashboards that are added as tabs to projects. We often use dashboards on projects because when you do so, the results for all the reports on the dashboards are filtered to the current project. This is a powerful feature. We use this to make project meeting dashboards. During a meeting, we call up the project, navigate to its meeting dashboard tab, then use the information presented as an agenda. It works very well. In the new experience, we're finding that some of the features don't work very as expected. First, the dashboard is truncated after about 2 screen-heights. You can scroll down a bit, but if there is more information than would fit on 2 screens, the rest of the report is cut off. The scroll bar stops at that point. There is no way to navigate to the rest. Chart behavior has also changed. In the past, when you clicked on a region of a chart (e.g. a bar on a bar chart or a slice on a pie chart), Workfront would present a pop-up table, showing the underlying records represented by that region. It's a handy and powerful way to navigate and focus on one subset of data. Now, when I do the same on a chart on a project-level dashboard, Workfront navigates to a new page with only the chart report on it. Worse, because the report is no longer filtered to only that project, I get results for the entire Workfront environment. I can't think of a use case in which this would be useful. Then, when I use the browser's Back button to return to the project, I'm shown the same dashboard, but it seems to be a static snapshot of the previous page. It doesn't allow scrolling. I have to refresh the page to get it to work again. Corey Young Dayton Children's Hospital
I haven't seen anything else posted recently so I came to add that I am experiencing some of the same weirdness with dashboards. The chart behavior described above in both a standalone dash and an object-based tab dash is the one my users have complained about the most. I've gotten them in the habit of clicking "Details" and bulk editing using that view instead of the chart but it's not ideal. However, the truncation on the horizontal and vertical both appear to be fixed for me. I've also noticed that if I have a report that pulls in images it is showing the URL instead of the image, but the same report (same user) works perfectly in Classic. Monique Evans Stanley Black & Decker, Inc.
I am avoiding the new experience for as long as I can. In the past, I've been an early adopter for new features, within Workfront and elsewhere. This unnecessary UI jumble has shaken my confidence in the product and the company. It is no more intuitive than the UI it is replacing. It increases the number of clicks for several everyday tasks. It introduces new constraints, performance issues, and glitches. Corey Young Dayton Children's Hospital
Corey, We're taking the same approach, especially since the base UI is still in flux. "New Experience" really feels like a early-stage Open Beta or some kinda of advanced stages Open Alpha. Feels a bit like video game testing I did more than a decade ago. But to be honest, from all the hype we thought it was "final" already and were all ready to start dedicating some of my time to investigating the environment. I was a bit confused when I found out it's not locked-down and "final." Sure, it was because I "assumed," but to be honest, all the hype makes it feel finalized. I can't introduce this sort of things to users and we have opted to wait until New Experience becomes a final product and has kicked-around a bit for a few months, if possible. I am following this channel because it *is* a chance to give input. Have already participated in one UI session with WF engineers about the report building UI and I found i fascinating and loved being able to help. But I'm an admin, that's more part of my job description than day-to-day users. If you look at it as an Open Beta, it's not so bad. Kevin Quosig