Interface ConstraintContextOnTable
- All Superinterfaces:
DependenciesDefinitionContext
,SchemaNodeContext
- See Also:
-
Method Summary
Modifier and TypeMethodDescriptionvoid
This method prevents, in the user interface, the constraint from being pre-validated dynamically when the related field is updated at user inputs.void
Specifies that the current constraint on table must never block operations in the repository when it adds validation errors.Methods inherited from interface com.orchestranetworks.schema.DependenciesDefinitionContext
addDependencyToInsertAndDelete, addDependencyToInsertAndDelete, addDependencyToInsertAndDeleteInOtherInstance, addDependencyToInsertAndDeleteInOtherInstance, addDependencyToInsertDeleteAndModify, addDependencyToInsertDeleteAndModify, addDependencyToInsertDeleteAndModifyInOtherInstance, addDependencyToInsertDeleteAndModifyInOtherInstance, addDependencyToInsertDeleteAndModifyInOtherInstance, addDependencyToInsertDeleteAndModifyInOtherInstance, addDependencyToModify, addDependencyToModify
Methods inherited from interface com.orchestranetworks.schema.SchemaNodeContext
addError, addError, addInfo, addMessage, addWarning, getSchemaNode
-
Method Details
-
setBlocksCommitToNever
void setBlocksCommitToNever()Specifies that the current constraint on table must never block operations in the repository when it adds validation errors.If this constraint is checkable at user inputs then in the context of the user interface this constraint will not be checked at user inputs when submitting a form. This allows to relax this constraint on table when erroneous values may be allowed when submitting a form through the user interface. If this constraint on table is checkable at user inputs it will be still checked after submitting a form if the form is valid and modified values have been comitted.
- Since:
- 5.5.0
- See Also:
-
disableAjaxPrevalidation
void disableAjaxPrevalidation()This method prevents, in the user interface, the constraint from being pre-validated dynamically when the related field is updated at user inputs. This can be useful to improve performance or to avoid unnecessary validation errors during form updates. However, the constraint will still be validated when the form is submitted or when loading the record in the view.
- Since:
- 6.2.2
-