Navigation

• Main Page

• What's New
• All Pages
• Categories

• Language Selection

Quick Search Advanced Search »

Table of Contents [Hide/Show] Introduction The Mobile client     Basics     Initialization        Initial Synchronization     Interface        Navigation        Views           Menu           Search           Activities view        Forms           Navigation           Mandatory, business recommended and optional fields           Field types           Related views        Options        Wildcard searching     Synchronization

Edit

Introduction

This document is a guide for end-user of the CWR Mobile Client for iPhone. It describes how to use the Mobile Client.

Edit

The Mobile client

The Mobile Client is an extension to the Microsoft Dynamics CRM platform. It can be used by mobile users to work offline and synchronize periodically with the office. The following chapters describe the following subjects:

• Basic functionality of the Mobile Client.
• Initializing and starting the Mobile Client.
• How the Mobile Client synchronizes with the server.
• How navigation through the Mobile Client works.
• How to use views to display relevant information.
• How forms are used in the Mobile Client.

Edit

Basics

CWR Mobile CRM is an application installed on the iPhone and is found in the App Store. The application link can also be found by opening the CWR updates page in the web browser. The CWR updates page is a web page that is installed on the CWR Mobile CRM server. the updates page can be opened by opening the safari browser on the iPhone and navigating to http(s)://servername:portnumber/cwrupdates. Replace the servername and portnumber with the appropriate URL.



The client contains the following functionality:

• The Mobile Client can go offline, storing its information in a local database.
• The Mobile Client doesn’t require configuration updates after initialization. Updates are automatically transferred when the client synchronizes with the CWR Server.The following updates are transferred automatically:
  • Changes in Entity Metadata, like added fields.
  • Views.
  • Forms.
  • Navigation.

Edit

Initialization

When the Mobile Client has been installed from the Apple App Store, it has to be initialized. This means that all basic configuration information is sent to the Mobile Client. When the initialization has been performed, the user can use the Mobile Client. Upon first starting the Mobile Client, the system will display the initialization wizard. The initialization screen will ask the user for the remote URL where the CWR Server can be found, his or her credentials and the domain name. Please not that the following screenshot is not representative of your organization. Make sure you have the correct URL available.



Click “Done” in the top menu to continue the setup. At this point, the user is validated as a legitimate Mobile User. If the user is not a valid mobile user, an error message is displayed. Contact the administrator of the software if this occurs.

Note: Make sure you have a stable connection to the CWR Server. This is essential for a correct initialization.

The initialization process can take a while to complete. A message is displayed when the process is complete.



Click on the "Dismiss" button in the message box to finish the initialization process. The Mobile Client will start automatically.

Edit

Initial Synchronization

When the Mobile Client is started for the first time, no data is available to the user. The Mobile Client must first be synchronized. To perform the initial synchronization, click on the "Synchronize" button on the bottom menu.

Edit

Interface

Edit

Navigation

The first screen to open when the application is started is the main navigation. It consists of the following components:

• The Main navigation section. In the following figure, these tabs are "Workplace" and "Sales".
• Sub navigation items that give access to the underlying data and are placed under the main navigation.
• Access to the Synchronization Manager. (See "Synchronization")
• Access to the options menu.

Edit

Views

Views are a way to filter and view the information in an entity, like accounts, in a user-friendly way. A view exists of a set of columns and a filter to show only relevant data. An example of a view is "My active accounts". All accounts have an owner, and the view displays only accounts with the user as owner. This is called a filter. The columns in this example are "Account Name" and “Main Phone”.

Note: Only the first and second columns in the view definition are used in the IPhone display.



To display all the views that are available, click on the views button.

Menu

The menu of a view contains the following options:

• Views: All views defined for that entity.
• Create: A new record of the type of the view is opened.

Note: The activities views will display a selection box of the available activity types.

Search

Besides using views to filter data, it is possible to search the view. The search box located above the view results. To search, open a specific view and tap in the search box. When text is entered, the list will automatically be filtered.

