I have a UD menu item to run a customized kinetic version of order entry. As far as I can tell the menu item only ever launches in kinetic. But activity tracking has two records every time this screen is launched, one says classic and one says metaui. I don’t know if this is a bug in activity tracking? Something to do with UD menu items? We are trying to use this to figure out who is still using classic forms so its not very useful if it tells me they are using classic if they aren’t.
Is anybody else seeing this in their activity tracking?
So this is entirely reproducible. I can’t tell if its a bug or working as designed because I can’t even get support to understand the question
If you create a new menu item as a Kinetic App.
Launching it from the browser: You get MetaUI in key 2(correct) and Desktop in key 3 (um what?)
Launching it from the client: You get Classic in key 2 (NOOOOOO) and blank in key 3 (why?)
Is there somebody on this board that can explain how activity tracking is supposed to work? @timshuwy
I WANT to be able to clearly see who is using kinetic and who is using classic. This completely blows that up because it is capturing a value of classic instead of metaui when the user is, in fact, using the kinetic interface.
@aosemwengie1 , could it be that the blank in Key3 is what tells you what they are using? If someone opens up a classic screen, is Key3 blank for MetaUI?
Not sure I understand what you are saying but from what I can tell, all my menus that are hardcoded to classic get correctly noted as Key2=classic when launched (and key 3 is blank).
I’m just speculating. But it looks like both records get created no matter what you open. I’m wondering if Key3 only gets populated when you launch a browser version. So, if Key3 is not populated for MetaUI, that would mean that they opened Classic?
That is what I thought originally, but I just did a clean test and its not creating two records with each launch, its only creating the single records I listed out above.
