On our portal, I recently noticed the "Enable Test Script" option under the UIv4 security section, because UIv4 recommended I toggle it from Enabled to Disabled. I avoid UIv4 like the plague but as LM forces it on us more and more, I end up having to use it more and more. Maybe in this one case it was a good thing because I wasnt aware about the toggle.I even reached out to LM and the person who helped me provided a lot of good information but had to look into it himself in terms of sharing docu...

Modules toolbox has come a long way, but that's not saying much. It's got a long way to go. My opinion: Actions that aren't associated with editing the module shouldn't be exclusively in the editor. LM has made the decision to have a "viewer" and an "editor". If they persist in this, they should put things like "show associated devices", "test appliesto", "test active discovery", and "test collection" in the viewer as well as the editor. They do not change the DS, so they don't need to be locked...

"Enable Test Script" UIv4 security experiences? | Product Discussions

Discussions

"Enable Test Script" UIv4 security experiences? | Product Discussions | LogicMonitor Community