administrators

The legacy UI definitely has issues with multiple tabs/windows. I'll be looking into the issue with the Modbus tools today. Thanks for letting us know.

@mattfox said in Release Notes for Mango 3.6.0:

I saw the release video, most impressed. Nicely done all!

Thanks, this is the video for anyone who wants a quick 5 minute overview of the new features

Hi ppaniceres, welcome to the forum!

There's a simple example of writing to a file from a script within Mango in this thread: https://forum.infiniteautomation.com/topic/4208/creating-files-in-filestore-from-excel-post-process-script

I would probably do this with a scripting data source on a cron like 0 * * * * ?

Yes, would be quite simple with an event handler script.

Hi Mista, welcome to the forum

That has certainly been fixed in later versions to output more than null. I don't recall exactly what the issue there was, but you can perhaps check your browser's network tab and see what the response from the Dwr is, which may show the actual compilation results or error.

Actually BACnet4J uses Simple Logging Facade for Java (SLF4J) https://www.slf4j.org. In Mango we use the Log4J binding and configure BACnet4Js logging via Log4J.

However if you are only using BACnet4J with no additional logging library you can configure the SLF4J loggers by including a binding. Some bindings require configuration but if you just want to discard all logging messages place the NOP binding on your class path.

See this link https://www.slf4j.org/manual.html#swapping for the various bindings you can choose, all you need to do then is put 1 of these bindings on your class path and configure it if the binding requires it.

Hi YEZI,

This would be in your log4j configuration, which in Mango would likely be located at either Mango/overrides/classes/log4j2.xml or Mango/classes/log4j2.xml

You can reload the log4j settings at the /ui/administration/log4j-reset page from within Mango after you've modified the appropriate XML file's list of packages and log levels (near the bottom of the XML file)

In 3.6 security was added to scripts to ensure that only a script with superadmin permissions could invoke Java code. That's probably what you're seeing.

As the update event of the meta data point.

Certainly!

Do you mean that you tried it on the beta and it didn't work or you're saying that you're not using the beta and it still works? It should work for lots of older versions and still in future versions, as the post about the events email is a year and a half old at least.