Thanks for your reply.
I figured that this was not (yet) possible, thus devised a workaround using the Grails constraints mechanisms. In case anybody runs into the same problem:
I defined a script task as first task of my process that sets a map of form property IDs to associated constraints, like this
constraints = [
someLongFormProperty: [min: 1L],
someStringFormProperty: [
inList: ['red', 'green', 'yellow']
]
]
In my application I then use a Grails command object, bind the entered form values to it, set the constraints defined in the process variable and validate the command object. This way I can leverage the power of Grails validations and still define the constraints as part of the process definition. Only thing that did not work was using custom Grails validators since they are defined as Closures which are not Serializable and thus cannot be stored as process variables.