
r3 recognizes three domains in which inheritance operates:
templates
translations
pages
r3 maintains separate inheritance trees for each dimension in each domain. This means that templates can have entirely different search paths from translations for each project, or for products or intls within a project .
![]() |
Note |
|---|---|
The page dimension has only one set of inheritance data for page specifications. |
The path in a project's tree structure that r3 uses to search for a domain object is called a search path. Search paths enable fine-grained control over sharing of customized templates and translations. During file generation, r3 requires a location to start searching for a domain object. If the object cannot be found in the start location, it searches other related locations higher on the tree until it finds the domain object or reaches the top of the tree. If r3 reaches the top of the tree without finding the object it is searching for, it uses the topmost object.