Previous Topic: General Name Equivalence RulesNext Topic: Adoption Examples


Specific Name Equivalence Rules

Some objects have specific rules for name equivalence.

The aggregate objects that are adopted if they meet specific name equivalence rules follow:

This Type of Aggregate Object

Is Adopted If:

DIALOG FLOW

The source and destination procedure steps have common ancestry and at least one of the associated exit states have common ancestry

DENORMALIZED COLUMN

The parent tables, associated attributes, and the associated relationships have common ancestry.

FOREIGN KEY COLUMN

The parent table's associated attributes and the associated relationships have common ancestry.

INDEX
(non-identifier-based)

The associated data tables with common ancestry that implement relationships with common ancestry or the associated data tables with common ancestry and index with same name and associated database with same name and do not implement relationships.

LINK TABLE

The associated data tables and the associated relationships have common ancestry.

RELATIONSHIP

They have the same source and destination names and the associated entity types or subtypes have common ancestry.

TRANSACTION OPERATION (delegating)

They have the same name and are associated to entity type (or work attribute sets) and delegated to transactions with common ancestry

TRANSACTION OPERATION (non-delegating)

They have the same name and are associated to entity types and procedure steps with common ancestry

USER MATRICES

They have the same name and the associated x and y user or system-defined classes have common ancestry.