wMobile System Settings (Part 1)
wMobile has a variety of System Settings that control how wMobile works, what options are visible to users, and how often certain tasks happen. Because there are so many options, we’ll be splitting this topic into two separate blog posts. In this first article, we’ll go over the Common settings (which includes system-wide settings and settings that apply to both Phone and Desktop applications) and Desktop-specific settings. We’ll cover the Phone Edition settings in the next article.
The wMobile System Settings can be accessed in the wMobile Manager Console, in the center pane as shown below.
If “Desktop” is selected in the wMobile Explorer Pane on the left, then only Desktop system settings will be displayed when the System Settings button is selected.
When you open System settings from the “wMobile” (top) level in the wMobile Explorer pane, you’ll have 3 sections of settings available: Common, Desktop, and Phone. Common settings pertain to both Phone and Desktop. These sections are normally expanded by default, but can be expanded and collapsed using the plus and minus ( + and -) buttons.
Each item that can be configured, will have an explanation of the setting when it’s selected, as shown below.
When a setting is changed, select Save to keep the changes. (You can make multiple changes and save when all are done.) Depending on the setting(s) changed, you might be prompted to restart some of the wMobile components as shown below.
Click OK to proceed. When it’s done, the window will close, and you’ll see a Ready status in the lower left.
We’ll highlight some of the most commonly changed System Settings.
- AllowMarkAsPrivate – This setting controls whether the option is shown on activities to be able to mark them as private. This would be on a system level, meaning that it would apply to all users.
- ShowNotesAsHtml – This option is shown in gray because it’s imported from GoldMine and can’t be changed here. It’s shown for reference.
- 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.
- CheckDuplicateContactCriteria – This can be set as None, Company, Contact, Company AND Contact, Company OR Contact. 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.
- 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.
- DuplicateCriteriaIgnoreBlankValues – This can be set as True or False. The desired setting will be dependent on how contacts are added in GoldMine. For example, 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.
- DuplicateCriteriaIgnoreRecordOwnership – 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.
- Linked Documents – If documents are uploaded on the Links tab in wMobile Desktop, this is the location where they will be uploaded. It’s recommended to have a specific folder for this.
- 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.
- AutoFilingSuppressionFilter – 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.
- 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.
- 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.
- EnableMgrConsoleGMLogin – If this is set to False, no GoldMine credentials will be required to open the wMobile Manager Console on the server. A user must already have actually logged onto the server to be able to launch the wMobile Manager Console. If this is set to True, then when the wMobile Manager console is opened on the server, a GoldMine username and password must be entered.
- UseGoldMineCurtaining – The default for this setting is True, so that GoldMine curtaining rules will be taken into account in wMobile.
- PDI (Personal Data Interchange) – These settings pertain to downloading contacts to a mobile device using the Add to Local Address Book feature.
- DisableAddToLocal – This setting controls whether the options are available for users to download contacts to local devices such as a phone, iPad, tablet, or computer such as a laptop.
- FaxMapping – This would be the fax label used when exporting a contact to a mobile device.
- Phone1Mapping - This would be the Phone1 label used when exporting a contact to a mobile device.
- Phone2Mapping -This would be the Phone2 label used when exporting a contact to a mobile device.
- Phone3Mapping - This would be the Phone3 label used when exporting a contact to a mobile device.
- PerfLog – If PerfLogEnabled is set to True, then performance logging will be enabled. An administrator can then query the WT_PerfLog SQL table. This is most often used in troubleshooting performance issues, but can also be used to track how often wMobile is used.
- DisableListClosest – This setting controls whether the “List Closest Contacts” feature is available in wMobile Phone. The feature will only work if the database has been geocoded with latitude and longitude values in the correct format. (The fields must be numeric fields with 6 decimal places. The fields must be type “float” in SQL.)
- GeocoderLatitudeField – the latitude field can be specified here.
- GeocoderLongitudeField – the longitude field can be specified here.
Account Policies | Password Policy
- MinPasswordLength – If a password change is prompted through wMobile, this setting for length would be taken into account.
- PolicyType – the Policy Type is 0 or 2. A zero value means no password security policy in wMobile. A 2 value will use a mixed policy utilizing GoldMine and wMobile security policies, such as GoldMine’s password expiration and wMobile’s password length rules.
- MaxFailedLogins – this is the maximum number of logins before a user’s account gets locked. The default is 3, but can be increased.
Security | Login
- AllowOneClickLogin – this setting controls whether users are allowed to create and use One-Click login shortcuts. The One-Click Login not only has the URL of the login page, but also encrypts the username and password. This can be a real time-saver and convenience not to have to type in the username and password on each login, however some company’s security policy would not allow this. If the value is set to False here, then the option will not appear in the user’s Options, and any previously created One-Click Logins would not work.
UI (User Interface)
- ClonedContactMessage – This is the warning that will appear on screen when the user clones a contact. (The “\r\n” code seen in this example results in the text appearing on separate lines in the on-screen message.)
- ShowUserOptions – At some companies, they configure a standard set of user preferences and don’t want them changed. In this case, the ‘Tools | Options’ menu item can be hidden from view so users cannot access their settings.
In the next blog article, we’ll show the most commonly changed settings for wMobile Phone Edition.