Product rules
|
|
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 may copy data instances but they 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 information identifies the key parts and options that are applicable to the record type you are creating.
Create a new product rule by selecting Product from the SysAdmin category.
The key to a product rule instance has two parts:
Field |
Description |
| Product Name |
Enter a Product name. As a best practice, begin the name with a letter and use only letters, numbers, the ampersand character, and hyphens. |
| Product Version |
Enter a version name that includes only letters, numbers, and a hyphen. (This unrestricted value does not need to match a RuleSet version.) |
NOTE: Choose with care the RuleSet and version into which you place a new product rule. The direct or indirect prerequisites of that RuleSet version, as listed in the Requires RuleSets and Versions list of the RuleSet Version form, must include the RuleSets and versions to be included in the product.
Product rules are rarely referenced by other rules. However, when searching for a Product rule, the system:
Class-based inheritance does not apply. Time-qualified resolution features are not available for Product rules.