Script limitations

• The OMI web client uses cross-platform technology to render visuals on non-Windows platform. This causes some limitation in script usage in graphics. If a client script in a graphic uses a .NET namespace that is not compatible with the .Net standard namespace, the script will not function correctly. Where possible, you may need to refactor the script to use the .Net standard namespace for proper script execution. If there is no equivalent member in the standard namespace, the script is not supported in the web client.

• OMI web client does not support the EmbedContent() function.

• The OnHide script for a graphic or layout is not triggered if you close the browser tab (or the entire browser window) where the ViewApp is running. The OnHide script is triggered correctly if you close just the graphic or layout.

• Action scripts configured to trigger while the center mouse button is down do not work. All other trigger types do work.

• SQL scripts and scripts that access the device’s file system are not supported. You may be able to work around this by moving the scripts’ logic to object scripts and bind visual elements to object attributes.

In addition, the following script methods are not fully functional when used in an OMI web client application. Click the method name to see its limitations.

HideGraphic()

ShowContent()

ShowGraphic()