Scripting events and execution triggers

Events and execution triggers are the basis for customizing octoplant with scripting. By linking scripts to server-side or client-side events, you can automate tasks, connect external tools, and enforce rules right when they are needed.

Event-driven scripting gives you clear control over how octoplant behaves in your workflows.

With events and execution triggers, you can:

• Integrate external tools or editors into octoplant workflows
• Automate checks, such as verifying project files before upload
• Add logic that depends on project type, file format, or component type
• Provide users with feedback or warnings at critical points
• Standardize processes by applying company-specific requirements

The following sections list the available events and explain how to use them to run scripts.

Events on the server

Server-side events run independently of clients.
Use them when you want to ensure consistent processes for all users, automate system-wide checks, or control backups and comparisons centrally.

For more detailed information, refer to Events on the server

Events on the clients

Client-side events run on the workstation where the user performs the action.
Use them to integrate local tools, give users immediate feedback, or enforce checks at the point of data entry.

For more detailed information, refer to Events on the clients