The administrator that maintains the views can determine which fields have to be searched, when a mobile user searches for information. The administrator also determines which fields are displayed in the views. It is not possible to update this information from the Mobile Client.

Activities view

There is a special view available to display different activities. This view is similar in look and feel to a regular one, with the difference that it is possible to view and create the following activities:

• Appointments.
• E-mails.
• Phone calls.
• Service Activities.
• Campaign Responses.
• Tasks.
• Letters.
• Faxes.

Note: Depending on which activity types are synchronized to the IPhone, certain activity types may not be displayed.

Edit

Forms

Forms display information of a record, like "Account Name" and "Addresses" from an account. The user can open the form of any record by tapping on it. Records can be found in a view.

Navigation

To navigate through the form tap and hold your finger on the screen and move it to the top. This will cause the screen to move downwards.

Note: Unlike the Windows Mobile Client, tabs are located on a single page. They are clearly indicated on the form by their name.



The menu button on the bottom menu brings up the related views. This button is displayed in the following image:



To start editing the form, click on "Edit" in the top-right corner.

Mandatory, business recommended and optional fields

The administrator can set the type of fields, but also make them mandatory, business recommended or optional. They can be distinguished by their color.

• Mandatory fields: These fields are indicated by a red star in the right-top corner of the field. When the Mobile User leaves this field empty, the Mobile Client will display a message stating that the field is empty.
• Business recommended fields: These fields are indicated by a blue star in the right-top corner of the field. When the Mobile User leaves this field empty, the Mobile Client will not display a message.
• Optional fields: These fields are displayed as normal text and do not have to be filled in.
• Disabled fields: These fields cannot be edited and are greyed-out.

Field types

There are different types of fields that are available on a form. These fields are configured by an administrator and cannot be changed on the Mobile Client. The following list describes all the available fields and shows how the field looks like on the Mobile Client:

• Text field: In these types of fields Mobile Users can type anything. The administrator can set the maximum amount of characters the Mobile User can type. An example of an open text field is "Account name" or "Category".

• Memo fields: Memo fields are large text fields that are designed for displaying large amounts of text. The administrator can set the size of the field. An example of a memo field is “Description”. Extra functionality of this field is that when you empty the label of the field in the Mobile Configurator, the field is expanded over the whole width of the page, giving the user even more space to enter data.

• Number fields: These fields are for inserting numbers only. An example of a number field is "Number of employees" or "Duration".

• Currency fields: These fields are for inserting amounts only, like "Annual revenue". The localization of the Mobile User determines which currency symbol is used.

• Picklist fields: A picklist is a list of defined number of choices the Mobile User can make. An example of a picklist field is “Relationship type”.

• Date/Time fields: Date/Time fields are fields that can be used for displaying dates and/or times. This means that administrators can determine if only the date or time or both are displayed. An example of a date only field is "Birthday". An example of a date/time field is "Appointment start".

• Telephone fields: These fields are similar to Open Text Fields, with the addition of the ability to directly call the number in the field. An example of this field is "Mobile Phone" or "Work Phone". When the user clicks the field, the phone number is dialled automatically.

• URL and E-mail fields: These fields are similar to Open Text Fields, with the addition of the ability to open the URL in a web browser. An example for these field are "E-mail address" and "Web Site".

• Boolean fields: A Boolean field is a field with two options, mostly "Yes/No". Only one option can be set, so its value is either one or the other. An example of this field is "Send Marketing Material".

• Lookup fields: A lookup field is a special type of field, because it links a single other record to the form. An example of this field is “Primary contact” on the account form. The contact is a different type of record, but through the “Primary contact” it is linked to the account.

It’s not possible to type in this field. The field is filled in by clicking on the search icon on the right side of the form.



If the form is in edit mode, the following screen is displayed:



The Mobile User can click on a record and it will be linked to the lookup field. If the value has to be removed, the Mobile User can click on the "Clear" button in the top-right corner of the screen. The lookup field is cleared.

Note: When the form is opened, and the lookup field is clicked, the user will be taken to the lookup record form.

