Siebel CRM Desktop for IBM Notes Administration Guide > Customizing Siebel CRM Desktop > Customizing UI Behavior >

Controlling How Siebel CRM Desktop Handles Data That Is Not Directly Visible

You can use the viewmodes element to configure Siebel CRM Desktop to display or hide data that is not directly visible. Data that is not directly visible is a type of data that the client does not receive during synchronization, but instead gets through an association with another Siebel CRM object type. For example, filter settings might prevent CRM Desktop from synchronizing some accounts to the client, but the synchronized contacts that reference these account might contain this account data. In this situation, CRM Desktop displays this account information in the Contact form, but not in an Account view.

Starting with Siebel CRM Desktop version 3.1, you can configure a view mode according to the type of operation that CRM Desktop performs. You can use one of the following values for the viewmodes element:

• General. Specifies a value for the General viewmode. If this value exists, then it overrides a value that the ViewMode attribute specifies.
• Dedup. Specifies a value for the Deduplication view mode. For more information, see Resolving Synchronization Conflicts.
• QBID. Specifies a value for the Query-By-Id view mode.
• Not specified. If you do not specify the viewmodes element, then CRM Desktop does the following:
  • Uses the default value for the deduplication viewmode that it gets from the value that you set for the General view mode
  • Uses All as the default value for the Query-By-Id view mode.

CRM Desktop uses a master filter only on query change requests when it uses the General view mode.

For more information, see How CRM Desktop Displays Data That Is Not Directly Visible.

Using Query By Id to Hide Data That is Not Directly Visible

The example in this topic configures CRM Desktop to hide all data that is not directly visible for contacts. It prevents CRM Desktop from getting data from the Siebel Server and storing it in the client.

To hide data that is not directly visible for contacts

1. Use an XML editor open the siebel_meta_info.xml file.
2. Define the following view modes for the contact object type:

   General="Sales Rep" Dedup="All" QBID="Sales Rep"/>

3. Define the following view modes for the account object type:

   General="Sales Rep" Dedup="All" QBID="Sales Rep"/>

4. Define the following view modes for the opportunity object type:

   General="Sales Rep" Dedup="All" QBID="Sales Rep"/>

5. Define the following view modes for Contact.Account and Account.Contact:

   General="Sales Rep" Dedup="All" QBID="Sales Rep"/>

6. Define the following view modes for Contact.Opportunity and Opportunity.Contact:

   General="Sales Rep" Dedup="All" QBID="Sales Rep"/>

7. Make sure the user does not modify the default filter preset that restricts the number of objects that CRM Desktop synchronizes from the Siebel Server.

Using Query By Id to Synchronize Only My Accounts and Activities

1. Use an XML editor open the siebel_meta_info.xml file.
2. Locate the following code:

   Account

   <object TypeId='Account' Label='#obj_account' LabelPlural='#obj_account_plural' UpsertBusObjCacheSize='0' EnableGetIDsBatching='true' IntObjName='CRMDesktopAccountIO' SiebMsgXmlElemName='Account' SiebMsgXmlCollectionElemName='ListOfCRMDesktopAccountIO' >

   <viewmodes General="Sales Rep" Dedup="All"/>

   Account.Action

   <object TypeId='Account.Action' Label='Activity' LabelPlural='Activities' EnableGetIDsBatching='true' IntObjName='CRMDesktopAccountIO' SiebMsgXmlElemName='Action' SiebMsgXmlCollectionElemName='ListOfAction' >

   <viewmodes General="All" Dedup="All" />

3. Modify the code you located in Step 2 to the following code. Bolded font indicates the modifications you must make:

   Account

   <object TypeId='Account' Label='#obj_account' LabelPlural='#obj_account_plural' UpsertBusObjCacheSize='0' EnableGetIDsBatching='true' IntObjName='CRMDesktopAccountIO' SiebMsgXmlElemName='Account' SiebMsgXmlCollectionElemName='ListOfCRMDesktopAccountIO' >

   <viewmodes General="Sales Rep" Dedup="All" QBID="Sales Rep"/>

   Account.Action

   <object TypeId='Account.Action' Label='Activity' LabelPlural='Activities' EnableGetIDsBatching='true' IntObjName='CRMDesktopAccountIO' SiebMsgXmlElemName='Action' SiebMsgXmlCollectionElemName='ListOfAction' >

   <viewmodes General="Personal" Dedup="All" QBID="Personal"/>

Using Filters to Hide Data That Is Not Directly Visible

This topic describes how to hide data that is not directly visible for accounts from a custom IBM Notes view that Siebel CRM Desktop uses. It describes how to prevent CRM Desktop from storing data in the client. For information about how to prevent CRM Desktop from getting data from the Siebel Server and storing it in the client, see Using Query By Id to Hide Data That is Not Directly Visible.

To use filters to hide data that is not directly visible

1. Open IBM Domino Designer, and then choose the _Account view.

   For more information, see Opening IBM Domino Designer.

2. In the Objects tab, choose View Selection.
3. Make sure IBM Domino Designer displays the View Selection code. For example:

     SELECT CRMDType="Account" & (@Contains(ObjectStateString;"P") | !(@Contains(ObjectStateString;"I") | @Contains(ObjectStateString;"V")))

   where:

   • CRMDType="Account" configures CRM Desktop to choose only accounts for the view.
   • (@Contains(ObjectStateString;"P") establishes the P object state string.
   • !(@Contains(ObjectStateString;"I") makes sure CRM Desktop does not established the I object state string.
   • (@Contains(ObjectStateString;"V") establishes the V object state string.
4. Use an XML editor open the Ln_connector_configuration.xml file, and then make sure the state_field for the Account type uses the following value:

   <type id="Account" state_field="ObjectState">

   If you copy this view, then CRM Desktop also copies this filter. This configuration allows you to create other views that you can use with Siebel CRM data.