Difference between revisions of "Bypass validation"
From SmartWiki
| Line 1: | Line 1: | ||
System Administrators can create [[Submit Buttons]] for records which move the records to a different status and trigger the field validation and [[Submit Logic]] on that record. | System Administrators can create [[Submit Buttons]] for records which move the records to a different status and trigger the field validation and [[Submit Logic]] on that record. | ||
| − | The "Bypass Validation" setting on Submit Buttons allows the user to move a record to a different status without triggering the field validation. The [[Submit Logic]] on the button itself will still be validated. | + | The "Bypass Validation" setting on Submit Buttons allows the user to move a record to a different status without triggering the field validation. This includes [[JavaScript Validation]] and [[mandatory]] settings on custom fields. The [[Submit Logic]] on the button itself will still be validated. |
Using this feature, System Administrators are able to allow users to change a record back to "Draft" status, for example, without having to fill out all the mandatory fields on a record. | Using this feature, System Administrators are able to allow users to change a record back to "Draft" status, for example, without having to fill out all the mandatory fields on a record. | ||
Latest revision as of 11:11, 15 May 2014
System Administrators can create Submit Buttons for records which move the records to a different status and trigger the field validation and Submit Logic on that record.
The "Bypass Validation" setting on Submit Buttons allows the user to move a record to a different status without triggering the field validation. This includes JavaScript Validation and mandatory settings on custom fields. The Submit Logic on the button itself will still be validated.
Using this feature, System Administrators are able to allow users to change a record back to "Draft" status, for example, without having to fill out all the mandatory fields on a record.
