Bookshelf Home | Contents | Index | PDF |
Configuring Siebel Business Applications > Reusing Predefined Objects > Guidelines for Reusing a Predefined Object > Reasons Not to Reuse a Predefined ObjectReusing an object can result in problems. Copying a Predefined Object Can Cause an Upgrade ProblemCopying an object can cause an upgrade problem that is difficult to debug. Functionality is often added to most of the predefined business components during major releases. This new functionality often depends on new fields, joins, and so on, that Siebel CRM adds to a predefined business component. During the upgrade, Siebel CRM adds these new fields only to the predefined business components that reside in your merged repository. Copying an object can result in problems following an upgrade. These problems can be difficult to locate and debug. The errors often occur because some C++ code for the business component or applet class attempts to find a field that does not exist in your custom copy of that business component or applet. The only way to debug the problem is to compare your custom business component with the predefined business component, and to add any new fields and other child object definitions that Siebel CRM added in the new release. This work can be complex, requiring detailed knowledge of what Siebel CRM modified in the new release. Copying a Predefined Object Can Cause RedundancyCreating a new copy of a business component or applet can result in redundancy in your configuration. For example, if you create a copy of the Account business component and name it My Account, and use this copy on all of the views that reference accounts, then you must define copies of every applet that references accounts, and you must make sure each of these copies references the new My Account business component. It might be necessary for you to create a new business object, screen, and so on. Copying a Predefined Object Can Increase ComplexityYou might make a copy of an object in the belief that doing so will reduce problems during an upgrade. The assumption is that if the business component is named My Account, then the Application Upgrader will leave it alone during the upgrade, resulting in no problems after the upgrade. This assumption is misleading. The problems you might encounter with an upgraded configuration that contains a copied object might be more complex to solve than the problems that reusing a predefined object causes. It is easier to examine your Siebel application after an upgrade and remove various new controls and list columns from a predefined applet than it is to examine each custom business component and applet to identify the fields, joins, multi-value links, and so on, that you must troubleshoot. Results of Reusing An Object InappropriatelyReusing a Siebel module or repository object in a way that does not meet the original purpose of the object can cause the following problems:
|
Configuring Siebel Business Applications | Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |