Classic -> New Experience Nightmare | Community
Skip to main content
N
NRYNR
Level 10
August 11, 2021
Question

Classic -> New Experience Nightmare

  • August 11, 2021
  • 14 replies
  • 6740 views

I was losing sleep over this six months ago when I tested things, but had hopes the experience would have improved. After some testing, we're finding that New Experience pages load 5-6 times slower than in Classic. Try to CTRL+ CLICK an open more than one tab at a time and things get even slower. We've all become quite accustomed to pages loading quickly when popping out into new tabs. But speed isn't the only problem. I'm also getting trapped in iFrame hell where the focus of the cursor is constantly grabbed by each report on the dashboards we use. So getting to that last report at the end of the dashboard is quite an interesting ride. We also use the "Allow embedding of Workfront in an Iframe" feature, which still loads Workfront in Classic for some reason. Perhaps things are better for the users with super high-speed fiber internet connections, but a huge part of our work force is remote with varying internet speeds. However, Classic is fine even when in the most remote places with just a single bar on a Verizon MIFI.

So what gives? Now that Workfront is an Adobe product, perhaps it's time to reconsider kicking Classic to the curb. There's not one feature we NEED in New Experience, yet we're seemingly being forced to use it because of all the features customers WANT.

Is anyone else dreading the day they have to move everyone over? For those of you who have already switched, do users simply normalize working at a much slower pace? Is leadership okay with productivity declining? Am I the only one who finds the experience to be a complete disaster?

  • Dashboards ~25 Seconds to Load vs. 5 seconds in classic
  • Dashboards - Every report is an iframe with scroll bars, grabbing the focus of the cursor if there's a pause resulting in endless scrolling.
  • Issue ~30 Seconds to load instead of < 5 seconds in classic.
  • Program ~20 Seconds to load
  • Project ~30 Seconds to load instead of < 5 seconds in classic.
  • Task ~20 Seconds to load overview instead of < 5 seconds in classic
  • iFrame - When loading Workfront in an iFrame, it still loads in Classic... confusing.
  • Custom Forms Report - We're no longer able to edit forms from a report. Once edit is clicked, navigation takes us to Setup, a huge productivity killer for a team of >5 editing forms all day long.
    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    14 replies

    K
    KellieGa1
    Level 2
    August 11, 2021

    I've noticed the same thing. Sometimes I have to refresh report pages 4-5 times before they actually load.

      J
      Adobe Employee
      jbostonAdobe Employee
      Adobe Employee
      August 11, 2021

      Hi Narayan, thank you for your feedback. The experience you and your users are having is a high priority for us, and we consider each piece of feedback deeply and thoughtfully. No customer should be losing sleep over this, and if you are, let's chat about some of the improvements we're already making and some of your feedback in more detail. Some of what you mentioned regarding iFrames is already being addressed as part of a top initiative.

      For the performance numbers you are seeing, this is indicative of an issue that needs further investigation with our Support team. As you suggested, those extremely high page loads are most likely due to network requests being blocked, and we would like to investigate further the specific configuration in your instance. As a best next action, we will have your CSM and account executive reach out to you on this topic.

        N
        NRYNRAuthor
        Level 10
        August 12, 2021

        Well Josh, I'm actually more interested in hearing from other customers on this topic, which is why I posted to the community instead of Support or a CSM.

        Doesn't this all boil down to the cost of maintaining and supporting Classic? Doesn't Adobe have some extra cash laying around that they can fork over to at least delay this until the issues are fully sorted out? I'm only interested in helping you all arrive at the right thing to do for the customer.

        MikeHa1
        MikeHa1
        Level 3
        August 12, 2021

        I have been experiencing similar lag times. I had actually put in a support ticket, but there was no resolution form it. The delay/lag times seem to be intermittent..

        K
        KevinQu1
        Level 10
        August 12, 2021

        @NRYN R - inactive‚, I've had the same general experience as you and @Mike Haleas‚. Ticket gave vague "we know, we're working on it." Other posts to the community boil down to "your IT must be blocking something."

        Except…my IT is always telling me that WF is not following industry practices (email notifications are a big one here) and is just expecting too many concessions. So I haven't even considered chasing-down that ghost; it will be long and tedious and alot of finger-pointing. It will involve diving into the weeds since we've done all the documented whitelisting. If it's IT-related, it's going to be some minutia of settings that WF will say to change but IT cannot or will not because of security or knock-on effects.

        Personally, I wonder if the code is too bloated and simply causing drag on the page loads, and WF can't see it because their test environment is too ideal (fast inter/intranet, local servers, fast computers, etc.).

        *shrug*

        J
        JillAc
        Level 10
        August 12, 2021

        I'm going to jump in on this too. Definitely slower page loads across the board, but also equally frustrating are pages that don't reload at all -- in Classic when you switched from Scheduling tab to Tasks (for example) the Tasks would refresh, and now you have to manually refresh to see the changes to the schedule that you made.

        RandyRoberts
        Community Advisor
        RandyRobertsCommunity Advisor
        Community Advisor
        August 12, 2021

        NWE is a beta pet project at best. Definitely not ready for prime time. I've been complaining about the latency and plain old load failures for some time.

        I was told to open a ticket, haha. Like my support rep could actually do something about it.

        Very disappointing.

        J
        JohnWe16
        Level 2
        August 12, 2021

        We are experiencing the same performance issues since we started using the new experience. Lag times have definitely increased. I agree with Mike. They are intermittent. Lately its been bad.

        ChrisBudgen
        ChrisBudgen
        Level 5
        August 16, 2021

        Same here, we have roughly 1k users and have started with a POC, the feedback was: better design, super slow (especially if you have more than 100 items in a list and some calculated columns) and there are a lot of inconsistencies within NWE. E.g. the user edit and create modals are still Classic, filter/view/grouping selections have a different UI depending on the object, ...

        N
        NRYNRAuthor
        Level 10
        August 16, 2021

        A common suggestion is to reference an existing ticket when there is a larger problem at hand. A ticket has been raised expressing Truist's inability to migrate to New Experience at this time. You can reference the case at https://one.workfront.com/s/case/5004X00001aSAWkQAO/new-experience-migration-plans-failed to help Adobe Workfront Support better understand the scope of the problem.

        M
        ManuelBa
        Level 4
        August 17, 2021

        The very slow NWE has been discussed several times here in the forum; combined with the numbers provided by @NRYN R - inactive‚ I‚Äòd say we can call it a fact that it is considerably slow and annoying for anyone using Workfront regularly. I resign from creating support tickets here as it’s a waste of time.

        Regarding the inconsistency of NWE and Classic: I have the impression we got rid of occasionally seeing the classic one after we entirely and irreversibly switched to the NWE (‚Äî> support ticket). Thus, the issue seems to be a result of the hybrid situation. Please be aware that we didn’t manage to migrate layout templates and created new ones for the NWE.

        N
        NRYNRAuthor
        Level 10
        August 17, 2021

        It's a One that needs to be flipped back to a zero. It can be done. it should be done. But will it be done? Ooh the suspense. Tick Tock...Tick Tock...

        M
        ManuelBa
        Level 4
        August 17, 2021

        After a lot of bad news, a small consolation: our users like the NWE design better…

          TamBou
          TamBou
          Level 5
          October 6, 2021

          Ditto, thus far

          K
          KellyFo
          Level 3
          August 18, 2021

          Hey folx - I have complete empathy by anyone experiencing slow loading speeds whether it is in WF or any page on the internet in general. But, I feel like WF clearly and regularly communicated the upcoming transition to NWE and the pending decommission of Classic well over a year ago. It is just not feasible for any company to support all the previous versions of their product. If so, I know some people who would still be carrying around an iPhone 5 and complaining how slow and incompatible it is with newer apps.

          I do wonder if some people are experiencing slower load speeds due to using Classic and NWE at the same time, and I also wonder if a clean sweep of their instance might be needed? Possibly purging unneeded objects could help the situation.

          Christina_Jarosz
          Christina_Jarosz
          Level 9
          August 18, 2021

          Kelly - this was one of the first things we tried - purging the classic from our instance since we are all on NWE and it's no success. The load time is still agonizingly slow.

          Show more replies
          Terms & ConditionsAccessibility statement

          Loading footer...