So after some battle testing I found that the validation engine needed some polish as well as some 40″ spinners and one of the hula dancers you stick to your dashboard.
For those of you that are new check out the documentation in v2.0 first.
Get it on GIT
Besides fixed a few bugs we added some great new functionality as well.
V2.1 is out!
It’s been a while since I’ve posted something on my blog but it’s also been a while since I was working on something that I felt worth sharing.
I’m proud to present motoValidation v2 a big improvement to my original creation. The goal of this script is to limit the amount of code that a developer must write in order to accomplish common validation use cases in IBM BPM platform. This script is currently targeted for Heritage coaches only… I’m not sure if I like client side coaches yet… I’m sure they’ll grow on me but they need some serious stuff before I’ll consider them usable.
With motoValidation we make some assumptions:
- The most common type of validation is a required field
- The target for your validation is the same as the binding
- We should not make developers provide redundant information over and over (if I have to type tw.whatever.thing.thing.thing one more time I’m gonna snap…)
- Validation should require as little code as possible
Get it from Git