|
|
Map eForm 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 map eForm rule by selecting Map eForm from the Integration-Mapping category.
Key parts:
A map eform rule has two key parts:
Field |
Description |
|
Apply to |
Select the name of the class it belongs to. A map eForm rule and the eForm file rule it specifies have the same Apply to class. Typically, this is a class derived from the Work- base class. |
|
Identifier |
Enter a name for this rule. Begin the name with a letter and use only alphanumeric, ampersand, and dash characters. |
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 Map eForm rules