About Constraints
rules
|
|
| New | Constraints | Pages & Classes | History | More... |
Create constraints rules to define and enforce comparison relationships among property values. Constraints rules can provide an automatic form of property validation every time the property's value is "touched", in addition to the validation provided by the property rule or other means.
The system evaluates constraints automatically each time a property identified in a constraints rule is changed. This technique is known as forward chaining.
No other rules explicitly reference constraints rules. When you save a constraints rule, Process Commander enforces it immediately and thereafter. The system automatically adds a message to any property that is present on the clipboard and fails a constraint. This message marks the page containing the property as invalid and ordinarily prevents the page from being saved.
Use the Policy Decisions slice (
) or Application
Explorer to access the constraints rules that apply to work
types in your application. Use the Rules by Type Explorer to
list all the constraints rules available to you.
After you complete initial development and testing, you can delegate selected constraints rules to line business managers. The Constraints tab of the Constraints form provides managers with access to the fields most often updated.
For each constraints rule in your application, consider
which business changes might require rule updates, and whether
to delegate the rule to non-developers who then can make such
updates directly. See How to build for
change.
Constraints rules are instances of the Rule-Declare-Constraints class. They are part of the Decision category.
Note the s in the rule
type. The Rule-Declare-Constraints rule type
replaces the Rule-Declare-Constraint rule type,
which is deprecated.
Home