Limitations on the Upgrade Ancestor Property

The Upgrade Ancestor property is considered only during repository merges as part of application upgrades under these conditions:

• If an upgrade ancestor is inactive in the New Siebel Repository, then it is obsolete, and its upgrade behavior is not propagated to descendants.

  If an ancestor object is obsolete in the New Siebel Repository, then its descendants are not also obsolete.

  If an upgrade ancestor is not present in the New Siebel Repository, then error messages display during the repository merge and are written to the merge log file. These errors are acceptable and do not mean the merge has failed.

• The Upgrade Ancestor property is not considered during repository imports. However, imported objects can specify an upgrade ancestor. When the next application upgrade is done, the Upgrade Ancestor property is taken into account.

• The setting of the Upgrade Ancestor property is not considered when applying application patches. If the upgrade ancestor is modified by the patch, then descendants are not modified.

• Use caution when specifying upgrade ancestors. For regular merges, setting the Upgrade Ancestor property on applets propagates merge problems from standard-object applets to descendant applets.

• Specifying an upgrade ancestor for objects slows the repository merge.