|
|
Data TransformsRecords 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 data transform rule by selecting Data Transform from the Data Model category.
Key parts
A data transform rule has two key parts:
Field |
Description |
|
Apply to |
Select a class that this data transform applies to. The list of available class names may depend on the ruleset you select. Each class may restrict rules applying to that class to an explicit set of rulesets as specified on the Advanced tab of the class form. |
| Name |
Enter a name that is a Java identifier. Begin the name with a letter, and use only letters, digits, and the dash character. See How to enter a Java identifier. A conventional name for the initial, and typically the simplest, data transform in a class is |
Rule resolution
When searching for instances of this rule type, the system uses full rule resolution which:
- Filters candidate rules based on a requestor's ruleset list of rulesets and versions
- Searches through ancestor classes in the class hierarchy for candidates when no matching rule is found in the starting class
- Finds circumstance-qualified rules that override base rules
- Finds time-qualified rules that override base rule
About Data Transforms