Mobile Sales Configuration File for Windows Mobile

System Administrators can modify the Mobile Sales system configuration for Windows Mobile in the SybaseCRM.Configuration.xml file. You must update and provision this file to the device before logging into the application (subscribing) for the first time.

The Mobile Sales installation for Windows Mobile contains two versions of this configuration file.

File name	Location on Windows Mobile device	Purpose
SybaseCRM.Configuration_template.xml	\Program Files\Mobile Sales\Templates	To change system configuration settings for your company, modify this version of the configuration file. Modify options that begin with `SYS_`. Device users can modify the other options in this file by changing application settings.
SybaseCRM.Configuration.xml Note: Do not modify. This file is the runtime version of the configuration file.	\Program Files\Mobile Sales\Data	During application startup, the Mobile Sales application copies the version from the Templates directory to the Data directory. When device users change Settings from within the application, the new values are written to this configuration file.

Once you modify the template version of this file, you can provision it to one or more devices. For personal/developer installations, you can overwrite the default file in the Templates directory, for example, using ActiveSync. For enterprise installations, use Sybase Unwired Platform to provision the configuration file to the device. In Sybase Unwired Platform System Administration, see Systems Administration > Device User Management > Device Provisioning > Afaria Provisioning and Device Management.

Mobile Sales for Windows Mobile system configuration options
Configuration option	Description
SYS_PushToNativeContact	Determines how native contacts synchronize with Mobile Sales contacts. Automatic – all new Mobile Sales contacts become personal contacts; however, you must manually indicate which new personal contacts become Mobile Sales contacts. Once connected, if you change contact data in one place, it automatically synchronizes it. Manual (default) – you must indicate which Mobile Sales contacts that you want to copy to your native contacts, and which personal contacts you want to convert to Mobile Sales contacts. Once you indicate this connection, changes to contact data in one place automatically synchronizes data between both contact instances. None – you cannot link personal and Mobile Sales contacts.
SYS_PushToNativeCalendar	Determines how native calendar entries synchronize with Mobile Sales activities. Automatic – new Mobile Sales activities for meetings, tasks, and appointments become personal calendar entries; however, you must manually indicate which new personal calendar entries become Mobile Sales activities. Once connected, if you change data in one place, it automatically synchronizes it. Manual (default) – you must indicate which Mobile Sales activities that you want to copy to your native calendar, and which personal calendar entries you want to convert to Mobile Sales activities. Once you indicate this connection, changes to data in one place automatically synchronizes data between both instances. None – you cannot link personal calendar entries and Mobile Sales activities.
SYS_MaximumLoginAttempts	Indicates the maximum number of incorrect login attempts before the user is locked out of the application.
SYS_MaximumLoginAttemptsExceeded	Indicates whether the device user has exceeded the maximum number of login attempts. If this option is set to true, the user has exceeded the limit. Instruct the device user to edit this file and set it back to false to be able to log into the application.
SYS_MinimumMemory	Indicates the minimum memory required, in MB, for creating the database and initially subscribing to the SAP system. If this minimum memory is not met, a subscribe is not attempted. If the database already exists, this parameter is ignored. The default is 2MB. In organizations where devices are expected to store large data sets, you can increase this value so that storage memory is not exhausted during the initial subscribe.
SYS_SubscriptionBlockSize	Determines the number of messages processed in each message processing interaction from the message queue. The default is 10. Note: Do not set this value to 0. Use caution in setting this value to a large number or increasing it significantly; runtime memory could be consumed during the processing of a large block of messages, thus affecting overall performance.
SYS_Enable_Accounts	Enables the Accounts facet in the application. Enter false to disable the functionality and remove the icon from the home screen.
SYS_Enable_Contacts	Enables the Contacts facet in the application. Enter false to disable the functionality and remove the icon from the home screen.
SYS_Enable_Activities	Enables the Actvities facet in the application. Enter false to disable the functionality and remove the icon from the home screen.
SYS_Enable_Leads	Enables the Leads facet in the application. Enter false to disable the functionality and remove the icon from the home screen.
SYS_Enable_Opportunities	Enables the Opportunities facet in the application. Enter false to disable the functionality and remove the icon from the home screen.
SYS_Enable_SalesDocuments	Enables the Sales Documents facet in the application. Enter false to disable the functionality and remove the icon from the home screen.
SYS_Enable_Analytics	Enables the Analytics facet in the application. Enter false to disable the functionality and remove the icon from the home screen.
SYS_AskEnableDemoMode	Enables a pop-up asking to run the the CRM app in demo mode. The default is true. Set this parameter to false to disable the pop-up. If enabled, the user is prompted by the pop-up only once. The user is not prompted each time the user starts the application. The app can be run in demo mode without installing Sybase Messaging.
SYS_MappingKey	Sets the Google maps API key. For additional information about the Google Maps API and licensing, see http://www.google.com/enterprise/earthmaps/maps.html. Go to http://code.google.com/apis/maps/signup.html to sign up and generate the key.