Object Interdependencies

When effective dating is applied to organization objects within Incent, interdependencies between the objects work like this:

• People—Once created, a Person is associated with a User (Setup > User), and
exists for all time unless removed. There can be multiple versions of a Person, made unique by the effective start date of the version.
User assignments and Employee Status apply to all versions, and a Person can only exist in one Position version for any given date.
• Positions—A Position is associated with a Title and with the Person currently associated with that Title. There can be multiple versions of a Position, made unique by the effective start date of the version. Once created, Positions exist for all time
unless removed. A Person can only exist in one Position version for any given date.
• Hierarchy—is the relationship of position to position that illustrates the organization of the company. Positions can be added, moved, and removed from version to version. This object controls team report access and indirect credit rollup.
• Named Relationships—are position-to-position relationships, where one-to-many relationships can be added, changed, or removed from version to version to use in indirect crediting.

The relationship between positions in the Hierarchy and Named Relationships creates the structure of your company’s hierarchical organization for security and indirect crediting.

To track typical changes that occur during each month, you can create different versions of each object that are made unique by the dates during which they are active.

The first version you create of a Person, Position, Hierarchy, or Named Relationship object is considered the master version of that object.

For more information about versions, see Using Versions.