Configuring wMobile System Settings
System wide settings are configured from within the wMobile Manager Console.
For information regarding default user options, please see: Configuring wMobile User Options
The System Settings are accessed by selecting the wMobile node in the wMobile Explorer window and then double-clicking the System Settings icon.
To the right of the wMobile Explorer window is a tree list containing nodes. Selecting a node in the tree list will allow you to edit its associated properties in the Properties window on the right.
There are many configuration settings available that are not described here in detail. To get descriptions for a specific settings, click on a property name and its description will appear at the bottom of the dialog.
The Configuration node is at the top of the tree list and has the following sub-nodes:
▪Common: Contains settings that are common throughout wMobile.
▪Desktop: Contains settings that are specific to the wMobile Desktop edition.
▪Phone: Contains settings that are specific to the wMobile Phone edition.
Example of System Settings in wMobile Manager Console.
Here are some common settings that can be updated in System Settings.
Configuration > Common > Contacts >
AllowContactDeletion – This setting controls whether contacts can be deleted in wMobile. This is dependent upon GoldMine user settings as well.
ContactRecordTypeField – This should indicate which field in GoldMine is used to store the Record Type. Typically, this is the Key1 field, unless it’s been changed or customized.
Configuration > Common > Contacts > Duplication
AllowDuplicateEmailAddresses – This setting controls whether duplicate email addresses can be entered into wMobile. This is not recommended because email messages are linked based on a matching email address.
CheckCriteria – This setting is used to determine which field(s) will be used to detect potential duplicate records. Click on the 3 dots (ellipsis) at the end of the line to launch the Duplication criteria editor.
Options here are greater than in GoldMine itself (which includes Company and Contact name, Phone number and Email address). In wMobile, you can select any field, including custom fields, as potential duplicate detection criteria. If selecting more than one field, use And if both (or all) fields should be used to identify potential duplicates. Use Or if only one of the selected fields needs to match to be considered a duplicate.
The desired setting will be dependent on how your GoldMine is used. Some companies have a “company-centric” database where each company they work with has a record in GoldMine, and all the contacts they work with are entered as additional contacts on this one record. Some companies have a “contact-centric” database where they have a separate GoldMine record for each contact they work with. In the latter case, you would not want to be detecting duplicates based on Company, because you’d expect to have multiple records with the same company name. Another consideration is whether you have individual people as customers, where there’s no company name. Detecting duplicates based on Company wouldn’t be very helpful in that case. You’d want to match on Contact, or perhaps Company AND contact, so both would have to match for the new contact to be detected as a potential duplicate.
ConsiderBlankValues – This can be set as True or False. The desired setting will be dependent on how contacts are added in GoldMine. As in the example above, if you have many records where there’s no company name, then you’d want to set this as True to ignore the blank company field.
ConsiderRecordOwnership – This can be set as True or False. If set to True it will not take record ownership/curtaining into account on evaluating potential duplicates. So if a duplicate exists in the database, a user would be notified of a potential duplicate, even if he or she doesn’t have access to see it. If set to False, then record ownership/curtaining will not be ignored. If a user adds a record that already exists, he or she will not get any warning of a potential duplicate.
ConsiderUserAccessContactFilter – This can be set as True or False. If set to True it will NOT take record a User's record access filter into account on evaluating potential duplicates. So if a duplicate exists in the database, a user would be notified of a potential duplicate, even if he or she doesn’t have access to see it. If set to False, then record ownership/curtaining will not be ignored. If a user adds a record that already exists, he or she will not get any warning of a potential duplicate.
LinkedDocPath: This value represents a mapped drive or network UNC path that the Remote GoldMine Service can access. This path is where the linked documents will be saved.
AccountConnectionMaxRetries: This is the maximum number of times the wMobile Email Fetcher Service will try to connect to an email account. The default is 3, but can be increased. After this number of attempts, the account will be disabled for auto-checking to preserve resources on the server.
AutoFilingSupressionFilter: This can be manually entered values, such as specific email addresses. Email from an email address(es) would not be linked and auto-filed in History..
This option allows you to exclude email from auto-filing. For example, a specific email address or domain could be excluded. Add entries to this field to be excluded. Separate each of the filter values with a semi-colon (;) or a comma (,) character. An asterisk (*) character may be used as a wildcard in order to exclude all email from a specific domain.
firstname.lastname@example.org; email@example.com (these two email addresses will not be auto-filed).
*.baddomain.com (all email addresses from "baddomain.com" will not be auto-filed).
CountLimit: The count of emails that will be downloaded from the user’s server or ISP mailbox. The default is 1,000. The most recent emails are downloaded.
DaysLimit: This setting determines how many days back the fetcher service will go back to download email from the user’s server or ISP mailbox. In cases where an administrator is trying to auto-file older email, this number can be increased.
DDCheckInterval: This setting is used if DDEnabled is set to True, and determines how often (in hours) the fetcher will check and de-duplicate filed email.
DDEnabled: This setting determines whether the de-duplication service is enabled. Some customers have the email accounts set to auto-file certain email folders (such as the Inbox and Sent items folders). Auto-filing is mainly used by customers that don't use GoldMine or wMobile as their email client. They might use Outlook, Zimbra, Lotus Notes, MacMail, etc. However, sometimes, a customer will use multiple email clients and doesn't want to miss linking important emails. In this case, the de-duplication service would review emails for duplicates and remove them.
DDTargetPeriod: if DDEnabled is set to True, this setting determines how many days back will be checked for duplicates. The default is 30 days.
DisableFilingForUnlinkedEmails: This setting controls whether the menu options “File” and “Copy to GoldMine Inbox” are visible for unlinked emails.
EmailFetcherMinCheckInterval: This setting determines how often the email fetcher service will go out to the users' server or ISP mailbox to check for new messages. The default is 30 minutes, but can be decreased. It's not recommended to set this lower than 5 minutes to ensure a fetch is completed before the next attempt.
When auto checking is enabled, wMobile will make a specified number of attempts to connect to the email server to perform a sync. If the number of attempts exceeds the value set in the AccountConnectionMaxRetries property, wMobile will disable the auto checking by add a "tick" to the Disable Auto Checking checkbox for the email account trying to sync.
Example: Using default settings, the email Fetcher will attempt to connect to an email account 3 times, every 30 minutes. If it fails to connect those 3 times, over a total of 90 minutes, the auto-retrieval will be disabled. This is to avoid using up expensive system resources for failed connections.
For information on re-enabling auto-retrieval, see the topic on Troubleshooting Email Accounts.
EmailFetcherScanInterval: The default value is 1, so every minute the fetcher service will check the email accounts table and check if it's time to check each email account.
EmailFetcherTaskQueueConcurrentLimit: this determines the number of tasks that the fetcher will perform concurrently. The default is 25. Each request to check an email account is counted as a task. (by a user within the wMobile application or automatically by the fetcher service). If there are many email accounts, some tasks will be queued. When the number of open tasks drops below 25, queued tasks would then be processed accordingly.
EnableFilingOnSentItems: The default is False. This setting controls whether “File” option is available on Sent email. In most cases where email is sent from wMobile or GoldMine, the email is already filed. This option would pertain to customers using another email client to send email.
Configuration > Common > GoldMine
EnableMgrConsoleGMLogin: Use to disable the GoldMine user login requirement for the wMobile Management Console. When there is no GoldMine login requirement, it won't use a GoldMine license when opened.
UseGoldMineCurtaining: This controls whether wMobile will use GoldMine's record curtaining rules.
DisableAddToLocal: Use to disable/enable users from being able to add data into their device's local address book/calendar. Settings: False = enabled (allows users to use feature); True = disabled.
Configuration > Common > Security > Login
Tree Navigation: Configuration > Common > Security > Rights
AdditionalContactRights: Global System Rights for Additional Contacts.
HistoryActivityRights: Global System Rights for History Activities.
PendingActivityRights: Global System Rights for Pending Activities.
PrimaryContactRights: Global System Rights for Primary Contacts.
Configuration > Phone > Contacts
In new installations, this is set by default. Older installations might have this set as False to allow use of custom field view XML files.
Record Typing is automatically enabled in Desktop Edition, there is no configuration setting.
Configuration > Phone > Contacts > Related Actions
Many of these items have settings to control whether they appear in wMobile. The Visible status can be changed to False to remove them from view.
Configuration > Phone > Contacts > Related Views
Many of these items have settings to control whether they appear in wMobile. The Visible status can be changed to False to remove them from view. For example, f your company does not use GoldMine Cases, that option can be removed from view in wMobile so the menus will be shorter and will require less scrolling.
Configuration > Phone > Contacts > Opportunities
Although less commonly used, items can be removed from view in the Opportunities screens by changing the Visible setting from True to False.
Configuration > Phone > UI
•DefaultListPageSize: Defines the default number of items for lists.