Did this give you what you needed Chris?
It lets us do what we need to do, I was asking more if there is a way to define these at a form level, without having to upload a library as a shared resource.
Ah, ok, I assumed that when you uploaded a library to the component it would go to a shared library. I've had a play now and I can see it on the form's resources tab, with the option to publish to another library.
This is perfect, thanks Ben.
Although I can add it to a page, it just doesn't seem right that it should go there.
The context for my comment is the scenario where I have some logic in a visibility rule for a block in a form and then I realise I'm duplicating it in another block and maybe a third. It would be handy to on the spot create a function (within the Maestro editor) that they can all call without the overhead of creating and maintaining a library and potential version problems.