{"id":1175,"date":"2022-02-11T16:46:08","date_gmt":"2022-02-11T16:46:08","guid":{"rendered":"https:\/\/logicbuilder.integroscrm.com\/help\/?page_id=1175"},"modified":"2022-08-12T16:16:33","modified_gmt":"2022-08-12T16:16:33","slug":"on-validation","status":"publish","type":"page","link":"https:\/\/logicbuilder.integroscrm.com\/help\/on-validation\/","title":{"rendered":"On Validation"},"content":{"rendered":"\n

<\/a>Fires the flowchart before a record is saved and works directly on the form implementing validation rules. It is possible to check whether some field contains a particular value, whether a value complies with a format, or check related records to the current one. For example: check whether a Case is in an appropriate status prior to sending an email to a Client, or whether mobile phone in Lead corresponds to format, or whether parent Bug status is in an appropriate status to close related Case.<\/p>\n\n\n\n

Validation rules work in RecordView, on ListView, and subpanels in the Sugar Interface. Unlike On Data Change<\/a> or On Link Change<\/a>, On Validation doesn’t work when the record is saved on the server, e.g. through API. To implement rules for such save please see Throw Exception<\/a>.<\/p>\n\n\n\n

 Each On Validation flowchart must contain operator Add Validation Violation<\/a>.<\/p>\n\n\n

\n

After the flowchart which starts from On Validation is deployed on the Sugar instance it is necessary to clean the browser cache so that implemented rule works.<\/p>\n<\/div>\n

<\/p>\n

<\/p>\n

inputs:<\/strong><\/p>\n

<\/p>\n

<\/p>\n

select from the list a module for which records validation rule is needed.<\/p>\n

<\/p>\n

<\/p>\n