|
|
Library rulesRecords can be created in various ways. You can add a brand new record to your application or copy an existing one. Existing rules can be specialized by creating a copy into a specific ruleset, against a different class or (in some cases) with a set of circumstance definitions. Data instances may be copied but do not support specialization as they are not versioned.
Based on your use case, the Create, Save As or Specialization form is used to create the record. The number of fields and available options vary by record type. Start by familiarizing yourself with the generic layout of these forms and their common fields:
This help topic then identifies the key parts and options that are applicable to the record type you are creating.
Create a library rule by selecting Library from the Technical category.
Key parts
A library rule has two key parts:
Field |
Description |
|
Identifier |
Enter a name for this library. Begin the name with a letter and use only letters and digits. The name must be a valid Java identifier; see How to enter a Java identifier. Don't choose a name that matches a standard library, unless you intentionally plan to override functions in that standard library. Avoid using the name |
| Ruleset Name |
Select a ruleset name. A library is available to all versions of a RuleSet. However, the functions in the library may differ from RuleSet version to RuleSet version. NOTE: You can't create a new library rule in a branch RuleSet. See branch RuleSet. |
Rule resolution
When searching for library rules, the system filters candidate rules based on a requestor's RuleSet list of RuleSets (but not versions).
Time-qualified and circumstance-qualified rule resolution features are not available for library rules. The class hierarchy is not searched.
About Library rules