We’re planning on making some progress moving departments to Kinetic UI early next year. Our preferred method is to move one department at a time, starting with our engineering staff. What strategies have others used to manage this process? Currently, most users share the same menu structure. I had considered using this as an opportunity to finally break out each department’s menu items into separate structures. This would allow me to enable Kinetic on a per menu item/structure basis. My issue with this method is how to handle Open With. If I enable to Kinetic for a department’s structure, how to ensure their Open With menus only link to Kinetic menu items, without impacting other departments?
Which if you set it to Kinetic it will default all forms for that user to Kinetic (if it can). Another easier way to do this is to move those departments to the Browser.
So remove Epicor Client and move them fully to the browser that way there’s no accidental launching of Classic.
Perhaps I was thinking about this the wrong way. I had assumed that I would be changing individual menu items to open in Kinetic, so users didn’t have a way to revert. That’s where I was getting hung up with context menu maintenance, since those entries link to specific menu IDs; how do I ensure that users who aren’t part of a migrated department get non-Kinetic entries.
You’re probably right, simply uninstalling the client and forcing browser use would solve it. My biggest fear with that method is that there would no longer be an option for classic form use if through this process we find that a few are still necessary.
Word of caution - if you’re going to start off deploying Kinetic to engineering, be aware of a serious Method Tracker issue that was supposed to be fixed in 2022.2 and wasn’t, and is now scheduled for 2023.1 next year. PRB0255458. The only workaround is to use Classic.
Right, these were the sort of issues why managing a dedicated menu structure for engineering was attractive. If we discover serious issues that force classic form use, I can just toggle the menu item for everybody instead of expecting them to toggle form specific Kinetic/Classic preferences.
Absolutely - our issue is we were sold Kinetic as a finished product, so we planned on starting everyone out on the web. Once we got into implementation, we quickly became unpaid beta testers and Kinetic-only went out the window.
