Scripting

octoplant offers the possibility to create scripts and script applications, which are automatically executed before or after certain events. You can use these scripts to further enhance the default behaviour of the octoplant system. For example, you can use scripts to run specific projects or specific version of an editor. You can also use scripts enable work with devices, that are not completely supported by octoplant.

Scripts and scripting applications are not permanently active. Rather they are first called up when a specific event on the server or on the client occurs. For more information about which actions can be used to call up which scripts or scripting applications, see the sections Server-sided events and Client-sided events.

Scripting applications are compiled files and can be created and used independently by users.

In addition, the Scripting package provides users with a number of advantages when it comes to creating scripts:

• The scope of the scripting package includes its own interpreter. Thanks to this, you no longer have to use compiled script applications, rather you are able to execute the source code of the scripting file directly.
• The scripting package allows to create multiple scripts for the same event and to specify which script will be executed depending on the component type.
• This tutorial looks at the commands, key words, functions, and conditional assignments, which you can use in the scripts.

It is possible to use scripts via user-specified button in the UserClient. These are configurable and can be used to execute user-defined scripts. The configuration of the buttons is described at the end of this documentation.

Scripting, contact us (https://auvesy.com/en/contact).

Related Topics

• AdminClient
• UserClient
• Scripting events on the server
• Scripting events on the clients