checks the data against metadata and, optionally, validation rules. The metadata defines the expected format for the data, such as the data type or the number of characters permitted. Customer 360 has additional validation rules such as validation of government identifiers, addresses, phones numbers, and emails addresses.
Validation processes run at the field level, section level, and record level:
Field level. When you add or edit data in a field in the
view, a client-side validation process verifies that the data satisfies the metadata. For example, when you enter a date in a Date field and then navigate away from the field, the process verifies that you entered the date in the expected date format.
Section level. When you apply all changes in a section in the
view, a client-side validation process verifies that all data satisfies the metadata and that the required fields contain data.
Record level. When you save a record in the
view, a server-side validation process verifies that data satisfies the metadata and the validation rules.
If user input does not satisfy the metadata or the validation rules, you see messages about the problems with the data.