Bookshelf v7.5: Configuration Steps for Upgrade Inheritance

Upgrade Guide for Microsoft Windows > Upgrading the Siebel eBusiness Application > Preparing the Prior Customer Repository for the Merge >

Configuration Steps for Upgrade Inheritance

CAUTION: The repository merge procedures only apply to development environment upgrades. If you are performing a production environment upgrade, skip to Upgrading the Custom Database Schema.

After you have decided it is necessary to create a copy of an object in the repository, it is easy to specify the parent object from which the copy was created. After creating the copied object, specify the parent object name in the Upgrade Ancestor property of the copied object. This is what allows the copied object to be recognized as a copy during the application upgrade, and it is changed along with its parent object.

NOTE: You must manually populate this property since it is not automatically populated for you when you copy an object. Remember that this property can only be populated if the copied object is an applet, business component, integration object, or report object type.

To copy an applet, business component, integration object, or report object and children

Select the Object type (Applet, Business Component, Integration Object, or Report) in the Object Explorer.
Select an entry in the Object list applet.
Choose Edit > Copy Record to create a copy of this record.
In the new record, fill in a new name in the Name field.
In the Upgrade Ancestor field, select a value from the Upgrade Ancestor dialog box.

The picklist shows all the other business components, applets, integration objects, and reports in the repository.

The following figure shows that the Access Control Employee BC is the Upgrade Ancestor for the copied BC.

To view all descendants or copies of an object

Right-click on an object.
A dialog box appears.

Select View Descendants from the dialog box.

The following dialog box appears showing the Parent Name and Descendants.

UI objects should be copied if the look-and-feel of the application changes significantly or if there is a difference needed between two objects (that is, different search specifications on two applets). Business Components should only be copied after all other configuration approaches have been exhausted, and copying is clearly the only solution. The issues involving repository maintenance and specialized classes still are present with copied BCs. Upgrade Inheritance functionality allows certain copied objects to be upgraded and inherit the same characteristics that the parent object possessed. This avoids postupgrade errors and configuration problems.

CAUTION: In order to specify the Upgrade Ancestor property in Siebel Tools, you had to lock the project in Siebel Tools. Remember to unlock all projects before starting the repository merge.

Propagating Changes from a Parent to Descendants

It is possible to propagate changes that are made to the parent to the descendants of that parent. This is accomplished with the new Object Comparison and Synchronization feature, which allows two objects to be compared, and the differences between the two objects to be applied to one another to keep them synchronized.

The Object Comparison and Synchronization feature can be used to compare any two objects. The objects do not need to have a parent-descendant relationship.

CAUTION: Do not rename any objects relating to the Team Forecast View (SWG) and the Personal Forecast View (SWG), because they do not exist in the Release 7.x repository without the "(SWG)" suffix.

Upgrade Guide for Microsoft Windows
Published: 20 October 2003