• Party list fields: A party list field is a lookup field where multiple records of multiple types can be linked to the form. An example of this field is "Required attendees" in the appointment activity. This means that the Mobile User can link an account and contact to the required attendees.

it’s possible to link different types of records to the party list. This is done by clicking on the party list filed and selecting the type of record in the menu on the bottom of the screen. When all records have been added, click "Done".

Note: If the type selector on the bottom menu is not click-able, it is not possible to link other entities.

to remove a selected record, click on the remove button icon on the left of the record. Click "Apply" to remove.

Related views

Entities can be related to each other, like contacts and accounts. An example is that a contact can have one or more accounts to which they are related to. In this case, the contact is a primary contact for all accounts. Related accounts are shown in the "Related" menu item on the contact form.



It is possible that more than one related view has been created by the administrator. This has been done to filter the related view in much the same way as a regular view. (See chapter "Views"). To open other related views, open a specific related view and click on the "Views" button.

If the menu button for "Views" is greyed out, no other related views have been created for this form (other than the one on the screen). It is possible to create a new related record by clicking on the button "New" in the bottom menu. This opens a new record. After saving, the record is displayed in the related view. When a new related item is created, the attribute mapping from CRM is used to pre-fill fields. An example: If the Mobile User opens an account and adds an contact, the address fields of the contact will automatically be filled in.

Edit

Options

It’s possible to change certain configuration options for the Mobile Client. These options can be found in the main navigation, by clicking on the "Options" button in the bottom menu.

The following options are available for configuration:

Connection:

• CRM Server: The location of the server. This field is editable.
• Username: The mobile username. This field is not editable.
• Password: The password of the mobile user. When the mobile users’ password changes, it’s possible to update the password in this field.
• Domain: The domain name of the user. This field is editable.
• Organization: The CRM organization name. This field is not editable.

Application:

• Log: All errors are logged. To view these errors, open the log viewer.
• Search mode:
  • No wildcard: No wildcard characters are added to a search query in the view.
  • Wildcard prefix: A wildcard character is added in front of a search query.
  • Wildcard suffix: A wildcard character is added behind a search query.
  • Full wildcard: Two wildcard characters are added; one in front and in behind a search query.

More information about wildcard searching, see the next chapter.



Edit

Wildcard searching

A wildcard character is used to substitute any other character or characters in a search query. The asterisk (*) substitutes as a wildcard character for any zero or more characters, meaning that it’s possible to search, for example companies, without knowing the full name of the company.

The following examples describe the differences with each wildcard setting.

• No wildcard.

No asterisk is added to the search query. This means that the full search query has to be given or no results will be returned. An example: The Mobile User wants to find the company "CWR Mobility", but the user only remembers "CWR". The Mobile User searches for CWR, but no results are returned, because the full company name must be inserted.

• Wildcard prefix.

An asterisk is added before the search query. An example: The Mobile User wants to find the company "CWR Mobility", but the user only remembers "Mobility". The Mobile User searches for "Mobility", and the result "CWR Mobility" is found.

• Wildcard suffix.

An asterisk is added before the search query. An example: The Mobile User wants to find the company "CWR Mobility", but the user only remembers "CWR". The Mobile User searches for "CWR", and the result "CWR Mobility" is found.

• Full wildcard.

An asterisk is added before and after the search query. An example: The Mobile User wants to find the company "CWR Mobility", but the user only remembers "Mobi". The Mobile User searches for "Mobi", and the result "CWR Mobility" is found. This is because the wildcards replaced all characters before and after “Mobi”.

Edit

Synchronization

Synchronization is a process where data is exchanged between the server and the Mobile Client. To synchronize the Mobile Client, navigate to the main screen and click on the "Sync" button on the bottom menu. This opens the Synchronization Manager as displayed in the following figure. Click on "Start" to begin synchronization.



Note: When the Mobile Client has been initialized, there is no data stored in the local database. To fill the system with data from the server, an initial synchronization must be performed first.