a!dateField - How to clear the dateField if I enter wrong format date. By default appian says "the value ..... is not a valid date. Valid format is ....". Even without value and saveInto the wrong format value is saved in the field.

Hi Vijay, AFAIK this is expected behaviour of Appian.
If you enter the wrong value, the default Appian's validation functionality will get triggered and won't let your code to go further unless you correct the same. It will retain the value and will show with a red mark on it. If doesn't retain the value, displaying the validation message alone won't make any sense.
And your second point is pretty clear, you have entered the correct value there won't be any validations to occur but it won't retain the value if there are no respective properties configured on that field's respective SAIL Component.

From the technical point of view, this is correct poorna. But from a user prospective in a dynamic form, user may going back and forth the value is not cleared out. User does not feel this is good intuitive design. Appin might have handled cleared out the value from object and displaying the user entered wrong date along with the validation message

From the technical point of view, this is correct poorna. But from a user prospective in a dynamic form, user may going back and forth the value is not cleared out. User does not feel this is good intuitive design. Appin might have handled cleared out the value from object and displaying the user entered wrong date along with the validation message

In such kind of Dynamic scenarios, we will definitely be configuring the value and saveInto parameters to the respective SAIL components, to persist the value, instead of avoiding them during configuration.
1. With Appian's default validation behaviour we can achieve the basic validation on the field
2. If you have a custom validation that can be achieved by defining validation rules
3. Finally, a value can be valid while entering and may be invalid after sometime in future, this can also be achieved and so the user can see the previous value he entered in the dateField with a validation message that we configure using the custom validations on the field.
In all of the above scenarios, configuring the value and saveInto parameters is obvious!!