Bookshelf Home | Contents | Index | Search | PDF

Siebel Tools Reference > Repositories > Automatic Upgrade of Copied Objects >

Recommended Guidelines for Copying Objects

---

The guidelines for copying objects vary. If the object is a UI object such as an applet or view, it should only be copied if significant changes will be made to the look and feel of the object. Copying the object rather than using the out-of-the-box object makes certain that the modified look and feel would be preserved following the upgrade. If only minor changes will be made to the UI object, it is better to use the out-of-the-box object since this will eliminate the time spent on configuration and the continuing maintenance of the repository. Other valid reasons for copying UI objects would be:

If two different UI objects had to display different records (that is, different search specifications on applets).
If different read/write properties between two objects were necessary (that is, one applet is read-only, and the other is editable) and if this could not be accomplished through the dynamic read-only buscomp user property.
If different drilldowns were necessary for different applets depending on the view that contains them (and provided this could not be accomplished through a dynamic drilldown).

When copying an applet that uses a business component based on a specialized class, the following guidelines apply:

The copied applet must be used with the original business component, not a copy of the original business component.
If you want to use a copied applet with a copied business component, you need to change the class of the copied applet.

These guidelines are illustrated in the following example:

Applet	Applet Class	Business Component	Business Component Class
Quote List (SCW)	CSSFrameListQuote	Quote	CSSBCQuote

If you copy the Quote List (SCW) applet, the copied applet can only use the original Quote business component, not a copy of the Quote business component. However, if you change the class of the copied Quote List (SCW) applet from CSSFrameListQuote to CSSFrameList, then you can use the copied Quote List (SCW) applet with a copy of the Quote business component (which is still based on the CSSBCQuote class).

If the object is a non-UI object, such as a business component or business object, it is recommended that you not copy them if not absolutely necessary. These recommendations pertain mainly to the copying of BCs, which is more common than copying BOs. Copying BCs and BOs should be avoided. In other words, the out-of-the-box object should be used, and modifications should be made to this object rather than creating a copy and using the copy in the configuration. There are some situations when the copying of BCs cannot be avoided. The following reasons are given for this:

When a BC must appear twice in a business object; for example, when the Account BC and Sub Account BC both appear within the Account BO.
When two BCs contain different search specifications and predefault values for the type field that differentiates the records of these two BCs.

These guidelines are aimed at minimizing the use of copied BCs because of the problems that can occur with repository maintenance, specialized classes, and upgrading. Even with the Upgrade Inheritance feature it is important to be careful in deciding to use copied objects.

Bookshelf Home | Contents | Index | Search | PDF