Backeberg got PTAEO validation working with a single-line PTAEO form.

But really we wanted the fix five box form design that people were used to from START.

...

FRU0013856 is where that work is happening.

Possible bug. When validating round Three, Backeberg found that changing Award to a bad value, and then changing it back doesn't seem to work properly. If you change a character to an invalid value, the PTAEO gets marked invalid as it should. If you put it back to a good value, that should fix it again, but instead the bad value seems to be sticking. I haven't reported this back to Fruition because I found a separate, more obvious bug and I instructed them to fix that first.

There were two bugs, both now resolved:
1) the return information from the ptaeo validator (valid, or invalid with error message)
2) there was a problem where entering lower case characters as part of a valid ptaeo would be marked invalid, because they were submitted to the validator before being auto-capitalized.

***Changes captured in Update Set: 2013/03/08 - 1 ***

Round two

In Round Two, Backeberg was astonished at how many variables were required to get some javascript validation working, and also to get all of the form backend moved into variable sets. And to split the work into three variable sets: one for recurring, one for initial, one for both.

FRU0013779 was for adding javascript simple validation (capitalization and turning into variable sets).

***Changes captured in Update Set: 2013/03/31 - 1 ***
***Changes captured in Update Set: 2013/03/01 - 1 ***

Round one

In Round One, we wanted Fruition to confirm it was possible to get five parallel boxes to appear side by side on a single row, and behave properly.

...