If the Groovy code returns
the event is triggered and the associated task is executed.
Otherwise, nothing happens.
If the Groovy code throws an exception, it is considered a coding error and the event is NOT triggered. Thus, exceptions should be properly handled in the Groovy code.
Table 32.7. Variables accessible in Groovy code
|java.util.Properties||properties||An empty container which may be filled with String-String key-value pairs in your Groovy code. It is passed to the task which may use them somehow. For example, the task execute graph passes these parameters to the executed graph.|
|java.util.Map<String, Object>||data||An empty container which may be filled with String-Object key-value pairs in your Groovy code. It is passed to the task which may use them somehow according to its implementation - e.g. the task execute graph passes it to the executed graph as dictionary entries. Note that it is not serializable, thus if the task is relying on it, it can be processed properly only on the same cluster node.|
|javax.servlet.ServletContext||servletContext||An instance of ServletContext in which CloverDX Server is running.|
|com.cloveretl.server.api.ServerFacade||serverFacade||An instance of serverFacade usable for calling CloverDX Server core features.|
|java.lang.String||sessionToken||A sessionToken needed for calling methods on the serverFacade.|