Siebel Configuration Best Practices : Part 4

Best practices for modifying Siebel Vanilla objects.

1. If  there is a Siebel Vanilla field where Immediate Post Changes, Force Active or Link Specification is set to TRUE, make sure you never change this property as it would be used in the underlying C++ code for that Business Component. Any change to the property will result in undesired errors which are very hard to debug.

2. When you clone or copy a Business Component, consider if the BC really does need to be cloned, as there is usually a lot of Siebel fields, MVL, User Properties on an existing BC. We need to find out that is it possible to create the BC from scratch only using the Fields, MVLs, user properties that are required? 

This could lead to better performance than cloning the entire BC. If the cloned BC has a class other then CSSBCBase then there is a need to introspect why you are cloning the BC in the first place, if you are not requiring any specialized class functionality then change the class of the cloned BC to CSSBCBase. CSSBCBase class allows user properties to be invoked which other Business Componenty classes can not. 

3. Ensure that you don't change the column or join on standard vanilla fields. The vanilla fields have been mapped to those joins/columns by Siebel and may be used in the C++ code associated to the class pertaining to that BC. Siebel have baselined and performance tested their product with the vanilla with the box BC fields and columns. Modifying the underlying columns on vanilla fields may adversely affect the performance of the Siebel application as appropriate indexes may not be used.

4. Ensure that you don't inactivate, delete or even modify any standard vanilla fields - the specialized C++ code for the BC class may require these fields and could cause errors which are very hard to debug and troubleshoot.

5. If  there is a need to create a new custom extension column you are usually create this on the base table (eg. S_OPTY) rather than using the 1:1 extension table (eg. S_OPTY_X). When you are updating and saving records having fields on the extension table it will result in additional INSERT or UPDATE statements required for the extension table.

Related Posts