@aosemwengie1 - I worry when there is a new release every 2 weeks.
It suggests to me that the initial QA of the big release was lacking and therefore needs patch updates frequently.
Do you find this not to be the case with Kinetic 2024.2?
We just downloaded 2024.1.17 yesterday … they keep churning out patches on a regular schedule even for the previous major release that have been out for 6 months
That’s a good question, I was going to do 2024.1.13+ as I found that people like @aosemwengie1 and others didnt’ comment on too many major issues there.
But now @aosemwengie1 is advocating for 2024.2 which is promising as many times @aosemwengie1 does not endorse recent releases due to major quality issues.
Yeah I mean, not trying to turn this thread into a but in all seriousness, this is Epicor life. All releases have 6+ months of biweekly updates, as @jwphillips said.
This, I don’t know. I’m pro-browser and thus biased of course.
So, on the one hand, are they really updating classic screens at this point anyway?
On the other hand, I guess you have little to worry about with versions if you are forgoing where all the updates are anyway (in Kinetic), right?
Classic is dead in 2026.1, in case you did not hear.
This is a very popular software practice. Companies run two week sprints that include fixes, small improvements, security enhancements, and even new features. These tasks are small and achievable as opposed to the previous large infrequent releases. This can actually make quality better since the culprit of issues is from relatively recent work. When releases were big, the coder who did the work 12 months ago may not remember the work or even work there anymore. Browsers release work continuously. There are other properties that might say something about quality, but releases are not one of them.
I feel like I have to reply to this now since you tagged me lol. There are huge improvements in 2024.2. For example design for ssrs finally works. System monitor finally displays all tasks. Grids are getting better. Just overall stability is improved. We have been working on it for several months now and I don’t have any complaints about 2024.2 that I don’t also have about about 2024.1 so I wouldn’t see the point in staying back.
Thank you, I was worried it was broken in 2024.2. Turns out there is a setting in employee that must be checked to allow for reporting scrap quantity on the production info tab.
The longer it goes, the more you’re missing out on that doesn’t exist in Classic. Nothing that they’ve introduced for at least a year now–maybe two–I think, is being added to the Classic. So you could be voluntarily hampering yourself by not converting at least some sooner.
I mean, I love Classic, I hate change, I may not be old enough to retire yet but I am already working on the front porch and rocking chair so that when I do get a cane I can sit out front and yell at the younglings to get off my lawn but I have to say, sticking with Classic and not even beginning the process of converting your users over is IMO a bad idea.
It is going away, no matter how much functionality Epicor has kneecapped in Kinetic, that is a fact. Waiting until you no longer have a choice means that you are giving up control on this for your business and again, IMO, that is a resume generating event.
We are rolling out 2024.1 over Christmas and during that all non-MES users will move to the Browser version. All screens that are not dashboards have been customized to try and have their functionality as smoothed out as possible while some of the severe limitations with dashboards mean we will suffer through launching in Classic mode for those. Eventually we will have to accept that those too will need to be Kinetic even though grid filters are next to useless in Kinetic and Row/Field coloring essentially violates the ADA & AODA laws we are required to abide by but there is not much I can do about that.
I’ve heard this argument but haven’t heard anything they’ve actually added. Any chance you could list some as currently upper management has no intention to continue upgrading as switching to browser based will hamper a lot of functionality that we’ve created, and I can’t honestly think of anything that we’re actually missing out on.