...
The next phase is to submit the PTAEO to the webmethods PTAEO validator. Bill is working on doing a quick demo / mockup of the variables we can send to the WSDL via the mid-server.
What
Next we need to either silently accept the value, or perhaps provide a visual cue that the value is accepted. Perhaps turn the field green.
If the the value is bad, we need to provide some form of notification of the mistake. This functionality is already built-into the webmethods WSDL; it's passed along as a text error message. The simplest notification would be a popup with the content of the WSDL complaint passed-through. Nicer would be some color or syntax highlighting.
When
I envision this validation to be controlled by Client Scripts. I think that onChange we should fire the validator. If we try it and it seems dumb, we can try a different tack.
We definitely need to validate onSubmit, and we should prevent/interrupt the submit from completing if the data is denied.