Kind of felt like a rebuilding year. Not a whole lot of new and exciting things, keynote was pretty much the same Prism demo as last year. The SaaS propaganda was curiously absent.
There was another great one along the same “advanced ways to deal with Application Studio” theme…
@James_OToole did a session on editing the app layer json directly and updating the layer with a REST call.
It seems stuff like this is the only way to get something truly advanced done in application studio. I still wish I could just write code to get it done but at least now I feel confident that I have tactics like these to convert some of our more gnarly classic customizations.
Classic sunset at 2026.1 is firm so those of us with reluctant Classic users need to put on the pressure. We have a few here . Staying with the theme of Kinetic UI conversions, I picked up some great tips from other users / sessions to hopefully be able to make the transition easier for those users too.
This was very good. I learned from him that the published layers are in the Content column and the unpublished are kept in CHARACTER03. He then used Kinetic’s built-in Publish method to move it.
Now, he was using the GENXXX endpoint, but I wonder if one could use the Ice.LIB.MetaFXSvc with the GetApp method to retrieve the JSON:
and the SaveApp and PublishApp to persist the changes.
InportApp and ExportApp methods are also available. I can also imagine this as a VSCode extension. Heck that would allow us to use source control right there.
(For those still playing the DevOps drinking game…)
You can, be very careful with that endpoint though. You cannot have a crash. (if you are intercepting that is) Classic won’t be around to save your ass forever. (To turn off your shitty bpm lol)
I’ll have to get the slides and see what he was doing. Sounds a little like KevinWillett to me
Starting with 2026.1 development will be implementing a more CI/CD approach with upgrades, they say they will begin to push smaller feature updates instead of these big biannual releases.
Going along with CI/CD, the Epicor Test Recoder tool was pretty neat to see in action. Gunna start needing this for testing upgrades.
Wasn’t expecting to come away with anything, but I didn’t know about this checkbox that lets you rearrange your layout like the homepage and gets rid of a lot of the gaps between panels.
@Callum_Stott noted that Test Recoder is built on WebdriverIO, so you can get more information about it if you want. Here’s a comparison to a tool like PlayWright.
Thanks Mark! I had begun diving into playwright but got pulled off. I do think playwright is more robust that this Epicor offering in its current state.
FWIW, I wore my got DevOps shirt at the rehearsal of Tuesday’s Road To Manufacturing. The Epicor CIO (Arturo Buzzalino) loved it. After the concert, he said it would get some attention. I told him it’s a big idea and will need to be broken down into more manageable stories. But he seemed pretty committed to the concept nonetheless. We’ll see.