Server-side triggers are the most common type of trigger. When clients perform operations such as create revisions, branches, or change workspace configurations, the server can execute user scripts before and after the operation completes.

Triggers that execute before an operation allow you to cancel an operation, depending on the result code of the triggered scripts. You can also use these triggers to perform tasks automatically, such as code beautifiers.

For more information, refer to the complete list of triggers executed on the server.

Some events that occur on the client can have associated scripts or programs.

For more information, refer to the list of supported client triggers.

You can also run triggers from the Global configuration file.

To use client-side triggers, you need to deploy the triggers. If you use the Global configuration, you can place your trigger in your  repository to make it available to every user. To use the Global configuration to deploy a client side trigger, you need to use

GLOBAL_CONFIG_PATH

).