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 a new field value by selecting Field Value
from the Data Model
category.
Field |
Description |
Apply to |
Specify the class that this field value 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. |
Field Name |
Specify the name of a subset of values. Usually this is name of a |
Referred to as Quick Create options, the fields presented in this area of the Create form are optional. Selections made here can be used as a starting point for the rule you are creating:
Field |
Description |
Translated value |
Enter a value to update the Localized Label tab of the Field Value as follows: "Translate from {Short description} To {Translated value}" Enter a literal constant that is an acceptable value for the Field Name property, using only letters, numbers, single spaces, and a hyphen. The value might appear in a selection list or other aspects of the application user interface, so choose text that is meaningful to your user community. Enter no more than 64 characters. If the Apply to and Field Name key parts together identify a |
When searching for rules of this type, the system:
Time-qualified and circumstance-qualified rule resolution features are not available for this rule type.