Entity Validation
They take account of the data type from the underlying entity to give you the simplest level of client-side validation. This is not a security feature but assistance to the user when entering data, to notify them if they have entered either the wrong type of data or have left the input field empty.
As your application develops, you will almost certainly need additional input validation depending on your applications requirements. For example, you might want to validate a string field to be a valid credit card. This is achieved with custom formatters specified at the entity level and is described in a later section. The built-in validation covers you for simple cases.
input-form example
- See what happens when you input data with each type of input field.
- Notice that the data changes when you move focus from an input field.
- Try entering different or no values and seeing when the validations notify you of invalid input.
- Notice that you can back out of an edit with the Escape key on your keyboard.
Taking some time to familiarize yourself with the workings of the AutoForm now will lead to fewer surprises when you develop more complex input forms and will help you field questions from the end users of your application.
© 2001-2019 Fair Isaac Corporation. All rights reserved. This documentation is the property of Fair Isaac Corporation (“FICO”). Receipt or possession of this documentation does not convey rights to disclose, reproduce, make derivative works, use, or allow others to use it except solely for internal evaluation purposes to determine whether to purchase a license to the software described in this documentation, or as otherwise set forth in a written software license agreement between you and FICO (or a FICO affiliate). Use of this documentation and the software described in it must conform strictly to the foregoing permitted uses, and no other use is permitted.