Good news, bad news
Good news, we passed most of the validations cited above.
More good news: DataAssist appears to be doing exactly what I told it to.
I did check code placement, to me it looks like the Insert Record behavior is occurring after the server validation.
Bad news: The unique database values validation failed. I put my email address in as the test guppie and it entered the duplicate value into the data base. I would have expected to reload the Registration page with the Show If condition stating duplicate email address to be the next thing that I saw. Some more good news is were still in development and Im the only one finding this stuff.
I did not test the second unique value field because so far, my test was the first entry into that field.
I would have expected the cycle to be stopped when the Email validation failed, is there something that I need to add to stop this cycle when the validation fails? I see SecAssist 2 adds a URL parameter in the go to page; do I to add that?
Thanks for the quick response, it is appreciated.