Bookshelf Home | Contents | Index | Search | PDF

Configuration Guidelines > Creating and Modifying Objects > Creating Specialized Objects >

Avoiding Redundant Objects

---

There are two reasons not to copy objects:

Copying creates redundancy.

New copies create redundancy in the repository. If you rename a business component and use it in several views, then new applets must be based on the new business component. This process adds considerable redundancy and effort to the configuration.

Copying increases difficulties.

Copying an object will not make it easier to upgrade because the object does not change during the upgrade. However, it is easier to remove any controls or list columns that were added during the upgrade than it is to try and manually upgrade the objects by adding all the new functionality from the upgrade.

For example, if you need a business component to appear in a business object more than once, or if a business component requires a different search specification or predefault property values, you may have to create new business components. You would also need to create a new business component if you create a completely new logical entity that serves a role that is not handled by any existing objects.

Bookshelf Home | Contents | Index | Search | PDF