It means duplicating the form field names in the prototype list, setting the expected data types, and flagging each field as mandatory or optional.
It does not validate the validity of index values (e.g., a user ID field is actually that of a user) nor provide a callback for custom validation rules (e.g., field A and field B cannot be blank).
These types of rules must be validated directly in the request handler.
Worst of all, forms that do not validate return a jarring error page and requires the user to click the browser back button to recover.
The subclass to permit custom form validation (e.g., the password must be six characters in length, must contain both numbers and letters, etc.).Form validation is one of the weakest components of Content Server, which is surprising since forms are so vital to the user interface.Validation is usually performed by a ) prototype, which is a list of rules the request must satisfy.The framework is a component of the RHCore framework and is fully compatible with RHTemplate and RHModel.Form definitions can be inferred from your model definition and bound to an instance, which makes it easy to create forms to add and edit model data. The framework includes a number of form widgets that can be used without having to write any extra Java Script.