<![CDATA[Include Wildcard in script 'import' directive]]>I have groups of scripts, such as MIKROTIK::Update and MIKROTIK::Backup
Each script needs to be an individual script so that it can be executed from it's main(), needed for object tools.
Each script calls a global script which runs the requested scripted recursively on all matching nodes.  I do the same for WINDOWS::, LINUX::, etc.

For this to work, the global script has an import directive for each script, but there are a lot of them.

It would be really convenient if I instead of:
   import MIKROTIK::Update
   import MIKROTIK::Backup

I could rather have
  import MIKROTIK::*

]]>https://forum.netxms.org/topic/7698/include-wildcard-in-script-import-directiveRSS for NodeFri, 13 Nov 2026 10:35:19 GMTMon, 03 Jul 2023 04:28:15 GMT60<![CDATA[Reply to Include Wildcard in script 'import' directive on Fri, 15 Dec 2023 07:59:47 GMT]]>Wildcard import implemented in current development branch and will be included in release 5.0 (and 4.5 if it will be publicly released).

Best regards,
Victor

]]>https://forum.netxms.org/post/33082https://forum.netxms.org/post/33082Fri, 15 Dec 2023 07:59:47 GMT<![CDATA[Reply to Include Wildcard in script 'import' directive on Mon, 10 Jul 2023 10:54:06 GMT]]>Another option is to call functions by explicitly specifying script name. For example, if you have script

MIKROTIK::Update and function doUpdate within it, instead of doing

import MIKROTIK::Update;

doUpdate();

you can do

MIKROTIK::Update::doUpdate();

But wildcard import could be useful anyway, I agree on that.

]]>https://forum.netxms.org/post/32568https://forum.netxms.org/post/32568Mon, 10 Jul 2023 10:54:06 GMT