In most cases, the constraint definition is straight forward when defining a object variable. For example, if the destination IP field is empty, the GUI rendering engine will pop up an error message.
In some cases, though, the constraint is more complex and may depend on a combination of several conditions that can involve multiple variables.
For example, the 5 variables params.av, params.webfilter, params.spamfilter, params.ips, and params.scanport have the following dependencies:
- If params.av is set then params.scanport must be set
- If params.webfilter is set then params.scanport must be set
- If params.spamfilter is set then params.scanport must be set
- If params.ips is set then params.scanport is not mandatory
To make things simpler, it is possible to add a custom constraint evaluation to the object definition.
The custom constraint is implemented as a smarty template:
The evaluation of the constraint will be done when the user clicks on the "form save" button.
Once implemented, if the user sets the params.av variable but doesn't set the ScanPort, the GUI engine pops up the error:
This is one example of how complex constraints can be managed and simplified for the user.