Siebel CRM Desktop for Microsoft Outlook Administration Guide > Reference Information for Siebel CRM Desktop >
Files That the Customization Package Contains
To customize some Siebel CRM Desktop features, you can modify XML files and JavaScript files in the customization package. CRM Desktop includes the following basic customization capabilities:
- Adjusting the business logic to suit the business environment
- Customizing the user interface
- Specifying security and data validation rules
For more information, see Where Siebel CRM Desktop Stores Data in the File System. Files in the Customization Package
Table 38 describes the XML files that Siebel CRM Desktop includes in the customization package. For more information, see About the Customization Package.
Table 38. XML Files in the Customization Package
|
|
code_pages.xml |
This XML file provides a simple listing of code pages used for conversion when necessary and indicates that it is not customizable by the user. |
connector_configuration.xml |
This XML file provides the following capabilities:
- Defines objects that are synchronized
- Defines the criteria that CRM Desktop uses to detect duplicate objects in the Siebel database
- Defines the preset filters for a custom synchronization
- Defines the object types that CRM Desktop displays in the Filter Records tab of the Synchronization control panel.
- Defines presets for sliding date ranges.
For more information, see Customizing Synchronization. |
data_sources.xml |
Defines the data source that CRM Desktop uses in views, forms, and dialog boxes for Auto-Complete. |
dialogs.xml |
Defines the layout for a custom dialog box. For more information, see Customizing Dialog Boxes. |
forms_xx.xml |
CRM Desktop uses the forms XML files according to the version of Outlook installed on the client. These XML files provide the following capabilities:
- Indicates the fields that CRM Desktop uses to store references between objects
- Defines the form layout for each object
- Defines the field validation rules on a form
- Defines business logic in JavaScript
- Defines controls that CRM Desktop uses on a form
Throughout this book, the term forms_xx.xml refers generically to these forms files. The xx refers to the internal version of Outlook as defined by Microsoft. If you edit a forms_xx.xml file, then make sure you edit the file that supports the version of Outlook that is installed on the client. The business_logic.js file describes most business logic. To specify business logic, it is recommended that you use JavaScript in one of the forms_xx.xml files only if CRM Desktop runs this logic in the current form. If many objects are involved, then it is recommended that you specify business logic in the business_logic.js file. For more information, see Customizing Forms. |
info.xml |
This XML file provides the following capabilities:
- Identifies the product name
- Identifies the package version and the CRM Desktop version
- Identifies the product versions that are compatible with the package
- Identifies the Siebel Server versions that are compatible with the package
- Identifies the general comments for the package
You can use it to track the package version. You can use the product name and version to check compatibility. For more information, see How Siebel CRM Desktop Determines Compatibility. |
lookup_view_defs.xml |
Defines the configuration for view lookup definitions. This file applies only for versions that occur prior to Siebel CRM Desktop version 3.5. For more information, see Customizing the SalesBook Control. |
package_res.xx_YY.xml |
Provide string and image resources for use throughout the application. The appropriate language and region is determined by the Outlook client. In the event that a string cannot be located in the language-specific packge_res_xx_YY.xml file, either because the file is not present or the individual string is missing, CRM Desktop will use the default string declared in package_res.xml (which is also the English version). Throughout this book, the term package_res.xx_YY.xml refers generically to these package files. Where xx and yy define the language and region. For example, package_res.pt_BR indicates the language is Brazilian and the region is Portuguese. |
platform_configuration.xml |
Defines the configuration for the platform. For example, the platform_configuration.xml file defines how to do the following:
- Connect to the Internet
- Share native Outlook items
- Convert contacts
- Control the synchronization intervals that display in the Synchronization tab
- Control the data that CRM Desktop removes if the user removes CRM Desktop
|
siebel_basic_mapping.xml |
This XML file provides the following capabilities:
- Defines field mapping between CRM Desktop and Outlook
- Defines field mapping between CRM Desktop and Siebel CRM
- Describes objects to add to Outlook
- Defines the form that CRM Desktop uses to display an object in Outlook
- Defines a set of custom Outlook views that CRM Desktop applies for an object
For more information, see Customizing Field Mapping. |
siebel_meta_info.xml |
This XML file provides the following capabilities:
- Defines the object types that CRM Desktop supports
- Defines fields and their types
- Defines the XML element names that CRM Desktop uses to create a Siebel message
For more information, see Customizing Meta Information. |
toolbars_xx.xml |
Defines custom toolbars that CRM Desktop displays on a native Outlook form, custom form, or in the Outlook window. CRM Desktop uses the toolbars files according to the version of Outlook installed on the client. Throughout this book, the term toolbars_xx.xml refers generically to one of these toolbars files. If you edit a toolbars.xml file, then make sure you edit the file that supports the version of Outlook that is installed on the client. External JavaScript files specify all programmable actions for a toolbar. For more information, see Customizing Toolbars. |
views.xml |
Defines the views that CRM Desktop uses in CRM Desktop forms and Outlook windows. For more information, see Customizing Views. |
JavaScript Files in the Customization Package
Table 39 describes the JavaScript files that Siebel CRM Desktop includes in the customization package.
Table 39. JavaScript Files in the Customization Package
|
|
actions.js |
Defines actions for the toolbar. |
actions_support.js |
Defines action support functions for the toolbar. |
activity_processor.js |
Defines activity processing. You must not modify this file. |
application_script.js |
Defines entry points for scripts and to call scripts from other files. |
autoresolver.js |
Defines functions to resolve conflicts. |
autoresolve_helpers.js |
An internal CRM Desktop file. You must not modify this file. |
business_logic.js |
Defines logic for the following items:
- Activities
- Mail processing
- The data model
|
data_model.js |
Defines the data model and functions for objects. |
forms.js |
Defines user interface actions. |
form_helpers.js |
Defines functions to handle user interface events. |
helpers.js |
Defines utility functions. |
idle.js |
Defines the Idle Processing Manager and idle handlers. |
md5.js |
Defines how to implement MD5 (Message Digest Algorithm). |
mvg_dialogs.js |
Defines controls for multi-value groups. |
raw_item_functions.js |
Defines functions that access Outlook items. |
recurrence_processing.js |
Defines patterns for recurrence processing. For more information, see How Siebel CRM Desktop Transforms Objects Between Siebel CRM Data and Microsoft Outlook Data. |
sb_helpers.js |
Defines utility functions that are specific to Siebel CRM. |
security_manager.js |
Defines the security model. |
security_utils.js |
Defines security definitions that are specific to Siebel CRM. |
JavaScript Files That Siebel CRM Desktop Uses Internally
Siebel CRM Desktop uses the following files internally. You must not modify these files:
- actions_support.js
- activity_processor.js
- autoresolve_helpers.js
- data_model.js
- form_helpers.js
- helpers.js
- idle.js
- md5.js
- mvg_dialogs.js
- security_manager.js
|