In most cases, the modified data tag is pre-set to no when the program presents the form to the user; then, if the user changes the data in the form item, the modified data tag is set to yes, and your program logic can do as follows:
The user sets the modified data tag by typing a character in the item or by deleting a character. The modified data tag stays set, even if the user, before submitting the form, returns the field content to the value that was presented.
When a form is re-displayed due to an error, the form is still processing the same converse statement. As a result, any fields that were modified on the converse have the modified data tag set to yes when the form is re-displayed. For example, if data is entered into a field that has a validator function, the function can invoke the sysLib.validationFailed function to set an error message and cause the form to re-display. In this case, when an action key is pressed, the validator function will execute again because the field's modified data tag is still set to yes.
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.