Rules are a cornerstone of the Verne core engine, providing a flexible means of configuring functionality to meet the myriad of business rules that a registry application must satisfy.
Rules are configured using the platform and rule configuration elements. The rule scope determines when the configured rule is called at runtime.
During execution various standard variables are passed into the rule and available for configurators to query and control. What variables are available during a rule execution is dependant on the rule scope in which it is called.
Typically rules manipulate one or more view nodes’ properties, domain data or the service transaction properties to reflect specific business rules. Some very simple examples of what a configurator might do with rules are:
- Change a view node’s visibility
- Make a portion of the view tree read-only
- Set an attribute view node’s value
- Change mandatory-ness based on another view node’s value
- Validate the attribute value of an attribute view node has a certain pattern
See the CatDocs rule configuration pages for more details around configuring rules.
