MyCalls Screen-Pop - Nycomm Holding Page

Transcription

MyCalls Screen-Pop - Nycomm Holding Page
MyCalls Screen-Pop
Configuration Manual
CONFIGURE 3 RD PARTY APPLICATIONS TO INTERACT WITH MYCALLS
MYCALLS
MYCALLS DESKTOP
MYCALLS CALL MANAGER
MYCALLS CALL CENTRE
For NEC SV8100/SV9100 PBX systems and MyCalls version 4.5.x.x
1510-008-001
1
Contents
MyCalls Screen-Pop ........................................................................................................................... 1
Contents .................................................................................................................................................. 2
Copyright ................................................................................................................................................. 4
Revision History ...................................................................................................................................... 5
Macro script language............................................................................................................................. 6
Supported Versions ...................................................................................................................... 6
License Type ................................................................................................................................. 6
Prerequisites ................................................................................................................................ 6
Configuration Notes ..................................................................................................................... 6
Microsoft Outlook ................................................................................................................................... 7
Supported Versions ...................................................................................................................... 7
License Type ................................................................................................................................. 7
Prerequisites ................................................................................................................................ 7
Configuration Notes ..................................................................................................................... 7
ACT! ......................................................................................................................................................... 9
Supported Versions ...................................................................................................................... 9
License Type ................................................................................................................................. 9
Prerequisites ................................................................................................................................ 9
Configuration Notes ..................................................................................................................... 9
Goldmine............................................................................................................................................... 11
Supported Versions .................................................................................................................... 11
License Type ............................................................................................................................... 11
Prerequisites .............................................................................................................................. 11
Configuration Notes ................................................................................................................... 11
Maximizer ............................................................................................................................................. 12
Supported Versions .................................................................................................................... 12
License Type ............................................................................................................................... 12
Prerequisites .............................................................................................................................. 12
Configuration Notes ................................................................................................................... 12
Sage Line 50 .......................................................................................................................................... 14
Sage Line 50 ODBC ................................................................................................................................ 14
Supported Versions .................................................................................................................... 14
License Type ............................................................................................................................... 14
Creating an ODBC DSN................................................................................................................... 15
Setting up the MyCalls Screen pop Configuration screen ............................................................. 17
Sage Line 50 (SDO) ................................................................................................................................ 20
Supported Versions .................................................................................................................... 20
License Type ............................................................................................................................... 20
1510-008-001
2
Prerequisites .............................................................................................................................. 20
Configuration Notes ................................................................................................................... 20
Microsoft CRM ...................................................................................................................................... 22
Supported Versions .................................................................................................................... 22
License Type ............................................................................................................................... 22
CRM 4 ................................................................................................................................................ 22
Prerequisites .............................................................................................................................. 22
Configuration Notes ................................................................................................................... 22
CRM2011/2013 ................................................................................................................................. 23
Prerequisites .............................................................................................................................. 23
Configuration Notes ................................................................................................................... 23
Sales Force ............................................................................................................................................ 24
Supported Versions .................................................................................................................... 24
License Type ............................................................................................................................... 24
Prerequisites .............................................................................................................................. 24
Configuration Notes ................................................................................................................... 24
Copyright
This material is copyrighted by Kelmar Software Solutions Ltd. Any unauthorised reproductions, use
or disclosure of this material, or any part thereof, is strictly prohibited and is a violation of the
copyright laws of the United Kingdom.
Kelmar Software Solutions reserves the right to make changes in specifications at any time and
without notice. The information furnished by Kelmar Software Solutions in this material is believed
to be accurate and reliable, but is not warranted to be true in all cases.
Pentium is a trademark or registered trademark of Intel Corporation or its subsidiaries. All other
brand names and product names referenced in this document are trademarks or registered
trademarks of their respective companies.
Copyright ©2014 all rights reserved
Kelmar Software Solutions Ltd
Genesys Court
Denton Drive
Northwich
Cheshire
CW9 7LU
United Kingdom
1503-001-001
4
Revision History
Who
M. Sharps
A. Parker
J. Chapman
M. Foskett
1103-001-001
Reason
First Release
Updated for V3.5.0.0
Updated for V4.0.x.x
Updated for V4.5.x.x
When
09/09/11
01/05/12
05/03/13
30/09/14
5
Macro script language
Supported Versions
N/A
License Type
Included in MyCalls Desktop
Prerequisites
MyCalls must be installed and licensed
Configuration Notes
See ‘MyCalls Macro Script User Guide and Command Reference’ for configuration details
1103-001-001
6
Microsoft Outlook
Supported Versions
Outlook XP
Outlook 2003
Outlook 2007
Outlook 2010
Outlook 2013
License Type
Included in MyCalls Desktop
Prerequisites
Outlook is required to be installed on all clients PC’s wishing to search an Outlook/Exchange
Contacts folder.
Configuration Notes
The default outlook profile for the client PC is used by the Screen-pop.
It is only possible to use a system configuration on to contact folders that everyone has access to
and this tends to be only Exchange public folders.
The configuration dialog may take up to 15 seconds to appear on the first time of configuring
depending on the number of contact folders you have access to for your profile.
Searching a specific user’s Outlook account for contacts can only be achieved using a personal screen
pop database as other users will not have access to other peoples Outlook folders.
Outlook 2010 requires you to open the application manually before it will screen-pop.
Very large contact folders can be slow to search. To improve the performance you can elect to stop
the searching at the first found contact or import the contacts into the MyCalls Internal address
book.
1103-001-001
7
1103-001-001
8
ACT!
Supported Versions
ACT! 2005
ACT! 2006
ACT! 2007
ACT! 2008
ACT! 2009
ACT! 2010
ACT! 2011
ACT! 2012
ACT! 2013
ACT! 2014
License Type
Included in MyCalls Desktop
Prerequisites
ACT! will need to be installed on each of the client PC’s before it can be properly configured within
MyCalls.
The Configuration (below) requires you to specify
Server name: PC server name
User Name / Password: as defined during ACT! installation
Database Name: This is a database that you define when creating a database from within ACT! Using
the ACT! file->open database menu option you will normally see one or more .pad files. The
database name will be the file prefix of these .pad files. E.g. sales.pad would mean a database name
‘sales’.
ACT! Plugin folder: ACT installs plugin files during the ACT! installation process. You need to define
where on the local PC these plugin files are stored. The default is normally c:\program files\Act\Act
for windows\Plugins. Pressing the find button will attempt to find the ACT! plugins installed on your
PC.
ACT! Port: default is 10256
The plug in will automatically be added to ACT! on the first time the screen-pop configuration dialog
has connected to ACT! via the connect button.
On all client installations of ACT! the Screen-pop plug-in dll and its associated .config file are required
to be copied from the MyCalls installation directory to the ACT! plug-in directory .
C:\Program Files\NEC Infrontia\MyCalls\Act.Kelmar.Plugin.dll
C:\Program Files\NEC Infrontia\MyCalls\Act.Kelmar.Plugin.dll.config
Note that the plug-in directory may not be in the same place on each PC as it will depend on where
the ACT! application has been installed.
Configuration Notes
ACT! must be running before you can pop a record with MyCalls.
1103-001-001
9
ACT! will need to be re opened manually if it closed when using MyCalls
Searching can be carried out on Companies, Contacts or both. Separate search criteria can be
specified for Companies and Contacts. ‘Phone’ is set as the default search field.
1103-001-001
10
Goldmine
Supported Versions
Goldmine 6.7 – 9.0
License Type
Included in MyCalls Desktop
Prerequisites
Goldmine is required to be installed on every computer that wishes to search for contacts within a
Goldmine database.
Configuration Notes
Username and password entries are used when Goldmine is not running and this DLL starts the
application. If the application is already running then pressing the Connect button will always return
success regardless if the username is actually incorrect.
Phone1, phone2, phone3 are default search fields.
You can enable Goldmine to pop up a confirmation box if required.
You can optionally return focus back to the application you were using prior to the screen-pop so for
example if you were typing a word document then following the screen-pop you can be returned
back into word automatically.
1103-001-001
11
Maximizer
Supported Versions
Maximizer 9.5
Maximizer 10
Maximizer 10.5
License Type
Included in MyCalls Desktop
Prerequisites
Install Maximizer server from disk
Enter serial number
Specify Server install
Initially you can log onto the Maximizer server using the admin user and password. By Default these
are
User: MASTER
Password: CONTROL
Create a client installation of Maximizer for each of the MyCalls desktop clients and ensure
Maximizer is running on each client.
Configuration Notes
If you attempt to configure the Maximizer interface without installing Maximizer then the following
warning will occur
When installed the configuration is as shown:
1103-001-001
12
Enter username and password and click ‘Test’, only when a valid connection to the database is made
will the Maximizer fields be displayed.
Maximizer can contain a number of address books and the list is presented from which you can
select the address book you wish to search. Note these are Maximizer address books and are not
related to MyCalls address books.
Phone1, Phone2, Phone3 fields are default search fields. Searches can be carried out on Accounts,
Contacts or both.
1103-001-001
13
Sage Line 50
Sage supports two methods of connection for screen-pop purposes ODBC and SDO. Each version of
Sage provides an ODBC connection and an SDO application interface.
Whilst the SDO connection provides more functionality, the ODBC connection is simpler and faster
and for screen-pop purposes ODBC is the preferred option. In addition to this the SDO connection
requires a different interface for each version of Sage whereas the ODBC is a common interface
which simply requires the ODBC driver to be configured within the windows control panel.
Sage Line 50 ODBC
Supported Versions
Any version of Sage Line 50 that supports ODBC
License Type
Included in MyCalls Desktop
The Sage ODBC screen-pop interface is designed to operate with any version of Sage which supports
ODBC
The architecture is shown below.
The MyCalls server communicates with the Sage database(s) via ODBC. A separate ODBC system DSN
will be required for each Sage database within the organisation. The Sage data does not need to
reside on the MyCalls server but the ODBC DSN(s) must reside on the MyCalls server for the screenpop to work. In addition to configuring the ODBC DSN the Sage installation will also install a Sage
ODBC driver used by the DSN to interface to the sage database.
Each Sage Installation on the MyCalls server should automatically create an ODBC DSN and name it
according to the version of sage Installed. Additional Sage DSN's may be created manually if
required, for example you may have more than one set of sage data available within the
organisation. You will require an ODBC DSN for each Sage database.
1103-001-001
14
The MyCalls Sage ODBC configuration screen will automatically detect the DSNs and allow you to
select the required DSN from a drop down list. In order for the DSN to appear in this list it must be
created as a System DSN on the MyCalls server (see instructions below).
If you have carried out a standard Sage installation and your company data is stored in the default
location for a given version of Sage (the location can vary dependent on the version installed) then
the default DSN setup should work out of the box. However if you do a custom install and define the
location of the Sage data to be different than the default or create additional company data etc then
you will either have to modify the existing Sage DSN or create a new one.
Creating an ODBC DSN
If a Sage Client is not required on the MyCalls Server you can install the sage DSN and driver only by
using the ODBC install program found on the Sage Installation disk. Once this has been installed you
will need to configure the location of the Sage data as follows:
Select the Windows Control panel and select ODBC.
Select the System DSN tab from the configuration dialogue
Select the required Sage DSN from the list and click the configure button (or double click the DSN)
Type the path to the Sage data in the Data Path box
The path can be either:
A local path to the Sage Data
A shared network path
1103-001-001
15
A Mapped drive
The path must include the ACCDATA folder
e.g. \\SageServerPC\Accounts\2009\company.000\ACCDATA
Where ‘SageServerPC’ is the network name of the remote Sage Server and ‘Accounts’ is a shared
folder on that server
Click OK
The DSN should now be able to connect to the Sage data.
In the event that Sage is installed on the MyCalls server then the DSN will be automatically
configured to access the Local Sage data. If however the Sage Client is intended to access a remote
Sage database then you will need to modify the Sage ODBC DSN to access the remote data as
described above.
To locate the remote Sage data go to the Sage Server and Launch the Sage application.
Select Help -> About from the menu
Select the 'System Information' tab and select ‘Directories-> Data Directory’
1103-001-001
16
Copy the Data Directory information to the ODBC DSN config data path described above.
Setting up the MyCalls Screen pop Configuration screen
Having set up the Sage ODBC DSN you can then configure the MyCalls screen-pop
Select Configure->Screen-pop and click the Personal or System screen-pop dependent on
requirements
Select 'Create/Edit or Delete Screen-pop database
Click the 'Add New Database' button
From the Screen-pop configuration screen Enter a name for the new screen-pop database and
select ‘SageODBC’ from the dropdown list.
Click OK
You will be presented with the Sage ODBC configuration dialog
1103-001-001
17
Select the DSN required from the dropdown list. The data path is displayed to aid selection if you
have more than one Sage ODBC DSN to choose from
Enter the Sage Username and password
You can configure various mapping options and specify custom fields, Number masks etc. To
optimise search speed uncheck any number masks not required. With the sage ODBC databases a
number mask cannot begin with a parenthesis as this will cause an 'invalid filter error'.
1103-001-001
18
When complete click ‘OK’
Enter a number which exists in the Sage data into the Test Number box and click 'Test'
The Screen-pop viewer will return the record matching the number entered
Alternatively any errors encountered will be shown
Installing the MyCalls Sage ODBC DLL
To install the Sage ODBC dll simply copy the sageodbc.dll file into the screen-popdlls folder
Within the Mycalls Installation folder which has a default setting of:
c:\program files\ nec infrontia\mycalls\screenpopdlls
1103-001-001
19
Sage Line 50 (SDO)
Supported Versions
Sage Line 50 V12 2006
Sage Line 50 V13 2007
Sage Line 50 V14 2008
Sage Line 50 V15 2009
License Type
Included in MyCalls Desktop
Prerequisites
Install sage from disk as per sage instructions. This may entail sage on a server and several sage
remote clients
Login to Sage as user MANAGER
Add new sage user via – Settings/access rights
Enable the 3rd Party Integration option this will require a SAGE SDO (Sage data Objects) License and
activation key (contact sage for this)
Within Sage menu go to Tools->Activation->Enable 3rd party integration
Remote installation:
If required, setup a remote sage installation by carrying out an installation on a separate computer
Setup a mapped drive on the Sage client to access the remote computer Sage account data. Point
this at the root of the account data (not the ACCDATA directory)
Configuration Notes
Configuration within MyCalls is straightforward. Specify the data folder if on the local drive or if a
networked system specify the drive letter mapped to the parent of the ACCDATA directory on the
server PC. In the example below the S: drive points to the directory shown here (accessed by
pressing the browse button):
1103-001-001
20
By default the telephone1 and telephone2 fields are marked for searching. Searching can be limited
to Suppliers only, Customers only or both. Separate tabs are available so that Suppliers and
Customers can have differing search fields defined.
Several MyCalls custom fields have been mapped to some financial information regarding the
customer. This includes their credit limit, account status (open, on-hold, closed etc) and their aged
balances. If you do not wish this information to brought back and displayed, un-map the fields using
the ( <- ) button.
1103-001-001
21
Microsoft CRM
Supported Versions
Microsoft Dynamics CRM 4
Microsoft Dynamics CRM 2011
Microsoft Dynamics CMR 2013
License Type
Included in MyCalls Desktop
CRM 4
Prerequisites
Logging in to CRM4 requires users to be set up as both domain users and to have a user/security role
assigned within CRM4
To Assign a User/Security role within CRM4
 Login to CRM 4 as an administrator
 Go to settings/users
 Add the user name, userID and password plus any other details
 Go to Security roles
 Select the security roles that the user can have
 Save and log out of CRM4
