Oracle CRM On Demand Desktop Administration Guide > Administering Oracle CRM On Demand Desktop > Changing the Behavior of Oracle CRM On Demand Desktop >
Controlling the Exclusions List
The Exclusions List allows the user to exclude an individual record from synchronization even if this record matches a defined filtering criteria. Oracle CRM On Demand Desktop does the following work:
- To identify the records that it must synchronize from the Oracle CRM On Demand server, it uses the following filters:
- Excludes the records that are in the Exclusions List. It excludes each record in the list only if some other record does not reference this record.
- If a record is listed in the Exclusions List, and if no other record references it, then Oracle CRM On Demand Desktop removes this record from Microsoft Outlook even if the Remove Local Records option contains a check mark.
To configure the exclusions list
- Display the Exclusions button on the Filter Records screen of the Synchronization Control Panel:
- Use an XML editor to open the connector_configuration.xml file.
- Locate the following features element:
<features>
- Make sure the following attribute in this features element is set to True:
enable_sync_exclusions
You can add this attribute to the connector_configuration.xml file if it is not visible. For more information on adding the enable_sync_exclusions attribute, see Controlling the Confirm Synchronization Tab.
Turning on Exclusion Functionality
To turn on the exclusion functionality for a specific object, complete the following procedure. To turn on exclusion functionality for a specific object
- Use an XML editor to open the connector_configuration.xml file.
- Locate the object type that you want to exclude.
For example, for opportunities, locate the following object type:
type id="Opportunity"
- In the object you located in Step 2, add the synchronizer element.
For example, add the following element:
<synchronizer name_format=":[:(Name):]" threshold="5">
For more information, see Example Code for Setting the Synchronizer Element.
- Repeat Step 2 through Step 3 for each object type.
- In the actions.js file locate the siebel_item_delete function and the types_options variable inside the following section:
var types_options = { "Mail": { "confirmation": false }, "Account": { "exclude_allowed": true }, "Contact": { "exclude_allowed": true, "exclude_supported": function(item) { return item["SiebelShared"]; } }, "Opportunity": { "exclude_allowed": true }, "Lead": { "exclude_allowed": true } };
- In this section, add the new object type definition, and add set the exclude_allowed property to True.
When you add the new object type definition, it must be in the following format:
"MyObject": { "exclude_allowed": true }
Examples of How Oracle CRM On Demand Desktop Uses the Exclusions List
Assume the following:
- Contact 1 references account 1.
- Contact 1 matches a filter, but account 1 does not match a filter.
In this example, Oracle CRM On Demand Desktop synchronizes account 1 because contact 1 references it. It does not add account 1 to the exclusion list. For another example, assume the following:
How Oracle CRM On Demand Desktop Automatically Adds Accounts, Contacts, and Opportunities to the Exclusions List
If the user deletes an account, lead, contact, or opportunity in the Explorer view, then Oracle CRM On Demand Desktop displays the following prompt: Are you sure you would like to delete this item from Oracle CRM On Demand and Microsoft Outlook? Click Yes to delete the items from both applications. Click No to remove the items from filter.
The user can choose one of the following values:
|