Configuring the Cache Data Property of a Business Component

If Siebel CRM caches data for a business component, and if it modifies the contents of this cache, then this business component might reference obsolete data. This problem might occur in the following situations:

• A user modifies some data through another business component. For example, the user modifies data through a business component that uses a multivalue link.

• Another user modifies data while the user who first modified this data is still connected.

For this reason, it is recommended that you configure Siebel CRM to use caching only with static data, such as a list of values or a product. Do not configure Siebel CRM to use caching with data that the user might modify frequently, such as accounts or opportunities. If you do this, then the client cache might not remain synchronized with data in the server database.

It is recommended that you do not set the Cache Data property of a business component to TRUE and also set the Use Primary Join property of a multi value link to TRUE. If Siebel CRM modifies the primary record of a multivalue group business component in this situation, then it might not update data for the cached parent.