Siebel Configuration Best Practices

• Always set Force Active and Link Specification to FALSE until and unless field is being used in Workflow or EAI and not exposed on UI. For scripting use ActivateField method.
• Use fields mapped to index columns only in sort specifications
• Make sure that Sort order sequence defined on the Business components and  Pre-defined queries are same.
• Always identify a Primary Id field for MVL and set the Use Primary Join Property to TRUE
• Use Field user property ‘Required’ for conditional required scenario rather than writing script.
• Define Upgrade Ancestor property for clone objects which will help in Siebel upgrade.
• Don’t hardcode values of LOV’s in script and calculated fields. Always prefer to use LookupValue.
• Create extension table on Base table if data will persist in that column for most of the records else use the available column of extension table.
• Do not set No Delete , No Insert , No Update Properties at BC Level.
• Avoid using Sum and Count functions in calculated fields and it fires the secondary sql query and leads to poor performance.