… you need to select the Script Type from the available ScriptEngineFactories and then enter the actual script into the editor. This action does not read script files and it does not work with rule DSL scripts.
Read through this series of tutorials, but you will be much better off using scripted automation until the UI is built out in OH 3.0…
Many thanks for the clarity , I had thought it called a script file rather than having the script embeded in the rule. I will investigate further but it would be a good way of supporting those with existing scripts if it were possible to run scripts from the /conf/script folder. Scripts could then be written with the help of Visual Studio Code for syntax etc.
Many thanks for the documentation link I had not come across this one in my search !