<![CDATA[Read parameter value within script]]>With NXSL it is possible to generate an output with "println" to the client.
Is there a possibility to create an input-window from an nxsl-script where an input can be requested with an individual description (value=readln("Please insert a value:")). Something like You have implemented with objecttools "InputFileds" but even generated as a result of some script-calculation.
Best regards
Georg

]]>https://forum.netxms.org/topic/7683/read-parameter-value-within-scriptRSS for NodeFri, 13 Nov 2026 09:23:01 GMTFri, 26 May 2023 12:23:11 GMT60<![CDATA[Reply to Read parameter value within script on Tue, 13 Jun 2023 15:34:58 GMT]]>You should be able to do that with object tools. Create tool that will call a script, define necessary input fields, and when user will run the tool he will be asked for additional input. This input will be available in a script.
You can even create context dashboard and add those tools as action buttons.

Best regards,
Victor

]]>https://forum.netxms.org/post/32521https://forum.netxms.org/post/32521Tue, 13 Jun 2023 15:34:58 GMT<![CDATA[Reply to Read parameter value within script on Tue, 30 May 2023 12:36:47 GMT]]>Having an environmental Control unit where it is not possible to change sensornames via webgui I want to create a form from within netxms-gui where all connected sensors are listed with theire type (temperature, humidity, leakage). Within this form user should have the possibility to name the sensors and the data should be written via SNMP-set to the unit.
For user-convinience this should be done to for all used controller-units, even if there is possibility to change these data via web.
It would bee interesting applying some other data to the sensors like warning temperatur-settings individually per sensor with the same procedure.
Best regards
Georg

]]>https://forum.netxms.org/post/32491https://forum.netxms.org/post/32491Tue, 30 May 2023 12:36:47 GMT<![CDATA[Reply to Read parameter value within script on Mon, 29 May 2023 11:22:23 GMT]]>Can you please describe use case for that? Usually NXSL scripts are non-interactive, the only place where user normally invokes NXSL script is script based object tool - but there you can use input fields.

Best regards,
Victor

]]>https://forum.netxms.org/post/32480https://forum.netxms.org/post/32480Mon, 29 May 2023 11:22:23 GMT