Oracle CRM On Demand Desktop Administration Guide > Administering Oracle CRM On Demand Desktop > Changing the Behavior of Oracle CRM On Demand Desktop >

Setting Behavioral Limits for Oracle CRM On Demand Desktop

You can set the limits that affect certain Oracle CRM On Demand Desktop behavior. The files that this topic describes are part of the customization package. To modify one of these files, you can use any editor that supports editing in JavaScript or XML, such as Notepad.

To set the behavioral limits for Oracle CRM On Demand Desktop

1. Modify the helpers.js file to set certain limits.

   The helpers.js file is located in the customization package delivered in the installation ZIP file. Use the values from the following table.

   Variable with Default Value	Description
   var max_attach_file_size = 20	Sets the maximum size in megabytes of an attachment file in Microsoft Outlook.
   var ask_delete_confirmation = true	Determines if Oracle CRM On Demand Desktop displays the Revert Deletions and Accept Deletions buttons in the Confirm Synchronization tab of the Synchronization Control Panel.
   var action_selection_limit = 30	Sets the maximum number of items that Oracle CRM On Demand Desktop can process when the user executes a toolbar command. For example, if you set var action_selection_limit to 30, then the user can choose only 30 records in Microsoft Outlook, and then execute a command by using the toolbar in Microsoft Outlook. An example command is Email to Contacts. To avoid poor performance, you can modify this limit.

2. Edit the od_meta_info.xml file, using values from the following table. For more information on customizing, see Customizing Oracle CRM On Demand Desktop.

   Variable	Description
   max_commands_per_batch	Sets the maximum number of commands for each batch. For more information, see SiebelMetaInfo Element of the od_meta_info.xml File.
   max_ids_per_command	Defines the maximum number of object IDs. For more information, see SiebelMetaInfo Element of the od_meta_info.xml File.
   open_with_url_tmpl	Sets a template for the code that Oracle CRM On Demand Desktop uses to create a URL to open the page in Oracle CRM On Demand for that record.
   ViewMode	Sets the visibility of an object. Sales Rep is the only view mode supported in data synchronization. For example: ViewMode = Sales Rep For additional information on using the ViewMode attribute, see About the ViewMode Attribute When Using Books

About the ViewMode Attribute When Using Books

Book parameters are passed using the <Command> element attributes. For example, the following SOAP client request, from Oracle CRM On Demand Desktop to Oracle CRM On Demand, passes the following attributes:

ViewMode="Context" BookId="1QA2-1WPK6M" IncludeSubBooks="false"

When a user selects a book for a record type, the ID for that book and the IncludeSubBooks value are stored in the Microsoft Windows Registry. The connector then reads these values and inserts them into SOAP requests generated for that particular type. Also, Context viewmode is always used for such requests when you have to provide book parameters in those requests.

For example, the following is a sample SOAP request sent by the client:

<soapenv:Header>
  <ClientName xmlns="urn:crmondemand/ws">Oracle, CRM On Demand Desktop</ClientName>
  <crmod:SessionKeepAlive>true</crmod:SessionKeepAlive>
</soapenv:Header>
<soapenv:Body>
  <ClientSyncService_Execute_Input xmlns="urn:crmondemand/ws/crmdesktop/clientsyncservice/">
     <ListOfCommands xmlns="urn:/crmondemand/xml/clientsyncexecuteinput">
       <Batch>
         <Command ViewMode="Context" BookId="1QA2-1WPK6M" IncludeSubBooks="false">
            <Id>{27FA29C3-AD92-485E-BAE5-5E4567B03020}</Id>
            <Message><SiebelMessage IntObjectName='Account'>
                 <ListOfAccount startrownum='0' pagesize='100'>
                  <Account operation='querypage'>
                     ...
                  </Account>
               </ListOfAccount>
             </SiebelMessage></Message>
           </Command>
        </Batch>
     </ListOfCommands>
  </ClientSyncService_Execute_Input>
</soapenv:Body>
</soapenv:Envelope>