How to run asynchronous Scripts in Industrial graphics

Unfortunately not, in InTouch it is possible to modify the global timeout for scripts, but in OMI it is a fixed timeout (5sec), I have not found a way to change this.

So it requires you to use various methods to ensure script execution when it expected to take time, dividing your logic into multiple scripts to ensure that in completes without timeout.

Hi, in Intouch and OMI , if we use OnShow or OnTrue script is that compeltely asynchronous or does it complete within the scan cycle of when its executed ? Eg:  if tag==1 was triggered at 10:AM will it complete within the scan cycle or will it go into the next scan cycle ? Also is there a way to break the script using IF conditions ?

Hi, in Intouch and OMI , if we use OnShow or OnTrue script is that compeltely asynchronous or does it complete within the scan cycle of when its executed ? Eg:  if tag==1 was triggered at 10:AM will it complete within the scan cycle or will it go into the next scan cycle ? Also is there a way to break the script using IF conditions ?

From what I have understood, script execution in Industrial Graphics are not to be compare to the scan based execution of an Automation Object in application server. But it does seem to have an internal execution cycle (sub ms), perhaps someone from Aveva could explain this better.
But the result is that it is OnTrue scripts will be executed without any delay.

And if a script triggers another datachange, it will branch out and trigger this additional script, before returning to the main script and continue execution.

I am not aware of any way to abort a script within execution.

So the problem we are facing is , OMI or Intouch Window viewer is slow because we want to do some client side scripting, now client side scripting cannot be done on Automation Objects or Linked Content. I think OMI or Window viewer uses only one core for its CPU resources and we are not able to run a script on an independent thread.

I wish AVEVA gives us this to run on an independent thread just like App objects so that the ViewEngine runtime can remain fast and not crash. This is a problem on multiple implementations where we would like to do client side scripting