Records can be created in various ways. You can add a new record to your application or copy an existing one. You can specialize existing rules by creating a copy in a specific ruleset, against a different class or (in some cases) with a set of circumstance definitions. You can copy data instances but they do not support specialization because they are not versioned.
Based on your use case, you use the Create, Save As, or Specialization form to create the record. The number of fields and available options varies by record type. Start by familiarizing yourself with the generic layout of these forms and their common fields:
This information identifies the key parts and options that apply to the record type that you are creating.
Create an association rule by selecting Association from the SysAdmin category.
An association rule has two key parts:
Field |
Description |
|
Apply to |
Select a class that this Association rule applies to. The list of available class names depends on the ruleset you select. Each class can restrict applying rules to an explicit set of rulesets as specified on the Advanced tab of the class form. |
|
Identifier |
Select a prefix for this association rule. Start with a letter and use only letters and digits. Use a short but meaningful prefix for each association that correctly describes the relationship between the classes, because association names are used to prefix property names in the Report Viewer and the report definition rule form. Do not enter a prefix that is an SQL reserved word, such as SELECT, ORDER, or JOIN. |
When searching for rules of this type, the system:
Time-qualified and circumstance-qualified rule resolution features are not available for this rule type.