Bookshelf Home | Contents | Index | Search | PDF |
Configuration Guidelines > Specialized Classes > Specialized Classes >
Business Components
Follow these guidelines when copying or creating business components:
- Avoid copying business components based on specialized classes unless you are trying to get exactly the same functionality with minimal changes.
- If you copy a business component and alter the class to CSSBusComp or CSSBCBase, be aware that this business component can now access the data without the special rules active. Be sure that this is what you want because specialized rules may not be followed.
- By default, when you create a business component, it has a class property of CSSBusComp. You can change this to CSSBCBase if required functionality, such as Deep Copy, is not available. Do not change the class property to any other value.
- If a business component is based on a specialized class, do not delete, inactivate, or remap any of the standard child objects. If the object is not required for your configuration, configure the user interface to not show, in the case of a field, any controls which map to that field.
- Only copy a business component based on a specialized class if you require a minor change to the existing business component and also need to use the original business component for something else.
NOTE: If you require a read-only version of the business component, create duplicate applets and use a No Delete setting, instead of duplicating the business component.
- When copying a business component based on a nonspecialized class, remove all redundant objects. Be aware that some of these objects may be referred to by properties of the business component or other child objects.
- If you need to copy a business component and keep the specialized class, do not delete or inactivate any of the fields that are present in the copy. Do not display the fields on applets if you do not need them. Because the specialized class may reference these fields, you must keep the original settings. Also, be sure to set the Upgrade Ancestor property, so the copy will upgrade correctly during the upgrade process.
Bookshelf Home | Contents | Index | Search | PDF |
Configuration Guidelines Published: 18 April 2003 |