JSON Composer validation rules

By default, the JSON Composer uses strict validation, and the job fails if a violation occurs. To customize validation, specify the action to perform when a violation occurs.

The following tables describe the validation rules and the applicable actions.

Table 1. Value validation rules
Rule	Description	Actions
Data type has illegal value	The value must conform to the value rules for the data type of the corresponding item.	Ignore Type checking is not performed. The data types of the items in the Target column of the mapping table are replaced with the String data type. Log per Occurrence; Log once per Document Log per occurrence logs error for each occurrence and the log once per document logs error for the first occurrence of all errors of the entire document. Fatal (Default) Type checking is performed. An invalid value causes the job to fail.
Item that cannot be null has a null value	Items that cannot be null are checked to ensure that they do not contain null values.	Ignore Null checking is not performed. All items in the Target column of the mapping table become nullable. Log per Occurrence; Log once per Document Null checking is performed, and errors are logged. Null values are set. As a result, all items in the Target column of the mapping table become nullable. Fatal (Default) Null checking is performed. An invalid value causes the job to fail.
Trim values	Trim the white space before and after a value before performing type checking and type conversion.	False Trimming is not performed. True (Default) Trimming is performed on both sides of the value.