Looking forward to hearing @timshuwy on the What’s New Release 2025.1 of Kinetic in a few…
Woot!
6 Likes
They have emojis on the stream, and they float up the page lol.
I noticed they left off 
6 Likes
There was a ton of “wow” faces there on this one.
1 Like
It’s not a new announcement. But a big deal.
1 Like
I see that from a company perspective.
We went live in September of 2024, and we pushed all of our consultants to work Kinetic in the Browser Client only - they were initially a little resistant. Turns out this was a very good move for us…
I wish all those moving toward this godspeed… the good news is that all of Epicor’s resources will now not be split off in multiple directions for fixes/updates/requests…
4 Likes
Spring 2023 for us - probably 95% of the work’s being done in the browser already. A couple of tasks from a performance standpoint just go easier with the client and we’re using Citrix for those few users. Including me because BAQs are easier to maintain there. 
Concerned about the power tools being ready for primetime that’ll address DMT and the other client-centric items.
3 Likes
@timshuwy said that Power Tools will come with 2025.2.
13 Likes
This was in the Questions Block about it:
Question:
Just to clarify, everything in the browser except Power Tools?
Answer:
Correct. I forgot to mention Powertools. Powertools will include Epicor Functions, DMT, and Advance Print Routing. Powertools will have an initial release with Kinetic 2025.2
4 Likes
@timshuwy Appreciate your clarity and expertise! Thanks for the updates…
1 Like
Understood…so hopefully by 2026.1 they’re ready to rock. We’re lucky as semi-n00bs that we’ve been largely browser-based since the beginning…and can sympathize with those that have been client-based…especially if they’re running a non-vanilla environment.
2 Likes
That’s a really big deal, gives us a chance to confirm sustainability of those tools in our use cases. I’d rather see it turning up a year in advance, but 2025.2 is an improvement.
5 Likes
Powertools seems to be a significant concern to many, but in reality it is one of the simple things that we are doing. We are splitting out APR and Functions and DMT and all the pieces needed to run them into their own “powertools” menu application. This will be a separate install if desired from the smart client (althought at 2025.2 the smart client install will also have these tools). Since powertools has minimal development except for the new login/menu, it should be very easy to test and get right. The dev team is confident that 2025.2 will run it well.
4 Likes
I missed the webinar so apologies if this was answered, but what exactly is Powertools under the hood? Is it browser based, Winforms desktop application, or something else?
Powertools will be a windows application that will NOT run in a browser. its sole purpose is to provide all the services necessary to run DMT, Advanced Print Routing setup, and Epicor Functions editing. you will also need to install powertools if you are using Service Connect.
If a user does none of these things, they dont need the powertools. it is solely for administrators.
6 Likes
Thanks. So it sounds like it’s mostly a copy/paste of the existing classic programs wrapped into a new application? That makes me more optimistic it will be solid in the first release.
1 Like
You’re in luck, they just released the recording.
What’s New in Release 2025.1 of Kinetic: Preparing for Your Upgrade
4 Likes
Hopefully! 
2 Likes
That’s what I’ve been assuming too - that Power Tools will really just be the legacy desktop smart client, pared down to the bits that didn’t make the browser MVP release.
If I’m assuming correctly it makes sense that the power tools will not be a high stress or risk issue for Epicor. For us on the user end, these features bear a ‘functional’ scale of cost of risk, and that’s what would be the driving factor in frustrated communication. Trivial to execute or not, we really really really need assurance that these things won’t disrupt our ability to do business in May 2026.
1 Like
Well, DMT would need to be integrated, or was that done in 2024.2?