WAS CHANGED evaluation

crisg0112

Hi,

does AwareIM only evaluates WAS CHANGED when the user 'tabs' or goes to the next attribute on the form? Is there a way to check if the value was changed even if the user stays on the attribute he/she just modified?

The reason is that a user might fill up a form that conforms 100% to all the business rules and then prior to clicking the <SUBMIT> button, goes back and changes one attribute. The user then just clicks on the <SUBMIT> button and the context is still holding the 'old (valid) values' instead of the 'changed (invalid) values'.

BenHayat

crisg0112 wrote
Hi,

does AwareIM only evaluates WAS CHANGED when the user 'tabs' or goes to the next attribute on the form? Is there a way to check if the value was changed even if the user stays on the attribute he/she just modified?

The reason is that a user might fill up a form that conforms 100% to all the business rules and then prior to clicking the <SUBMIT> button, goes back and changes one attribute. The user then just clicks on the <SUBMIT> button and the context is still holding the 'old (valid) values' instead of the 'changed (invalid) values'.

Cris, I have seen this problem with many products over the years, because the Ajax part would become too chatty to send to server for each character typed/sent. It's not an Aware issue.

crisg0112

BenHayat wrote
crisg0112 wrote
Hi,

does AwareIM only evaluates WAS CHANGED when the user 'tabs' or goes to the next attribute on the form? Is there a way to check if the value was changed even if the user stays on the attribute he/she just modified?

The reason is that a user might fill up a form that conforms 100% to all the business rules and then prior to clicking the <SUBMIT> button, goes back and changes one attribute. The user then just clicks on the <SUBMIT> button and the context is still holding the 'old (valid) values' instead of the 'changed (invalid) values'.

Cris, I have seen this problem with many products over the years, because the Ajax part would become too chatty to send to server for each character typed/sent. It's not an Aware issue.

Thanks Ben. How did you overcame this issue? Is there a way to force the update prior to clicking the <SUBMIT>? Forgot to mention that I am using an AwareApp.startProcessFromForm with save flag set to true already.

BenHayat

crisg0112 wrote
BenHayat wrote
crisg0112 wrote
Hi,

does AwareIM only evaluates WAS CHANGED when the user 'tabs' or goes to the next attribute on the form? Is there a way to check if the value was changed even if the user stays on the attribute he/she just modified?

The reason is that a user might fill up a form that conforms 100% to all the business rules and then prior to clicking the <SUBMIT> button, goes back and changes one attribute. The user then just clicks on the <SUBMIT> button and the context is still holding the 'old (valid) values' instead of the 'changed (invalid) values'.

Cris, I have seen this problem with many products over the years, because the Ajax part would become too chatty to send to server for each character typed/sent. It's not an Aware issue.

Thanks Ben. How did you overcame this issue? Is there a way to force the update prior to clicking the <SUBMIT>? Forgot to mention that I am using an AwareApp.startProcessFromForm with save flag set to true already.

I did not overcome that problem. Most of server side systems, that's how they work.

crisg0112

Thanks Ben !