Classic Screens Sunset announcement

MODERATOR NOTE:

This thread was started with incomplete information due to a partner releasing details ahead of schedule. To ensure our discussions are based on accurate and official information, we’re temporarily closing this thread until Epicor releases the formal announcement. This upcoming announcement will provide more comprehensive information, facts, and guidelines.

Speculating on what is or isn’t happening won’t help until we have the facts. Once the official customer announcement from Epicor is released, we can re-engage in conversation I am sure we have lots of opinions and questions on this.

In the meantime, I’ve marked @timshuwy’s reply as the solution for now.

Thank you for your patience and understanding.

See:


OP:

One of the partners just shot out an email on this.

Classic is Sunset as of 2026.1

Mod: link to partner video removed

10 Likes

@timshuwy Wasn’t there going to be a 1 year warning? Pardon, misread it.

2 Likes

Isn’t it a one year warning? 2026.1 we are not on 2025.1??

1 Like

Sorry, misread I guess :laughing:

2 Likes

November 2024 → May 2026 is over a year.

4 Likes

I think he means officially from Epicor, not a partner announcement

1 Like

The video IS from Epicor, by an Epicor employee (Cristine Hansen), but hosted on a partner site.

4 Likes

Nah I think I just got confused by looking at this too fast, it skips 2025

1 Like

maybe they’re skipping 2025 as a release year?

that’d give them an extra year to tighten things up for the first browser-only release

2 Likes

How come all customers didn’t receive this announcement video is the bigger question :laughing:

6 Likes

viral marketing

3 Likes

They say in the video that the all customer version will be going out next week with the production release of 2024.2.

4 Likes

I’m not sure @klincecum would survive if they made him switch from classic function maintenance to a browser version without some time to play with it first.

5 Likes

I think @timshuwy has been open with us on the classic sunset. It was fair to assume one year from next insights (2026.1) was the plan.

8 Likes

Really need to refine BAQ/BPM/Function studio tools before browser only :sob: . There are some ideas out there to improve them. I’ll campaign for them in the Frideas thread.

6 Likes

It’ll be interesting to see how it goes. We’re virtually 100% browser as it is…only a few things that are client-only (and that’s going through a Citrix/RDP deal, no local user installs)…and a fairly limited amount of BPMs and such.

I’m new enough to Kinetic that I’ve only used the browser for regular BAQs and most BPM. My biggest complaint about the BPM designer is that it seems to not save if you try to save multiple new steps at once, so I have to remind myself to save every change.

The 2024.2 update adds UBAQs to the browser BAQ designer which looks a little more user friendly than the classic, although I’ve only glanced at it so far.

2 Likes

We’re thinking about doing an upgrade…I’d think we’d look to 2024.2.# as the next step from 2023.2.11…but it’s very early in the game.

1 Like

Probably not the FIRST word I’d use to describe it, but it fits…

2 Likes

I’m just glad we know what the timelines are.

May 2026 seems a reasonable amount of time to sort things (we’re aiming for Q2-2025), but I’m glad to have year to iron out any issues.

Hit one today on 2024.1 where a dashboard runs in classic, the baq runs as a tile on the home page -but the dashboard returns no data and the server log says it’s an invalid column name - absolutely no idea what is going on.

A year to sort these types of issues seems ok.

I really like App Studio, it is not a finished product by any means.

18 months will not only focus the customers, but hopefully also the Epicor development team.

1 Like