If the Groovy code returns Boolean.TRUE, 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 24.7. Variables accessible in Groovy code
| type | key | description |
|---|---|---|
| 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. I.e. 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 - i.e. 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 | instance of ServletContext in which CloverETL Server is running |
| com.cloveretl.server.api.ServerFacade | serverFacade | instance of serverFacade usable for calling CloverETL Server core features. |
| java.lang.String | sessionToken | sessionToken, needed for calling methods on the serverFacade |