Configuration Notes
 Enter the CRM Server URL e.g. http://mydomain.com:myport

Enter the business unit name with no spaces – this is not case sensitive. The business unit
name can be found within the CRM settings -> Business Units

Enter the Domain for which the user is a member – e.g. kelmar-software

Enter the ‘UserID’ and ‘password’ if you do not wish to use active directory credentials.

Click ‘Connect’
1103-001-001
22
CRM2011/2013
Prerequisites
A CRM2011/2013 account will need to be created with Microsoft.
Microsoft Windows Identity Foundation must be installed/enabled. On Windows 8 or Server 2012
(or later editions) this can be installed by turning the Windows Feature on. For other versions of
Windows this should be downloaded from Microsoft.
Configuration Notes
 Select the deployment type
 If an ‘On Premises’ deployment type then
o Enter the CRM Server URL e.g. http://mydomain.com:myport
o Enter the business unit name with no spaces – this is not case sensitive.
o Enter the Domain for which the user is a member – e.g. kelmar-software
o Enter the ‘UserID’ and ‘password’ if you do not wish to use active directory
credentials.
 If an online deployment type then
o Enter the Organisation Name
o Enter the User Name
o Enter the Password
1103-001-001
23

Click ‘Connect’
Sales Force
Supported Versions
No version information available as Sales Force is an online CRM application ( www.force.com ).
License Type
Included in MyCalls Desktop
Prerequisites
An account for the MyCalls screen-pop to log in to Sales Force needs to be created by the account
administrator.
A security token is required from Force.com. This will be emailed to the account administrator. The
security token may change from time to time; Force.com will inform the account administrator of
any changes.
Configuration Notes
Enter the account user name as provided by the administrator for use with the MyCalls Screen-pop.
In the password box, You must enter both the password for the user AND the security token
together with no spaces.
1103-001-001
24
e.g. Password for user could be Fe12DTR#01 and the security token could be
2pWg12pSL8RBWiGrxTcrYO3d.
The complete string entered into the password box will be
Fe12DTR#012pWg12pSL8RBWiGrxTcrYO3d.
You will need to be able to connect to Sales Force before you can complete the configuration.
Once you have connected to Sales Force, a list of available search and database fields will be
presented.
1103-001-001
25