10.8:documentation:adm:transformations

Groovy scripts

Scripts allow you to change the behavior of the application without restarting the server. Another reason to use scripts is authorization: they allow only some classes (services, managers, etc.) in scripts, see script authorization. Also, a script may call another script from within itself, by calling a special evaluator, see section scriptEvaluator.

A frontend agenda was created to simplify the use of scripts. The agenda allows basic CRUD operations (create, read, update, delete). The basic definition of a script requires a unique code and not unique name and category. As an optional attribute there is a description. We strongly recommend that you put some user description of the script in the description attribute. On creating a new script, it's allowed to add a script authorization section with authorization. The body of a script is in the Groovy language. You can find more about Groovy here.