Sage SalesLogix Implementation Guide
Sage SalesLogix Implementation Guide
Implementation Guide
Version 7.2
Developed by Sage SalesLogix Technical Publications
Sage SalesLogix Implementation Guide
Documentation This documentation was developed by Sage SalesLogix Technical Publications. For content
Comments revisions, questions, or comments, contact the writers at [email protected].
Disclaimer Sage Software has thoroughly reviewed this manual. All statements, technical information,
and recommendations in this manual and in any guides or related documents are believed
reliable, but the accuracy and completeness thereof are not guaranteed or warranted, and they
are not intended to be, nor should they be understood to be, representations or warranties
concerning the products described. Sage Software assumes no responsibility or liability for
errors or inaccuracies with respect to this publication or usage of information. Further, Sage
Software reserves the right to make changes to the information described in this manual at
any time without notice and without obligation to notify any person of such changes.
Technical Technical Support is available to customers who purchased their support contracts directly
Support from Sage Software, and to Certified Business Partners. Calls are answered during business
hours, Monday through Friday, excluding holidays. More information about the levels of
Technical Support available can be found on the Sage CRM Solutions Web site at http://
www.sagecrmsolutions.com/products/sagesaleslogix/support.
Customers with a valid technical support contract and a Web access code can request technical
support electronically on the Sage SalesLogix SupportOnline Web site: http://
support.saleslogix.com. Revisions to the PDF are also posted on this Web site.
Contents
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
What You Need to Know . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Planning Your Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Introduction
Sage SalesLogix is the leading customer relationship management solution that enables small
to medium-sized businesses to acquire, retain, and develop profitable customer relationships
through integrated Sales, Marketing, Customer Service, and Support automation solutions.
The Help symbol precedes online Help topic names, where you can find
additional information about features or procedures not detailed in this guide.
• Determine a method for synchronizing data between the main office and remotes (if
applicable).
• Prepare your network for Sage SalesLogix.
You can obtain a copy of the Sage SalesLogix Planning Guide on the Sage SalesLogix DVD,
from your Business Partner, from a Professional Services Group (PSG) representative, or on
Sage SalesLogix SupportOnline/Sage Software Online Support and Services at
http://www.support.saleslogix.com.
Related Documentation
In addition to the Sage SalesLogix Implementation Guide and Sage SalesLogix Planning
Guide, the following documentation is available. All documents are available on
SupportOnline/Sage Software Online Support and Services.
• The Compatibility Checklist outlines the hardware and software currently recommended
for a Sage SalesLogix implementation.
• The Sage SalesLogix Web Implementation Guide provides detailed instructions for
installing and configuring the Sage SalesLogix Web Client and other SalesLogix Web
interfaces, such as Customer Portal and LeadCapture. The Sage SalesLogix Web
Implementation Guide is available on the Sage SalesLogix DVD.
• The Sage SalesLogix LAN Developers Reference provides VBScript, COM, and SQL
functions you can use to customize Sage SalesLogix to meet your specific needs.
• The Sage SalesLogix API Reference online Help provides information about functions and
code that you can use to customize Sage SalesLogix to meet the needs of your business.
Additional resources and documentation are available on the Sage SalesLogix
SupportOnline/Sage Software Online Support and Services Web site at
http://support.saleslogix.com, and Help is available in each Sage SalesLogix application.
The Express Installation is intended for a Sage SalesLogix configuration of 5 to 25 users using
the Microsoft SQL Server database platform. If your implementation includes more than 25
users, Oracle, the Web, or Remote Offices, you should use the Standard Installation as
detailed in Part II of this guide. For Express installations, the Database Server, Sage
SalesLogix Server, and Administrative Workstation are all located on one computer.
This implementation checklist outlines the tasks you must complete to implement Sage
SalesLogix using the Express Installation (for additional configuration information and tasks
not required for an Express Installation, review the Standard Installation section of this
guide). These tasks are designed to help you organize and make decisions regarding your
Sage SalesLogix implementation. Any tasks that are recommended, but not required, are
designated as Optional.
If you are implementing Sage SalesLogix for the first time, read each chapter thoroughly to
ensure you have correctly completed the necessary steps. If you are upgrading from a
previous version, refer to the appropriate Upgrading document located in the Documentation
folder on the Sage SalesLogix DVD.
After completing the previous tasks, you can begin using Sage SalesLogix. However, you may
want to learn more about the following features to further customize your implementation.
Conflict Resolution You can define the criteria to use during synchronization to determine
what changes are kept when more than one user has changed data. See “Setting Conflict
Resolution Options” on page 84 for more information.
Dashboards Dashboards allow users to display and interact with a variety of analytical
information in a dashboard. You can set options to display data relative to a specified fiscal
calendar, the Gregorian calendar, or both. See the “Displaying the Sales Dashboard” topic in
the Sage SalesLogix Client Help for more information.
Departments You can create additional departments to assign to users. See “Creating
Departments” on page 89 for more information.
Multi-currency If your company has users in multiple countries using different currencies,
you can enable multi-currency support. See the “Managing Currency” topic in the
Administrator Help for more information.
Password Options You can set restrictions on user passwords. For example, you can require
that all users have a password (not blank). See the “Setting Password Options” topic in the
Administrator Help for more information.
Sales Processes Sales Processes are groups of steps and procedures that help users manage
their Sales pipeline. A sales process shows users the steps to complete while working to make
the sale. Processes can also prompt the user to complete activities, such as making phone
calls and writing letters. For information on creating and managing Sales Processes, see the
“Managing Sales Processes” topic in the Architect or Sage SalesLogix Client Help.
Sage SalesLogix Mobile Sage SalesLogix Mobile extends Sage SalesLogix functionality to
Pocket PC and BlackBerry devices. Sage SalesLogix Mobile provides instant access to
customer information wherever you are and exactly when you need it; all via a compact,
convenient, handheld-based application. Sage SalesLogix Mobile is add-on functionality that
requires separate installation and pricing. Contact your Sage SalesLogix representative for
more information.
SpeedSearch If necessary, you can customize the SpeedSearch indexes (requires the
SpeedSearch Server Advanced license) and index schedules. See the “Managing SpeedSearch
Indexes” and “Managing SpeedSearch Schedules” topics in the Administrator Help for more
information.
Synchronization Service Profile You can create profiles to run synchronization on a specific
schedule without an administrator logged on to the server. See “Creating a Synchronization
Service Profile” on page 119 for more information.
Teams You can create teams of users who require access to the same set of accounts. See
“Creating Teams” on page 99 for more information.
Windows Authentication With Windows Authentication, users are automatically logged on
without entering their Sage SalesLogix user names or passwords. See the “Using Windows
Authentication” topic in the Administrator Help for more information.
Before installing Sage SalesLogix, review and address the system prerequisites. This chapter
outlines the necessary requirements for a successful implementation.
Note For Express installations, the Database Server, Sage SalesLogix Server, Sync Server, and
Administrative Workstation are all located on one computer.
General Requirements
• Sage SalesLogix Planning Guide. Read this manual to help plan your entire
implementation.
• Compatibility Checklist. Refer to this document to ensure your hardware and software
meet Sage SalesLogix supported versions.
• Administrator rights for the computer on which you are installing Sage SalesLogix
components. See your Microsoft documentation for instructions on granting administrator
rights using one of the following options:
• Add each user to the local machine’s Admin group for the duration of the
implementation.
• Use a domain user account that is a member of the domain admin group for the
duration of the implementation.
You do not need administrator rights to run the Sage SalesLogix Client, Sync Client, or Mail
Client.
• Latest supported Windows Service Pack. Install the latest supported service pack for your
Windows platform, available from Microsoft at www.microsoft.com.
• MDAC (Microsoft Windows versions earlier than Vista) or Microsoft DAC (Windows Vista).
Microsoft Data Access Components are required on every computer running Sage
SalesLogix.
• Microsoft SQL Express installed on the Administrative Workstation. Microsoft SQL Express
is required if you have a Microsoft SQL Server 2000 database and there will be Remote
users created, or if the Resync utility will be used.
If Microsoft SQL Express is installed with Sage SalesLogix, it installs as a SALESLOGIX
instance with the sa password set to SLXMaster. If you install Microsoft SQL Express from
another source, you must set the sa password to SLXMaster (it is generally blank). To
install Microsoft SQL Express with the same configuration settings as Sage SalesLogix, use
one of the following files on the Sage SalesLogix DVD:
• For the Administrative Tools and Servers installation, run ...\SQLExpress\setup.exe
/settings "...\<SQLExpress>\Administrative Tools and Servers.ini"
• For the Sage SalesLogix Client installation, run ...\SQLExpress\setup.exe /settings
"...\<SQLExpress>\SalesLogix Client.ini".
• Microsoft .NET Framework. .NET Framework is required for .NET Extensions on the
Administrative Workstation, Architect, and Sage SalesLogix Client computers.
The Sage SalesLogix installation automatically installs .NET if the Framework is not
detected on the computer where you are installing Sage SalesLogix.
• Microsoft Windows Installer. Windows Installer is required for use with .NET Framework.
The Sage SalesLogix installation automatically installs Windows Installer if it is not
detected on the computer where you are installing Sage SalesLogix.
• TCP/IP installed and configured on every computer running Sage SalesLogix. TCP/IP is
required as the network communication protocol.
• Microsoft Internet Explorer. You must install Internet Explorer on every computer running
Sage SalesLogix. Refer to the Compatibility Checklist for supported versions.
• Microsoft Collaboration Data Objects. If you plan to run agents with e-mail output, you
must install the Collaboration Data Objects (CDO.dll) on your Sync Server.
• For Outlook XP, Collaboration Data Objects can be installed from the Control Panel >
Add or Remove Programs > MS Office > Change > Add or Remove Features >
Microsoft Outlook > Collaboration Data Objects > Run from My Computer.
• For Outlook 2007, download Collaboration Data Objects version 1.2.1 from the
Microsoft Web site at www.microsoft.com.
• Microsoft Word. You must install Word on the Administrative Workstation (or the
computer on which you install Architect) for template management and on each Sage
SalesLogix Client computer for mail merge.
• Crystal Reports Professional. If you plan to create or edit reports, you must install Crystal
Reports on the Administrative Workstation (or the computer on which you install
Architect) for report management.
The Crystal Reports installation is available as an option on the Sage SalesLogix DVD
browser.
• Mail client configured on the Administrative Workstation.
• Adobe Acrobat Reader. Required to view Sage SalesLogix documentation.
• No debuggers, programs, or screen savers running. Close all programs and turn off all
debuggers, screen savers, or anti-virus programs that may interfere with the installation.
For Visual Studio installed with Microsoft SQL Server 2005, launch Visual Studio > Tools >
Options > Debugging > Just-In-Time > and clear all three options.
Server Requirements
In addition to the “General Requirements” in the previous section, ensure the Server
computer(s) meet the following requirements.
• Microsoft SQL Server. Your database platform must be installed and running on the
Database Server.
Note By default, Sage SalesLogix uses the OLE DB Provider installed with MDAC v2.8. If your
implementation uses the SQL 2005 Native OLE DB Provider, you must install that provider
on any computer where Sage SalesLogix is installed.
• SQL Server Sort Orders set to 52 or 54. To check sort order information, type sp_helpsort
in SQL Server Query Analyzer.
• Sort Order 52 - Dictionary order, case-insensitive, for use with the 1252 character
set.
• Sort Order 54 - Dictionary order, case-insensitive, accent-insensitive, for use with the
1252 character set.
• SQL Server security set to SQL Server and Windows authentication.
To change the authentication mode, open Enterprise Manager, right-click the appropriate
server, and then click Properties. On the Security tab, set the Authentication to SQL Server
and Windows.
• Microsoft SQL Server Client and Server component versions match. For example, if the
Connection Manager uses the Microsoft SQL Server 2005 driver, then the Sage SalesLogix
Clients must use the 2005 driver.
• SYSDBA user is not assigned the System Administrators role. If the System
Administrator’s role within Microsoft SQL Server is selected for the SYSDBA user, you
cannot log on to Sage SalesLogix.
Client Requirements
In addition to the “General Requirements” on page 9, ensure the following are set up on each
Client computer.
• Microsoft SQL Express or Microsoft SQL Server. For Remote Clients only, Microsoft SQL
Express or Microsoft SQL Server must be installed. See the Compatibility Checklist for
supported versions.
If Microsoft SQL Express is installed with Sage SalesLogix, it installs as a SALESLOGIX
instance with the sa password set to SLXMaster. If you install Microsoft SQL Express from
another source, you must set the sa password to SLXMaster (it is generally blank). To
install Microsoft SQL Express with the same configuration settings as Sage SalesLogix, use
one of the following files on the Sage SalesLogix DVD:
• For the Administrative Tools and Servers installation, run ...\SQLExpress\setup.exe
/settings "...\<SQLExpress>\Administrative Tools and Servers.ini"
• For the Sage SalesLogix Client installation, run ...\SQLExpress\setup.exe /settings
"...\<SQLExpress>\SalesLogix Client.ini".
• Microsoft Outlook. You must install Outlook if you are using Outlook Integration. Ensure
Outlook is installed and configured before installing Sage SalesLogix.
See “Outlook Integration Requirements” in the following section for additional requirements.
• Small Fonts/Normal Size. Ensure the user’s Windows’ Display settings are set to Small
Fonts or Normal Size (the name of the option varies depending on which version of
Windows is installed).
To access this setting from the Windows Control Panel, double-click Display. On the
Settings tab, click Advanced.
• Data Execution Prevention (DEP) for essential Windows programs and services only. If
you are running Sage SalesLogix on Windows Vista, ensure this setting is enabled.
To access this setting, right-click My Computer > Properties > System Properties >
Advanced tab > Performance > Settings > Performance Options > Data Execution
Prevention tab > Turn on DEP for essential Windows programs and services only.
• Use User Account Control (UAC) to help protect your computer. If you are running Sage
SalesLogix on Windows Vista, ensure this setting is disabled.
To access this setting from the Windows Control Panel, double-click User Accounts and
then click the Turn User Account Control on or off hyperlink.
SpeedSearch Requirements
In addition to the “General Requirements” on page 9, ensure the following requirement is met
if your implementation includes SpeedSearch running on Windows Vista Business Edition.
• Admin user configured to run the SpeedSearch Service. If the SpeedSearch Service is
installed on a machine with Windows Vista Business Edition, the Local System Account
does not have enough inherited permissions to run the service.
• Set Internet Security. If your company uses Windows 2003, you must adjust the default
Internet Security setting in order for the Outlook Integration menu and toolbar items to
display.
To adjust security, open Internet Explorer. On the Tools menu, click Internet Options, click
the Security tab, and then set the Security level for the Internet zone to any setting other
than High.
• Download the WinHelp Engine (WinHlp32.exe). If you are running Sage SalesLogix on
Windows Vista and will synchronize information using Intellisync for Sage SalesLogix, you
must download the WinHelp engine to access the Online Help. Windows Vista does not
include the Help engine necessary for viewing the Intellisync for Sage SalesLogix Help.
Refer to the Microsoft Web site for download information.
The Express Installation installs the following components. In addition, the installation
creates and shares the default system folders.
• Sage SalesLogix Databases (Microsoft SQL Server)
• Sage SalesLogix Server
• Administrator
• Architect
• Sage SalesLogix Utilities
• SpeedSearch Service
• Synchronization Service
For more information on system components, see the Sage SalesLogix Planning Guide.
• If you are installing on Windows XP or 2003 Server, you must share the Sync Logs folder (created
during the installation) and set security to Full Control. The Sync Logs folder is created in \\My
Server\Sync Logs.
• To enable SpeedSearch to function correctly, you must place all files and folders to be included in
the default indexes in the C:\Program Files\SalesLogix\SpeedSearch\TextFile folder on the computer
to which you installed Sage SalesLogix. If you plan to customize the SpeedSearch indexes to include
files located on another computer, you must change the Local System Account to a Network user.
See “Server Requirements” on page 62 for more information about creating a Network user
(SLXService) with the necessary access. See “Managing SpeedSearch Indexes” in the Administrator
Help for more information on customizing SpeedSearch indexes.
Once you have installed the components necessary for your implementation, you must log on
to the Administrator and complete the following tasks:
• Add licenses.
• Enter Office information.
• Configure Sage SalesLogix options.
• Add Customer Service and/or Support information (if you are using the customer service
and/or support features).
Adding Licenses
All implementations require a Sage SalesLogix license (Standard, Advanced, or Premier).
Additional licenses determine the servers, offices, and users you can add to Sage SalesLogix.
See the Sage SalesLogix Planning Guide for a description of each available license.
The first time you log on to a Sage SalesLogix database that does not contain licenses, the
Setup Assistant appears.
To add office information without using the Setup Assistant, see the “Entering Office
Information” topic in the Administrator Help.
Adding Users
The last step of the Setup Assistant simplifies the process of adding Sage SalesLogix users.
The process for adding users is detailed in Chapter 5, “Configuring Sage SalesLogix Users.”
• Complete the information in the following sections to configure your Sage SalesLogix system. Then
use the processes detailed in Chapter 5, “Configuring Sage SalesLogix Users” to add users.
• Refer to Chapter 5, “Configuring Sage SalesLogix Users” to add users. Then return to the
following sections to complete your Sage SalesLogix system configuration.
Refer to the “Configuring SalesLogix Options” topic in the Administrator Help for
information on other options.
6. Select when you want the Data Transformation Services (DTS) file and Remote database
to be created:
• Prepare Remote DB and create it immediately automatically creates and runs
the DTS file. The DTS file creates the Remote database. This is the recommended
option.
• Prepare Remote DB and wait for Administrator creates and saves the DTS file.
This enables you to run the DTS file and create the database at a later time. This
setting is not recommended. This method requires a user interface and scheduler to
connect to the database and run the DTS package.
7. Click OK.
See the “Setting Accounting Options” topic in the Administrator Help for details.
9. Click OK.
When creating Sage SalesLogix users, you must add new users and modify the user profile.
Creating Users
Before creating users, determine the best method of configuring the user’s profile for your
company’s size and structure.
If you plan to add several users with identical profiles (for example, the same department,
division, manager, security settings, and so on), Sage SalesLogix recommends you use a user
template. Templates are recommended because they significantly reduce administration
time.
When creating users, you can apply a Sage SalesLogix user template, or a custom template
you create, which applies the appropriate settings to each user. User templates do not
consume a license and cannot log on to Sage SalesLogix.
For detailed information on default Sage SalesLogix user templates, see the “Creating a User
Template” topic in the Administrator Help. If necessary, you can customize the default
templates.
The following sections detail how to add users based on existing Windows’ users, and then
how to complete and activate the new users. For information on creating user templates,
refer to “Creating User Templates” on page 92.
For information on other methods of adding users, see the “A New Employee Needs Access to
Sage SalesLogix” topic in the Administrator Help.
10. If you want to import information from Windows’ Active Directory to each user’s profile,
ensure Update SalesLogix user information with Windows information is selected.
Otherwise, clear this check box.
For more information on importing from Active Directory, see the “Importing Additional User
Information from Windows” topic in the Administrator Help.
11. If you want to enable Windows Authentication (single log-on) for the selected users,
ensure Use Windows Authentication is selected. If you simply want to import the
users, clear this option (in this case users will be required to log on to the Sage
SalesLogix Client unless you enable Windows Authentication in each user's profile).
Configuring Users
If you create a user from a template, from an existing Windows’ user, or import the user
information from another application, you must complete additional configuration steps
before the user can log on.
1. On the Administrator Navigation Bar, click Users.
2. In the Users view, double-click a user to open the profile.
3. If necessary, select the Use Windows Authentication check box. In the Windows ID
box, select the name the user enters to log on to Windows.
With Windows Authentication, users are automatically logged on without entering their
Sage SalesLogix user names or passwords.
4. In the Username box, type the name the user will use when logging on to Sage
SalesLogix.
The user name is required and cannot contain spaces or an apostrophe. For Remote users,
the user name must also follow the Rules for Regular Identifiers specific to the version of
Microsoft SQL Server that you are using to create Remote databases. The Remote user
name must follow these rules as it is sent to the Microsoft SQL Server or Microsoft SQL
Express to be used as part of a Remote database name.
You can install the Sage SalesLogix Client using one of two methods.
Automated installation Automated installations create an executable file that allows the
Sage SalesLogix Client to be installed with no user intervention.
Automated installations reduce administration time when you upgrade to a new version, and
then add new users to Sage SalesLogix. During the upgrade process, you can update the
Client installation images directly from the upgrade wizard. Then when you add new users
and install Sage SalesLogix, the installation includes all service packs and upgrades that are
installed on your system.
Important When installing the Sage SalesLogix Client using an automated installation, third-party
applications are not installed. This includes Intellisync for Sage SalesLogix (Network
and Remote Client) and Microsoft SQL Express (Remote Client). Third-party
applications must be installed separately, and can be found in the Redist folder on
the Sage SalesLogix DVD.
Standard Sage SalesLogix Client installation The Sage SalesLogix Client can be installed
on each user’s computer using the Client installation. The standard installation includes
Typical and Custom options which allow you to install all components or choose the
components necessary for your implementation.
• In the SalesLogix Server box, select or type the name of the computer on which
you installed the Sage SalesLogix Server.
This setting is not available if you are creating a Sage SalesLogix Remote Client
installation.
• In the SalesLogix Database Alias box, select or type the name of the database
connection.
This setting is not available if you are creating a Sage SalesLogix Remote Client
installation.
• If necessary, in the Port box, change the port number used for communication
between the client and the Sage SalesLogix Server.
In most implementations, the default port number does not need to be changed.
However, if you have another application or service using port 1706, you should
change the port number to an unused port.
6. In the Network Location box, type or browse to the location where the automated
installation should be created.
This location must be a shared network path.
7. On the remaining screens, click Install and Finish to complete the installation.
The automated installation is created in the specified shared network location and a
shortcut to the installation is created on the desktop.
8. Distribute the shortcut or installation to users.
If your company uses Lotus Notes or GroupWise, see the “Setting Sync Preferences for Outlook
and Intellisync” topic in the Sage SalesLogix Client Help for step-by-step configuration
instructions.
By default, the Intellisync for Sage SalesLogix configuration files are created in the
...\Program Files\SalesLogix\SlxIntellisync folder. If necessary, you can change this location
after installation. This may be necessary if you are running Sage SalesLogix in a Citrix
environment. See the “Changing the Intellisync Default Installation Path” topic in the
Administrator Help for detailed instructions.
or proceed to “Adding Address Lists to the Outlook Addressing Tab” on page 32 if you want
users to have the ability to perform Sage SalesLogix Contact name resolution in Outlook.
3. In the Sync Configuration area, click Configure. The Intellisync for SalesLogix
Configuration dialog box appears.
You do not need to click the Login button for configuring the sync options unless you plan
to use several databases. The first time the sync options run, you will be prompted for the
database login.
4. To configure contact synchronization, select Contacts.
5. In the Choose Translator dialog box, do the following:
a. Select MS Outlook.
b. Ensure Synchronize is selected in the Operation area.
c. Click OK.
6. Click Configure and then click Advanced Settings.
7. In the Advanced Settings for Contacts dialog box, click the Filters tab, and then click
New.
8. In the Filter Name dialog box, type SyncSalesLogix, being sure to capitalize it exactly
as shown, and then click OK.
9. On the Conditions tab, complete the following:
a. Click Field, and then select Categories from the list.
b. In the Operator box, select contains.
c. In the Value box, type SyncSalesLogix, being sure to capitalize it exactly as shown.
d. Click Add to List, and then click OK.
The Advanced Settings for Contacts dialog box reappears, displaying the Filters tab. Notice
that SyncSalesLogix is added to the list of available filters.
10. Ensure SyncSalesLogix is selected, and then click OK.
The Intellisync for SalesLogix Configuration dialog box appears. Notice that "Contacts
Filtering with SyncSalesLogix" appears on the right side.
11. If you want to set up synchronization for other items, such as appointments (meetings
and phone calls), events, timeless appointments, or to-dos, select the item, and then
click Choose. Repeat Step 5 to select the translator, and then repeat steps 6 through 10.
If you do not set up synchronization for timeless appointments, any existing timeless
appointments are included on both the Sage SalesLogix and Outlook calendars. However,
updates and new timeless appointments are not synchronized.
12. Click OK to close Intellisync for SalesLogix Configuration.
13. In the Confirmation Options area of the Outlook Synchronization tab, Ignore all
confirmation items is selected by default. If you want to receive a confirmation message
when items are synchronized (not recommended), clear this check box.
14. In the Sync Run Options area of the Outlook Synchronization tab, under Calendar
Activities and Contacts, select the options that apply to your sync preferences.
For example, if Automatically (after any activity changes) is selected, automatic
synchronization with Outlook is triggered when you delete an activity in Sage SalesLogix.
15. When all settings are complete, click OK.
2. On the Edit menu, click Categories, and then click Master Category List.
3. In the New category box, type SyncSalesLogix. Capitalize it exactly as shown.
4. Click Add, and then click OK.
5. In the Categories dialog box, click OK.
6. From the Contacts view, double-click a contact that you want to synchronize, and then
click Categories.
7. In the Categories dialog box, select SyncSalesLogix, and then click OK.
8. You can continue assigning the SyncSalesLogix category to Outlook contacts by
repeating steps 6 and 7.
Note The SyncSalesLogix filter is used when synchronizing contacts. It is not necessary to use
this filter when you are exporting contact information to Outlook.
See the “Setting Sync Preferences for Outlook and Intellisync” topic in the Sage SalesLogix
Client Help for information on adding Sage SalesLogix Contacts to Outlook.
The Area, Category, and Issue lists are linked in a hierarchy. The Area you select determines
the options available for the Category, and the Category you select determines the options
available for the Issue.
The Area, Category, and Issue lists are used to reduce administration time when users are
creating tickets and defects. If you are not using the customer service or support features,
you do not need to create the area, category, and issue lists.
Marketing is fully integrated in the Sage SalesLogix Client and requires no additional
configuration. If you want to use the additional functionality provided by Marketing Services,
you must configure the Marketing Services Configuration Manager, create a Marketing
Services account, and then create a Marketing Services user.
If your implementation does not include Marketing Services, proceed to Chapter 8,
“Configuring the Synchronization Server”.
Note Marketing Services is a regional option and may not be available in all locations.
d. If your Sage SalesLogix Server is not directly connected to the Internet, select the
Use a SOCKS proxy check box, and complete the following information.
• In the Host box, type the computer name, IP address, or URL of the computer
that hosts the SOCKS server.
• In the Port box, type the SOCKS server port number.
• In the Authentication box, select saUsernamePassword if an account and
password are required to log on to the SOCKS server. Select
saNOAuthentication if an account and password are not required.
• In the Version box, select your SOCKS version number.
• In the Account name box, type the SOCKS account name (if you selected
saUsernamePassword in the Authentication box).
• In the Password box, type the SOCKS password (if you selected
saUsernamePassword in the Authentication box).
e. Click the Notifications tab.
4. On the Notifications tab, configure your settings for the SMTP server that is used to
send e-mail notifications regarding the processing of batch jobs that are scheduled using
the Sage SalesLogix Client. You can also configure the recipients of e-mail notifications.
a. Select the Send e-mail notifications check box if you want EmPulse to send
notifications regarding successes, failures, and so on. If you do not want to send e-
mail notifications, proceed to step 5.
b. Select the Login required check box if you want to be prompted to log on to the
SMTP server before notifications are sent.
If a login is required, set the Account name and Password used to log on to the SMTP
Server in the appropriate boxes.
c. In the SMTP host box, type the SMTP address of the SMTP Host Server.
d. In the SMTP port box, select the port number on which the SMTP Server
communicates with Sage SalesLogix.
e. Select the Include details of failed Service imports and exports check box if you
want detailed error reports when transactions between EmPulse and Sage SalesLogix
fail.
f. Under E-mail Recipients, select the Campaign manager box if you want to send
e-mail notifications to the manager of the campaign as assigned in Sage SalesLogix.
g. Select Request owner to send e-mail notifications to the user that scheduled the
request in Sage SalesLogix.
h. Select Service account owner to send e-mail notifications to the individual that
owns the account with EmPulse. For example, this may be a Business Partner or
some company executive not associated with the campaign in Sage SalesLogix.
i. Select the Other address check box to manually add e-mail addresses to which you
want to send e-mail notifications. Use the Other addresses grid to add additional e-
mail addresses.
j. Click the Scheduling tab.
5. On the Scheduling tab, set schedules for downloading and processing information from
EmPulse.
a. In the Download Responses On section, select which days of the week you want to
receive responses from EmPulse.
b. If necessary, select Limit polling and set a time that you want to connect to
EmPulse during the selected day(s).
When this option is selected, Sage SalesLogix only attempts to connect with EmPulse
during that time of the day.
c. Click the Options tab.
6. On the Options tab, select when you want to receive error messages and other
processing options.
• In the Windows Event Logging section, select the events for which you want to
receive error messages.
• Errors creates a log if a significant problem occurs, such as loss of data or loss of
functionality.
• Warnings creates a log if an event occurs that is not necessarily significant, but
may indicate a possible future problem.
• Information creates a log that describes the actions taken by the service. This
can be used for troubleshooting problems.
• If necessary, select the Only process responses for active SalesLogix
campaigns check box.
When this option is selected, response information is only received from EmPulse for
campaigns in Sage SalesLogix that are currently active.
• Select the Map User fields to EmPulse Custom fields check box to automatically
map Userfield1 - Userfield10 in the Sage SalesLogix CONTACT and LEAD tables to the
Custom 11 - Custom 20 fields in the EmPulse database.
7. Click OK to close the Configuration Manager.
3. In the SalesLogix User box, select the user that will access the marketing services
account.
If you want to automatically import campaign responses associated with this user, select
the Automatically import responses for this user check box. If this option is not selected,
the user must perform dynamic imports to analyze responses.
4. Under Service Login, the Primary option is selected.
When adding the first Marketing Services user, the Service Login section is disabled. There
must always be a primary account and the first user defaults to that primary account. If
additional Marketing Services users are added, you can select the Use Primary option to
use the Primary credentials when communicating with EmPulse. The Secondary option
allows the user to access an account other than the primary. For example, you may want
to use one account for your Sales department and another for your Marketing department.
5. In the Owner E-mail box, type the e-mail address of the EmPulse account owner. This
option is necessary only if the Service account owner check box is selected in the E-
mail Recipients section of the Notification tab on the Marketing Services Configuration
Manager.
The e-mail address must be an SMTP address. Use the format [email protected] or
“Some Name <[email protected]>".
6. Click OK.
Synchronization Server refers to both the software that runs synchronization and the
hardware on which the server is installed. A Sync Server is only necessary if you have Sage
SalesLogix Remote Clients or you plan to run agents.
Use the Sage SalesLogix Planning Guide to understand the synchronization process in detail
and to make decisions regarding your synchronization requirements.
For FTP performance tips, see the “Improving FTP Synchronization Performance” topic in the
Administrator Help.
11. In the Infiles, Outfiles, and FailedTrans boxes, type the Infiles, Outfiles, and
FailedTrans folder names on your FTP server (for example, /Infiles, /Outfiles, and
/FailedTrans).
Creating the Infiles folder is outlined in “Setting Up a Sage SalesLogix FTP Site” on page 40.
12. Under Login:
• Click Login and password below to assign the same login and password to the
Sync Server and all Remote users. Then in the Login box, type the general login that
is shared by all Remote users and Sync Server(s) when logging on to the FTP site. In
the Password box, type the corresponding password. Then, click OK.
If you choose to use a global login, you can use the default anonymous user that
comes with FTP. This user is already configured with the necessary permissions. This
user has a Login of anonymous, and the corresponding Password is your domain name.
• Click Personal login and password to assign a different login and password to each
Sync Server and Remote user. Then, click OK.
Use the FTP Sync Transport Local Options dialog box to set the login for the sync
server. Personal logins for Remote users are set in the individual’s user profile. The
instructions for configuring the user login are in Chapter 9, “Configuring the Sage
SalesLogix Remote Client.”
13. If you selected the Personal login and password option, in the Edit Sync Transfer
Profile dialog box, click Server Settings. In the Login and Password boxes, type the
Sync Server’s login and corresponding password to the FTP site.
14. Click OK.
9. In the Alternate Site box, type an alternate HTTP Server for file transfer.
If the Sync Client cannot connect using the primary Web Site, it attempts to use the
alternate site.
10. In the Port box, type the alternate site’s port number on the HTTP Server.
11. If necessary, select the Secure Comm (SSL) check box if you are using a secure
connection for your alternate site.
12. In the Infiles, Outfiles, and FailedTrans boxes, type the Infiles, Outfiles, and
FailedTrans folder names on your HTTP server (for example, /Infiles, /Outfiles, and
/FailedTrans).
Creating the Infiles, Outfiles, and FailedTrans folders is outlined in “Setting Up a Sage
SalesLogix HTTP Site” on page 42.
13. Under Login:
• Click Login and password below to assign the same login and password to the
Sync Server and all Remote users. Then in the Login box, type the general login that
is shared by all Remote users and Sync Server(s) when logging on to the HTTP
Server. In the Password box, type the corresponding password. Then, click OK.
• Click Personal login and password to assign a different login and password to
each Sync Server and Remote user. Then, click OK.
Use the HTTP Sync Transport Local Options dialog box to set the login for the Sync
Server. Personal logins for Remote users are set in the individual’s user profile. The
instructions for configuring the user login are in Chapter 9, “Configuring the Sage
SalesLogix Remote Client.”
14. If you selected the Personal login and password option, in the Edit Sync Transfer
Profile dialog box, click Server Settings. In the Login and Password boxes, type the
Sync Server’s login and corresponding password to the HTTP Server.
15. Click OK.
The first time you log on to the Monitor Console, you must set the name of the Sync Server
computer. Then you must register the synchronization service(s) to view data. This process is
detailed in the Monitor Console Help.
By default, the Monitor Console is installed in C:\Program Files\SalesLogix. To open the
Monitor Console, double-click SlxMonitorConsole.exe.
Remote Clients keep a subset of the main office database on their local computer (a laptop,
for example) and use synchronization to transfer changes between their system and the main
office. To synchronize data, the main office and each Sage SalesLogix Remote Client must
have a set of synchronization folders on their computers and have the ability to transfer files.
Remote users can also connect directly to the main office database using a LAN or WAN
connection.
Using Subscription
There are two ways to subscribe to accounts:
• Use subscription rules to request accounts based on specific criteria or conditions.
• As needed, use manual account subscription to select accounts using the Administrator or
Sage SalesLogix Remote Client.
For detailed instructions to create subscription rules, refer to the “New Subscription Rule or
Template” topic in the Administrator Help.
b. To set a date limit, select Files Added Within Last, and then type in a number of
days.
When this value is set, any attachments older than the specified value will not
automatically synchronize to the Remote. The Remote user can request the
attachment, but it will not be sent when creating a Remote database or during the
normal synchronization process.
c. To apply these options to all Remote users, click All Users.
d. Click OK.
3. Each database is placed in the folder specified in the Create Remote DB in server
directory box on the Database tab of the Options dialog box. To create the database(s),
do one of the following.
• To create the database(s) immediately, click Now.
• To create the database(s) at a later time, click Later.
• In the calendar, select a date and time, and then click OK.
The Administrator is unavailable when the timer is active.
• The Create Databases dialog box displays a countdown to the scheduled date
and time.
A test is performed to ensure the settings are configured and that the database can
be created in the chosen location.
The database is created with the file name SLX_userid_dat.sxd.
4. Click OK to confirm successful completion.
If the Remote user’s computer is connected to the network, create a folder on the
Administrative Workstation and copy the database to the folder. Share this folder so that the
Remote user’s computer has access to it.
If the Remote user is not connected to the network, copy the database to the user’s
computer using some form of removable media. Another option is to zip the database, e-mail
it to the Remote user, and instruct the user to copy it to his or her computer and unzip it.
For more information on automated synchronization, see the “Sage SalesLogix Synchronization
Client” topic in the Sage SalesLogix Client Help.
• Once at - Select the time of day that you want to update all enabled indexes.
• Repeat Every - Select or type how often you want all enabled indexes to be
updated.
5. Click OK.
The Standard Installation is intended for Sage SalesLogix implementations that have more
than 25 users, run on an Oracle database, access Sage SalesLogix over the Web, or include a
Remote Office(s).
This implementation checklist outlines the tasks you must complete to implement Sage
SalesLogix using the Standard Installation. These tasks are designed to help you organize
and make decisions regarding your Sage SalesLogix implementation.
If you are implementing Sage SalesLogix for the first time, read each chapter thoroughly to
ensure you have correctly completed the necessary steps. If you are upgrading from a
previous version, refer to the appropriate Upgrading document located in the Documentation
folder on the Sage SalesLogix DVD.
Required Tasks
All Standard implementations require the following tasks to be completed. Any tasks that are
recommended, but not required, are designated as Optional.
Synchronization Tasks
In addition to the “Required Tasks” on page 57, the following tasks are required for all
implementations that include Remote users or Remote Offices. If your implementation does
not include Remotes, the following do not apply. Any tasks that are recommended, but not
required, are designated as Optional.
After completing the previous tasks, you can begin using Sage SalesLogix. However, you may
want to learn more about the following features to further customize your implementation.
Dashboards Dashboards allow users to display and interact with a variety of analytical
information in a dashboard. You can set options to display data relative to a specified fiscal
calendar, the Gregorian calendar, or both. See the “Displaying the Sales Dashboard” topic in
the Sage SalesLogix Client Help for more information.
Multi-currency If your company has users in multiple countries using different currencies,
you can enable multi-currency support. See the “Managing Currency” topic in the
Administrator Help for more information.
Password Options You can set restrictions on user passwords. For example, you can require
that all users have a password (not blank). See the “Setting Password Options” topic in the
Administrator Help for more information.
Sales Processes Sales Processes are groups of steps and procedures that help users
manage their Sales pipeline. A sales process shows users the steps to complete while
working to make the sale. Processes can also prompt the user to complete activities, such as
making phone calls and writing letters. For information on creating and managing Sales
Processes, see the “Managing Sales Processes” topic in the Architect or Sage SalesLogix
Client Help.
Sage SalesLogix Mobile Sage SalesLogix Mobile extends Sage SalesLogix functionality to
Pocket PC and BlackBerry devices. Sage SalesLogix Mobile provides instant access to
customer information wherever you are and exactly when you need it; all via a compact,
convenient, handheld-based application. Sage SalesLogix Mobile is add-on functionality that
requires separate installation and pricing. Contact your Sage SalesLogix representative for
more information.
Windows Authentication With Windows Authentication, users are automatically logged on
without entering their Sage SalesLogix user names or passwords. See the “Using Windows
Authentication” topic in the Administrator Help for more information.
Before installing Sage SalesLogix, review and address the system prerequisites. This chapter
outlines the necessary requirements and the files and folders that must be created for a
successful implementation.
General Requirements
• Sage SalesLogix Planning Guide. Read this manual to help plan your entire
implementation.
• Compatibility Checklist. Refer to this document to ensure your hardware and software
meet Sage SalesLogix supported versions.
• Administrator rights for the computer on which you are installing Sage SalesLogix
components. See your Microsoft documentation for instructions on granting administrator
rights using one of the following options:
• Add each user to the local machine’s Admin group for the duration of the
implementation.
• Use a domain user account that is a member of the domain admin group for the
duration of the implementation.
You do not need administrator rights to run the Sage SalesLogix Client, Sync Client, or Mail
Client.
• Sage SalesLogix database is placed in its own instance. This applies to Oracle
implementations only.
• Latest supported Windows Service Pack. Install the latest supported service pack for your
Windows platform, available from Microsoft at www.microsoft.com.
• MDAC (Microsoft Windows versions earlier than Vista) or Microsoft DAC (Windows Vista).
Microsoft Data Access Components are required on every computer running Sage
SalesLogix.
If your Database Server contains only the Sage SalesLogix database and no other Sage
SalesLogix components, you do not need to install MDAC/Microsoft DAC on that server.
• Microsoft SQL Express installed on the Administrative Workstation. Microsoft SQL Express
is required if you have a Microsoft SQL Server 2000 or Oracle database and there will be
Remote users or Remote Offices created, or if the Resync utility will be used.
If Microsoft SQL Express is installed with Sage SalesLogix, it installs as a SALESLOGIX
instance with the sa password set to SLXMaster. If you install SQL Express from another
source, you must set the sa password to SLXMaster (it is generally blank). To install SQL
Express with the same configuration settings as Sage SalesLogix, use one of the following
files on the Sage SalesLogix DVD:
• For the Administrative Tools and Servers installation, run ...\SQLExpress\setup.exe
/settings "...\<SQLExpress>\Administrative Tools and Servers.ini"
• For the Sage SalesLogix Client installation, run ...\SQLExpress\setup.exe /settings
"...\<SQLExpress>\SalesLogix Client.ini".
• Microsoft .NET Framework. .NET Framework is required for .NET Extensions on the
Administrative Workstation, Architect, and Sage SalesLogix Client computers.
The Sage SalesLogix installation automatically installs .NET if the Framework is not
detected on the computer where you are installing Sage SalesLogix.
• Microsoft Windows Installer. Windows Installer is required for use with .NET Framework.
The Sage SalesLogix installation automatically installs Windows Installer if it is not
detected on the computer where you are installing Sage SalesLogix.
• TCP/IP installed and configured on every computer running Sage SalesLogix. TCP/IP is
required as the network communication protocol.
• Microsoft Internet Explorer. You must install Internet Explorer on every computer running
Sage SalesLogix. Refer to the Compatibility Checklist for supported versions.
• Microsoft Collaboration Data Objects. If you plan to run agents with e-mail output, you
must install the Collaboration Data Objects (CDO.dll) on your Sync Server.
• For Outlook XP, Collaboration Data Objects can be installed from the Control Panel >
Add or Remove Programs > MS Office > Change > Add or Remove Features >
Microsoft Outlook > Collaboration Data Objects > Run from My Computer.
• For Outlook 2007, download Collaboration Data Objects version 1.2.1 from the
Microsoft Web site at www.microsoft.com.
• Microsoft Word. You must install Word on the Administrative Workstation (or the
computer on which you install Architect) for template management and on each Sage
SalesLogix Client computer for mail merge.
• Crystal Reports Professional. If you plan to create or edit reports, you must install Crystal
Reports on the Administrative Workstation (or the computer on which you install
Architect) for report management.
The Crystal Reports installation is available as an option on the Sage SalesLogix DVD
browser.
• Mail client configured on the Administrative Workstation.
• Adobe Acrobat Reader. Required to view Sage SalesLogix documentation.
• Required hardware and software for Web components. See the Sage SalesLogix Web
Implementation Guide for complete details.
• No debuggers, programs, or screen savers running. Close all programs and turn off all
debuggers, screen savers, or anti-virus programs that may interfere with the installation.
For Visual Studio installed with Microsoft SQL Server 2005, launch Visual Studio > Tools >
Options > Debugging > Just-In-Time > and clear all three options.
Server Requirements
In addition to the “General Requirements” on page 61, ensure the Server computer(s) meet
the following requirements.
• Microsoft SQL Server or Oracle (See the Compatibility Checklist for details on supported
versions). Your database platform must be installed and running on the Database Server.
When installing Oracle, ensure that the Oracle OLE DB Provider is installed.
Note By default, Sage SalesLogix uses the OLE DB Provider installed with MDAC v2.8. If your
implementation uses the SQL 2005 Native OLE DB Provider, you must install that provider
on any computer where Sage SalesLogix is installed.
• Local System Account or SLXService user. The default Windows’ Local System Account
includes the privileges necessary for Sage SalesLogix services. However, if you have
changed the Local System Account or prefer to specify a different user, create the
SLXService user as follows:
Note If you plan to run Agents, the Local System Account cannot be used to log on and cycle the
Sync Server the first time. You must use a Domain account to log on and run a manual
synchronization cycle in order for Agents to work correctly.
• Create the SLXService user in your company’s domain. This is the security domain for
the area of the network where the Sage SalesLogix Server, SpeedSearch Service,
and Synchronization Service are located.
• Add the SLXService user to the local Administrators group on the Sage SalesLogix
Server, SpeedSearch Server, and Sync Server computers. The local domain is the
security domain for that particular computer.
• Set “Access this computer from the Network”, “Allow log on locally”, and “Log on as a
service” rights on the Sage SalesLogix Server, SpeedSearch Server, and Sync Server
computers.
• Set Full permissions for the Library and Documents folders on the Administrative
Workstation, as well as for the Sync Logs folder on all Sync Servers.
• Sage SalesLogix Logging Folders. Create and share the logging folders as detailed in
“Understanding Logging Access” on page 65.
• Oracle Provider for OLE DB Components (Oracle implementations only). When installing,
ensure that the Oracle Provider version matches your Oracle Server and Oracle Client
version. The major version for all three pieces must be the same or compatibility issues
may arise.
• Trust relationship. Establish a trust relationship if the Database Server is on a different
network domain from some or all of the Sage SalesLogix users and components. Ensure
that these domains have a trust relationship with each other and can share data.
Oracle
• Oracle Server, Oracle Client, and Oracle OLE DB Provider component versions match. The
Oracle version installed on your Database Server must be the same major version that is
installed on your Client computers. Compatibility issues arise when the versions are
different.
Client Requirements
In addition to the “General Requirements” on page 61, ensure the following are set up on each
Client computer.
• Microsoft SQL Express or Microsoft SQL Server. For Remote Clients only, Microsoft SQL
Express or Microsoft SQL Server must be installed. See the Compatibility Checklist for
supported versions.
If Microsoft SQL Express is installed with Sage SalesLogix, it installs as a SALESLOGIX
instance with the sa password set to SLXMaster. If you install Microsoft SQL Express from
another source, you must set the sa password to SLXMaster (it is generally blank). To
install Microsoft SQL Express with the same configuration settings as Sage SalesLogix, use
one of the following files on the Sage SalesLogix DVD:
• For the Administrative Tools and Servers installation, run ...\SQLExpress\setup.exe
/settings "...\<SQLExpress>\Administrative Tools and Servers.ini"
• For the Sage SalesLogix Client installation, run ...\SQLExpress\setup.exe /settings
"...\<SQLExpress>\SalesLogix Client.ini".
• Microsoft Outlook. You must install Outlook if you are using Outlook Integration. Ensure
Outlook is installed and configured before installing Sage SalesLogix.
See “Outlook Integration Requirements” on page 65 for additional requirements.
• Small Fonts/Normal Size. Ensure the user’s Windows’ Display settings are set to Small
Fonts or Normal Size (the name of the option varies depending on which version of
Windows is installed).
To access this setting from the Windows Control Panel, double-click Display. On the
Settings tab, click Advanced.
• Data Execution Prevention (DEP) for essential Windows programs and services only. If
you are running Sage SalesLogix on Windows Vista, ensure this setting is enabled.
To access this setting, right-click My Computer > Properties > System Properties >
Advanced tab > Performance > Settings > Performance Options > Data Execution
Prevention tab > Turn on DEP for essential Windows programs and services only.
• Use User Account Control (UAC) to help protect your computer. If you are running Sage
SalesLogix on Windows Vista, ensure this setting is disabled.
To access this setting from the Windows Control Panel, double-click User Accounts and
then click the Turn User Account Control on or off hyperlink.
• Oracle Provider for OLE DB Components (Oracle implementations only). You must install
the OLE DB components on every computer running Sage SalesLogix for database
connectivity.
When installing Oracle, ensure that the Oracle OLE DB Provider is installed. In addition,
your Oracle Server version must match your Oracle Client version.
SpeedSearch Requirements
In addition to the “General Requirements” on page 61, ensure the following requirement is met
if your implementation includes SpeedSearch running on Windows Vista Business Edition.
• Admin user configured to run the SpeedSearch Service. If the SpeedSearch Service is
installed on a machine with Windows Vista Business Edition, the Local System Account
does not have enough inherited permissions to run the service.
Remote Office Sync Logs Folder The Remote Office Sync Logs folder is necessary for
implementations that contain a Remote Office. This is the root folder for Remote Office
synchronization files. This folder must be shared to allow access by everyone (including the
SLXService user).
Remote Office Library Folder The Remote Office Library folder contains all Library
documents that Remote Office Network users have access to.
Remote Office Documents Folder The Remote Office Documents folder contains all
documents that Remote Office Network users have access to.
Note If Remote users need direct access to the main office database, include those users in both
the SlxNetwork and SlxRemote user groups. For example, this would be necessary if users
work remotely and also dock their laptop when in the office.
The Standard installation allows you to choose what components you want to install and the
location where you want to install them.
Oracle
The SLX_Blank.dmp and SLX_Eval.dmp files are used to import data and the database
structure to the Sage SalesLogix database.
SLX_Blank.dmp This DMP file provides data that serves as your production database. The
user name for the Sage SalesLogix database created from the DMP file is admin; the
password is password.
SLX_Eval.dmp This DMP file imports accounts, contacts, tickets, defects, etc., to your
evaluation database for demonstration or testing purposes. You can log on to the Sage
SalesLogix database created from this DMP file as admin, Lee, Dan, or any other regular user
in the database. No password is required.
Important Do not use the evaluation database as your production database.
For more information on password settings for third-party applications, see the
“Understanding Third-Party Access Scenarios” topic in the Connection Manager Help.
• SQL Server sa password - If you have a password set on the sa account on the SQL
Server, type the sa password.
7. On the remaining screens, click Install and Finish to complete the installation. One of
the following options may appear on the last screen:
• Launch Administrator - If your database platform is Microsoft SQL Server and your
database is installed on the same machine as the Sage SalesLogix Server, select this
option and proceed with Chapter 13, “Configuring the Sage SalesLogix System”.
Otherwise, do not select this option and continue with the following sections to create
database connections.
• Install Microsoft SQL Express - This option appears if you installed the
Administrative Workstation without the Sage SalesLogix Server. Microsoft SQL
Express is required on the Administrative Workstation if you have an Oracle database
or if the Resync utility will be used. Microsoft SQL Express is optional if you have a
Microsoft SQL Server database, but is required if the Resync utility will be used.
• Install .Net AJAX Extensions, Install SQL Server 2k5 Exception Message Box,
and Install SQL Server 2k5 Backwards Compatibility - These options are
selected as appropriate for your system configuration. If necessary, these
components will be installed after Sage SalesLogix.
8. If necessary, reboot your computer.
d. In the Password box, type the user password (for example, masterkey).
e. Select the Allow saving password check box. You must select this option or the
connection fails.
f. In the Select the database on the server box, select your database.
c. In the Read-Only password for this connection box, type the password used to
allow read-only access to Sage SalesLogix data from any third-party applications.
d. Click OK.
4. On the Provider tab in the Data Link Properties dialog box, select SQL Native Client,
and then click Next.
a. In the Data Source box, type the name of your Sage SalesLogix Server.
b. Under Enter information to log onto the server, ensure Use a specific user
name and password is selected.
c. In the User name box, type the user name used to log on to the Database Server
(for example, sysdba).
d. In the Password box, type the user password (for example, masterkey).
e. Select the Allow saving password check box. You must select this option or the
connection fails.
f. In the Enter the initial catalog to use box, select your Sage SalesLogix database.
9. Click OK.
Once you have installed the components necessary for your implementation, you must log on
to the Administrator and complete the following tasks:
• Add licenses.
• Enter Office information.
• Configure SpeedSearch.
• Configure Sage SalesLogix options.
• Add Customer Service and/or Support information (if you are using the customer service
and/or support features).
Adding Licenses
All implementations require a Sage SalesLogix license (Standard, Advanced, or Premier).
Additional licenses determine the servers, offices, and users you can add to Sage SalesLogix.
See the Sage SalesLogix Planning Guide for a description of each available license.
The first time you log on to a Sage SalesLogix database that does not contain licenses, the
Setup Assistant appears.
To add office information without using the Setup Assistant, see the “Entering Office
Information” topic in the Administrator Help.
2. Type your company information such as division name (if applicable), primary and
shipping addresses, and telephone numbers.
Note Only the Company Name is a required field.
3. Click OK.
Adding Users
The last step of the Setup Assistant simplifies the process of adding Sage SalesLogix users.
The process for adding users is detailed in Chapter 14, “Configuring Sage SalesLogix Users.”
• Complete the information in the following sections to configure your Sage SalesLogix system. Then
use the processes detailed in Chapter 14, “Configuring Sage SalesLogix Users” to add users.
• Refer to Chapter 14, “Configuring Sage SalesLogix Users” to add users. Then return to the
following sections to complete your Sage SalesLogix system configuration.
Configuring SpeedSearch
SpeedSearch allows users and external customers to search for information stored in the
Sage SalesLogix database, such as tickets, standard problems, procedures, attachments,
Library documents, and external documents on your network. It also supports the Keyword
Search features in the Sage SalesLogix Client.
Note The Advanced SpeedSearch license is required to search the History and Activity indexes.
By default, the installation creates a shared SpeedSearch folder on the SpeedSearch Server,
which contains indexes and is necessary for SpeedSearch to function correctly.
See the “Managing SpeedSearch Indexes” topic in the Administrator Help for a
description of the default indexes and for detailed steps on creating new file system
and database indexes.
Initially, Sage SalesLogix automatically builds the default indexes and includes the following
index schedules:
• Full build – By default, each index is scheduled to be completely rebuilt every Saturday at
12 a.m.
• Incremental build – By default, each index is scheduled to be updated with the changes
made since the last build each day Monday through Friday at 12 a.m.
• To change the default index schedules or create new schedules, see the
“Managing SpeedSearch Schedules” topic in the Administrator Help.
• To understand how SpeedSearch information synchronizes with Remotes, see the
“Understanding SpeedSearch and Remotes” topic in the Administrator Help.
Refer to the “Configuring SalesLogix Options” topic in the Administrator Help for
information on other options.
setting is not recommended. This method requires a user interface and scheduler to
connect to the database and run the DTS package.
Refer to the “Creating Conflict Resolution Rules” topic in the Administrator Help if you
want to change the default conflict resolution rules or add additional rules.
See the “Setting Accounting Options” topic in the Administrator Help for details.
3. In the Open and Close boxes, select the time your normal business hours start and end.
The Hours of Operation area defines the time used for certain reports and follow-up
activities.
4. In the Time units in minutes box, type the smallest billable time unit to use for tracking
the time spent on a ticket.
5. If your company includes the weekend as part of the regular work week, select the Work
weekends check box.
6. In the Ticket Assignment Options area, select one of the following:
• Unassigned - Tickets are left unassigned until a user views the call and assigns it.
• Logged-in user - Tickets are assigned to the user that saves the ticket.
• Auto-assignment - Tickets are assigned to the user or team associated with an
Area. If an Area has no associated user or team, the ticket is left unassigned. Area
values are configured in “Creating Area, Category, and Issue Lists” on page 106.
7. Select the Default user or team assigned to account overrides Ticket Assignment
Options check box if you want the Default User/Team selected on the Sage SalesLogix
Client > Account > Notifications tab to override the Ticket Assignment Option.
For example, if you set the Ticket Assignment Option to Logged-in user, and select this
check box, any tickets created for an account that has a Default User/Team set in the Sage
SalesLogix Client will be assigned to the defined user/team. Any accounts that do not have
a Default User/Team set, will be assigned to the logged-in user. If this check box is cleared,
new tickets for an account are assigned to the logged-in user even if the account has a
user/team selected as the default for new tickets.
8. Under SpeedSearch, choose whether or not to use an approval process to determine
which new tickets and defects are added to SpeedSearch.
9. Click OK.
When creating Sage SalesLogix users, you must add new users and modify the user profile.
Optionally, you can create teams. Teams contain users who require access to the same set of
accounts.
Creating Departments
Departments contain users, but cannot contain teams. However, teams can contain
departments. A user can belong to more than one department and more than one team.
The default department named None is automatically applied to all new users.
To create a department
1. On the Administrator Navigation Bar, click Users.
2. On the Edit menu, click New Department.
3. In the Department Name box, type a name for the department, and then click OK.
4. Repeat steps 2-3 to create additional departments.
For detailed information on each function, see the “Administrative Functions” topic in the
Administrator Help.
6. Click OK.
7. Add additional profiles as appropriate.
Creating Users
Before creating users, determine the best method of configuring the user’s profile for your
company’s size and structure.
If you plan to add several users with identical profiles (for example, the same department,
division, manager, security settings, and so on), Sage SalesLogix recommends you use a user
template. Templates are recommended because they significantly reduce administration time.
When creating users, you can apply a Sage SalesLogix user template, or a custom template
you create, which applies the appropriate settings to each user. User templates do not
consume a license and cannot log on to Sage SalesLogix.
For detailed information on default Sage SalesLogix user templates, see the “Creating a User
Template” topic in the Administrator Help. If necessary, you can customize the default
templates.
The following sections detail how to create a custom user template, add users based on
existing Windows’ users, and then how to complete and activate the new users.
For information on other user options not detailed here, refer to the “Modifying a User’s Profile”
topic in the Administrator Help.
If you did not create administrative roles, refer to “Creating Administrative Roles” on page
90 for more information.
Refer to the next section to set options on the Client System tab.
4. In the Email section, select your company’s e-mail application. If you are using Outlook
Integration, select Microsoft Outlook.
• (Microsoft Outlook) In the Profile Name box, select your local mail system profile.
• (Mail Client) In the Show names in address book by box, select how you want
contact names to appear in the address book.
Refer to the next section to set options on the Service/Support tab.
For information on other methods of adding users, see the “A New Employee Needs Access to
Sage SalesLogix” topic in the Administrator Help.
3. In the Windows Domain box, select the domain from which you want to map your
Windows' users.
Existing Windows users appear in the Windows Username and Windows Full Name
columns.
4. To quickly locate a specific Windows' user, type a Windows Username in the Search for
box.
You can use a variety of search methods in this box. For example, if you type the letter J,
all Windows user names that contain a J will appear.
5. Press CTRL and select all users that you want to create for a specific user type. For
example, select all users that you want to create as Network users.
6. In the User Type box, select the type of user that you want to create.
7. In the Template box, select the user template that you want to apply to the user(s).
You can select a custom template or a pre-configured system template. If you do not select
a template, users are created with a blank user profile with only system defaults enabled.
8. Click Create User(s).
A check mark appears next to each user that will be created.
9. Repeat steps 4-8 for all other user types that you want to create.
10. If you want to import information from Windows’ Active Directory to each user’s profile,
ensure Update SalesLogix user information with Windows information is selected.
Otherwise, clear this check box.
For more information on importing from Active Directory, see the “Importing Additional User
Information from Windows” topic in the Administrator Help.
11. If you want to enable Windows Authentication (single log-on) for the selected users,
ensure Use Windows Authentication is selected. If you simply want to import the
users, clear this option (in this case users will be required to log on to the Sage
SalesLogix Client unless you enable Windows Authentication in each user's profile).
Configuring Users
If you create a user from a template, from an existing Windows’ user, or import the user
information from another application, you must complete additional configuration steps
before the user can log on.
1. On the Administrator Navigation Bar, click Users.
2. In the Users view, double-click a user to open the profile.
3. If necessary, select the Use Windows Authentication check box. In the Windows ID
box, select the name the user enters to log on to Windows.
With Windows Authentication, users are automatically logged on without entering their
Sage SalesLogix user names or passwords.
4. In the Username box, type the name the user will use when logging on to Sage
SalesLogix.
The user name is required and cannot contain spaces or an apostrophe. For Remote users,
the user name must also follow the Rules for Regular Identifiers specific to the version of
Microsoft SQL Server that you are using to create Remote databases. The Remote user
name must follow these rules as it is sent to the Microsoft SQL Server or Microsoft SQL
Express to be used as part of a Remote database name.
5. In the Name box, enter the user’s name.
If you selected the Update SalesLogix user information with Windows information check
box on the Import Windows Users dialog box, the Username and Name boxes are pre-filled
with Windows information. This information does not need to be changed.
6. In the E-Mail box, enter the user’s e-mail address.
7. Select the User is a Manager check box if the user is a manager whose name should
appear in the Manager list.
8. Click the Employee tab.
9. If necessary, in the Accounting ID field, type the user's accounting identification code.
(This is the ID used by the accounting software.)
10. Click the Teams tab.
The Teams tab allows you to create user teams and add or remove the user from system
teams. User teams allow users to access accounts owned by another user. For example, if
you want Lee to have access to all Dan’s accounts, you can add Lee to Dan’s user team.
System teams group users together so that all team members have access to the same
accounts.
11. In the User Team section, click Add to add other users to this user’s team.
Users you add to this user’s profile can access all accounts owned by the main user (the
user whose profile you are editing).
12. In the Field Security of selected user box, select a security profile for the user
selected in the User Team section. This profile only applies when accessing accounts
owned by the main user (the user whose profile you are editing).
Creating system teams is detailed in “Creating Teams” on page 99.
Note Field security never applies to accounts owned by an individual when that individual is the
user accessing the accounts.
13. Click the Calendar tab.
The Calendar tab sets permission rights for users to view and modify other user’s
calendars.
14. In the Other Calendars section, click Add Users to set access for this user to add, edit,
delete, or sync activities for another user.
15. In the This User’s Calendar section, click Add Users to set access for other users to
add, edit, delete, or sync activities to this user’s calendar.
16. Click OK.
Creating Teams
The Sage SalesLogix Planning Guide describes how teams and team security function. Use
that information to help you decide how many teams you want and who is on each team.
Teams define who owns an account and which users can access that account. Users can
belong to more than one team and their security profiles can be different for each team.
To create a team
1. On the Administrator Navigation Bar, click Teams.
2. In the Teams view, click New Team.
3. In the Create New Team dialog box:
a. In the Team Name box, type the team name.
b. In the Team Owner box, select the user that you want to be the team owner. Teams
may have multiple team owners.
c. In the Select team members box, click a user(s) to add them to the team.
d. Click OK.
For more information on teams, including how to set different security profiles within teams and
making global changes to teams, see the “Working with Teams” topic in the Administrator Help.
You can install the Sage SalesLogix Client using one of two methods.
Automated installation Automated installations create an executable file that allows the
Sage SalesLogix Client to be installed with no user intervention.
Automated installations reduce administration time when you upgrade to a new version, and
then add new users to Sage SalesLogix. During the upgrade process, you can update the
Client installation images directly from the upgrade wizard. Then when you add new users
and install Sage SalesLogix, the installation includes all service packs and upgrades that are
installed on your system.
Important When installing the Sage SalesLogix Client using an automated installation, third-party
applications are not installed. This includes Intellisync for Sage SalesLogix (Network
and Remote Client) and Microsoft SQL Express (Remote Client). Third-party
applications must be installed separately, and can be found in the Redist folder on
the Sage SalesLogix DVD.
Standard Sage SalesLogix Client installation The Sage SalesLogix Client can be installed
on each user’s computer using the Client installation. The standard installation includes
Typical and Custom options which allow you to install all components or choose the
components necessary for your implementation.
• In the SalesLogix Server box, select or type the name of the computer on which
you installed the Sage SalesLogix Server.
This setting is not available if you are creating a Sage SalesLogix Remote Client
installation.
• In the SalesLogix Database Alias box, select or type the name of the database
connection.
This setting is not available if you are creating a Sage SalesLogix Remote Client
installation.
• If necessary, in the Port box, change the port number used for communication
between the client and the Sage SalesLogix Server.
In most implementations, the default port number does not need to be changed.
However, if you have another application or service using port 1706, you should
change the port number to an unused port.
6. In the Network Location box, type or browse to the location where the automated
installation should be created.
This location must be a shared network path.
7. On the remaining screens, click Install and Finish to complete the installation.
The automated installation is created in the specified shared network location and a
shortcut to the installation is created on the desktop.
8. Distribute the shortcut or installation to users.
If your company uses Lotus Notes or GroupWise, see the “Setting Sync Preferences for Outlook
and Intellisync” topic in the Sage SalesLogix Client Help for step-by-step configuration
instructions.
By default, the Intellisync for Sage SalesLogix configuration files are created in the
...\Program Files\SalesLogix\SlxIntellisync folder. If necessary, you can change this location
after installation. This may be necessary if you are running Sage SalesLogix in a Citrix
environment. See the “Changing the Intellisync Default Installation Path” topic in the
Administrator Help for detailed instructions.
or proceed to “Adding Address Lists to the Outlook Addressing Tab” on page 106 if you want
users to have the ability to perform Sage SalesLogix Contact name resolution in Outlook.
3. In the Sync Configuration area, click Configure. The Intellisync for SalesLogix
Configuration dialog box appears.
You do not need to click the Login button for configuring the sync options unless you plan
to use several databases. The first time the sync options run, you will be prompted for the
database login.
4. To configure contact synchronization, select Contacts.
5. In the Choose Translator dialog box, do the following:
a. Select MS Outlook.
b. Ensure Synchronize is selected in the Operation area.
c. Click OK.
6. Click Configure and then click Advanced Settings.
7. In the Advanced Settings for Contacts dialog box, click the Filters tab, and then click
New.
8. In the Filter Name dialog box, type SyncSalesLogix, being sure to capitalize it exactly
as shown, and then click OK.
9. On the Conditions tab, complete the following:
a. Click Field, and then select Categories from the list.
b. In the Operator box, select contains.
c. In the Value box, type SyncSalesLogix, being sure to capitalize it exactly as shown.
d. Click Add to List, and then click OK.
The Advanced Settings for Contacts dialog box reappears, displaying the Filters tab. Notice
that SyncSalesLogix is added to the list of available filters.
10. Ensure SyncSalesLogix is selected, and then click OK.
The Intellisync for SalesLogix Configuration dialog box appears. Notice that "Contacts
Filtering with SyncSalesLogix" appears on the right side.
11. If you want to set up synchronization for other items, such as appointments (meetings
and phone calls), events, timeless appointments, or to-dos, select the item, and then
click Choose. Repeat Step 5 to select the translator, and then repeat steps 6 through 10.
If you do not set up synchronization for timeless appointments, any existing timeless
appointments are included on both the Sage SalesLogix and Outlook calendars. However,
updates and new timeless appointments are not synchronized.
12. Click OK to close Intellisync for SalesLogix Configuration.
13. In the Confirmation Options area of the Outlook Synchronization tab, Ignore all
confirmation items is selected by default. If you want to receive a confirmation message
when items are synchronized (not recommended), clear this check box.
14. In the Sync Run Options area of the Outlook Synchronization tab, under Calendar
Activities and Contacts, select the options that apply to your sync preferences.
For example, if Automatically (after any activity changes) is selected, automatic
synchronization with Outlook is triggered when you delete an activity in Sage SalesLogix.
15. When all settings are complete, click OK.
2. On the Edit menu, click Categories, and then click Master Category List.
3. In the New category box, type SyncSalesLogix. Capitalize it exactly as shown.
4. Click Add, and then click OK.
5. In the Categories dialog box, click OK.
6. From the Contacts view, double-click a contact that you want to synchronize, and then
click Categories.
7. In the Categories dialog box, select SyncSalesLogix, and then click OK.
8. You can continue assigning the SyncSalesLogix category to Outlook contacts by
repeating steps 6 and 7.
Note The SyncSalesLogix filter is used when synchronizing contacts. It is not necessary to use
this filter when you are exporting contact information to Outlook.
See the “Setting Sync Preferences for Outlook and Intellisync” topic in the Sage SalesLogix
Client Help for information on adding Sage SalesLogix Contacts to Outlook.
The Area, Category, and Issue lists are linked in a hierarchy. The Area you select determines
the options available for the Category, and the Category you select determines the options
available for the Issue.
The Area, Category, and Issue lists are used to reduce administration time when users are
creating tickets and defects. If you are not using the customer service or support features,
you do not need to create the area, category, and issue lists.
Marketing is fully integrated in the Sage SalesLogix Client and requires no additional
configuration. If you want to use the additional functionality provided by Marketing Services,
you must configure the Marketing Services Configuration Manager, create a Marketing
Services account, and then create a Marketing Services user.
If your implementation does not include Marketing Services, proceed to Chapter 17,
“Configuring the Synchronization Server”.
Note Marketing Services is a regional option and may not be available in all locations.
d. If your Sage SalesLogix Server is not directly connected to the Internet, select the
Use a SOCKS proxy check box, and complete the following information.
• In the Host box, type the computer name, IP address, or URL of the computer
that hosts the SOCKS server.
• In the Port box, type the SOCKS server port number.
• In the Authentication box, select saUsernamePassword if an account and
password are required to log on to the SOCKS server. Select
saNOAuthentication if an account and password are not required.
• In the Version box, select your SOCKS version number.
• In the Account name box, type the SOCKS account name (if you selected
saUsernamePassword in the Authentication box).
• In the Password box, type the SOCKS password (if you selected
saUsernamePassword in the Authentication box).
e. Click the Notifications tab.
4. On the Notifications tab, configure your settings for the SMTP server that is used to
send e-mail notifications regarding the processing of batch jobs that are scheduled using
the Sage SalesLogix Client. You can also configure the recipients of e-mail notifications.
a. Select the Send e-mail notifications check box if you want EmPulse to send
notifications regarding successes, failures, and so on. If you do not want to send e-
mail notifications, proceed to step 5.
b. Select the Login required check box if you want to be prompted to log on to the
SMTP server before notifications are sent.
If a login is required, set the Account name and Password used to log on to the SMTP
Server in the appropriate boxes.
c. In the SMTP host box, type the SMTP address of the SMTP Host Server.
d. In the SMTP port box, select the port number on which the SMTP Server
communicates with Sage SalesLogix.
e. Select the Include details of failed Service imports and exports check box if you
want detailed error reports when transactions between EmPulse and Sage SalesLogix
fail.
f. Under E-mail Recipients, select the Campaign manager box if you want to send
e-mail notifications to the manager of the campaign as assigned in Sage SalesLogix.
g. Select Request owner to send e-mail notifications to the user that scheduled the
request in Sage SalesLogix.
h. Select Service account owner to send e-mail notifications to the individual that
owns the account with EmPulse. For example, this may be a Business Partner or
some company executive not associated with the campaign in Sage SalesLogix.
i. Select the Other address check box to manually add e-mail addresses to which you
want to send e-mail notifications. Use the Other addresses grid to add additional e-
mail addresses.
j. Click the Scheduling tab.
5. On the Scheduling tab, set schedules for downloading and processing information from
EmPulse.
a. In the Download Responses On section, select which days of the week you want to
receive responses from EmPulse.
b. If necessary, select Limit polling and set a time that you want to connect to
EmPulse during the selected day(s).
When this option is selected, Sage SalesLogix only attempts to connect with EmPulse
during that time of the day.
c. Click the Options tab.
6. On the Options tab, select when you want to receive error messages and other
processing options.
• In the Windows Event Logging section, select the events for which you want to
receive error messages.
• Errors creates a log if a significant problem occurs, such as loss of data or loss of
functionality.
• Warnings creates a log if an event occurs that is not necessarily significant, but
may indicate a possible future problem.
• Information creates a log that describes the actions taken by the service. This
can be used for troubleshooting problems.
• If necessary, select the Only process responses for active SalesLogix
campaigns check box.
When this option is selected, response information is only received from EmPulse for
campaigns in Sage SalesLogix that are currently active.
• Select the Map User fields to EmPulse Custom fields check box to automatically
map Userfield1 - Userfield10 in the Sage SalesLogix CONTACT and LEAD tables to the
Custom 11 - Custom 20 fields in the EmPulse database.
7. Click OK to close the Configuration Manager.
3. In the SalesLogix User box, select the user that will access the marketing services
account.
If you want to automatically import campaign responses associated with this user, select
the Automatically import responses for this user check box. If this option is not selected,
the user must perform dynamic imports to analyze responses.
4. Under Service Login, the Primary option is selected.
When adding the first Marketing Services user, the Service Login section is disabled. There
must always be a primary account and the first user defaults to that primary account. If
additional Marketing Services users are added, you can select the Use Primary option to
use the Primary credentials when communicating with EmPulse. The Secondary option
allows the user to access an account other than the primary. For example, you may want
to use one account for your Sales department and another for your Marketing department.
5. In the Owner E-mail box, type the e-mail address of the EmPulse account owner. This
option is necessary only if the Service account owner check box is selected in the E-
mail Recipients section of the Notification tab on the Marketing Services Configuration
Manager.
The e-mail address must be an SMTP address. Use the format [email protected] or
“Some Name <[email protected]>".
6. Click OK.
Synchronization Server refers to both the software that runs synchronization and the
hardware on which the server is installed. A Sync Server is only necessary if you have Sage
SalesLogix Remote Clients or Remote Offices, or you plan to run agents.
Use the Sage SalesLogix Planning Guide to understand the synchronization process in detail
and to make decisions regarding your synchronization requirements.
For FTP performance tips, see the “Improving FTP Synchronization Performance” topic in the
Administrator Help.
8. In the Alternate Site box, type an alternate address that connects to your FTP site.
If the Sync Client cannot connect using the primary address, it attempts to use the
alternate address. For example, you can use the named FTP site as the primary site and
the IP address as the alternate site.
9. In the Port box, type the alternate site’s port number on the FTP server.
10. In the File Names box, select Uppercase, Lowercase, or Unspecified.
Response time improves considerably if this setting matches the way file names are stored
on your FTP server. The default is Unspecified.
11. In the Infiles, Outfiles, and FailedTrans boxes, type the Infiles, Outfiles, and
FailedTrans folder names on your FTP server (for example, /Infiles, /Outfiles, and
/FailedTrans).
Creating the Infiles folder is outlined in “Setting Up a Sage SalesLogix FTP Site” on page 114.
12. Under Login:
• Click Login and password below to assign the same login and password to the
Sync Server and all Remote users. Then in the Login box, type the general login that
is shared by all Remote users and Sync Server(s) when logging on to the FTP site. In
the Password box, type the corresponding password. Then, click OK.
If you choose to use a global login, you can use the default anonymous user that
comes with FTP. This user is already configured with the necessary permissions. This
user has a Login of anonymous, and the corresponding Password is your domain name.
• Click Personal login and password to assign a different login and password to each
Sync Server and Remote user. Then, click OK.
Use the FTP Sync Transport Local Options dialog box to set the login for the sync
server. Personal logins for Remote users are set in the individual’s user profile. The
instructions for configuring the user login are in Chapter 18, “Configuring the Sage
SalesLogix Remote Client.”
13. If you selected the Personal login and password option, in the Edit Sync Transfer
Profile dialog box, click Server Settings. In the Login and Password boxes, type the
Sync Server’s login and corresponding password to the FTP site.
14. Click OK.
c. In the Host header for this Web site box, leave the field blank.
d. Click Next.
10. On the Web Site Home Directory screen:
a. In the Path box, click Browse and navigate to the folder you created in Step 1. DO
NOT point to the network logging path.
b. Clear the Allow anonymous access to this Web site check box.
c. Click Next.
11. On the Web Site Access Permissions screen:
a. Enable only the following Permissions: Read, Write, and Browse.
b. Click Next.
12. Click Finish.
13. In the Internet Information Services tree view, right-click your new Web site, and
then click Properties.
14. In the Web Site Properties dialog box, click the Directory Security tab.
15. In the Authentication and access control section, click Edit.
16. In the Authenticated access section, select Digest authentication for Windows
domain servers.
17. In the IIS Manager information dialog box, click Yes to continue.
18. In the Authentication Methods dialog box, click the Realm Select button, browse to
and select the domain of your HTTP Server, and then click OK.
19. In the Authentication Methods dialog box, click OK.
20. In the Web Site Properties dialog box, click the HTTP Headers tab.
21. Click the MIME Types button.
22. In the MIME Types dialog box, click New.
23. In the MIME Type dialog box:
a. In the Extension box, type SLXT.
b. In the MIME type box, type Text/Plain.
c. Click OK.
24. In the MIME Types dialog box, click OK.
25. In the Web Site Properties dialog box, click OK.
26. Reset IIS.
You can reset IIS using the IISReset Run command.
After setting up IIS, you must create a Sync Transfer Profile in the Administrator.
6. In the Web Site box, type the name of the HTTP Server to which the Sync Client
connects for file transfer (for example, httpserver).
Use the format: Servername or Servername.DomainName. Do not include http:// before
the server name.
Note This is the name of the server the Sync Client connects to, not the URL.
7. In the Port box, type the port number of your HTTP Server.
This is the port number you defined in Step 9 of the previous section.
8. Select the Secure Comm (SSL) check box if you are using a secure connection to
transfer files between the HTTP Host and Sage SalesLogix.
9. In the Alternate Site box, type an alternate HTTP Server for file transfer.
If the Sync Client cannot connect using the primary Web Site, it attempts to use the
alternate site.
10. In the Port box, type the alternate site’s port number on the HTTP Server.
11. If necessary, select the Secure Comm (SSL) check box if you are using a secure
connection for your alternate site.
12. In the Infiles, Outfiles, and FailedTrans boxes, type the Infiles, Outfiles, and
FailedTrans folder names on your HTTP server (for example, /Infiles, /Outfiles, and
/FailedTrans).
Creating the Infiles, Outfiles, and FailedTrans folders is outlined in “Setting Up a Sage
SalesLogix HTTP Site” on page 116.
13. Under Login:
• Click Login and password below to assign the same login and password to the
Sync Server and all Remote users. Then in the Login box, type the general login that
is shared by all Remote users and Sync Server(s) when logging on to the HTTP
Server. In the Password box, type the corresponding password. Then, click OK.
• Click Personal login and password to assign a different login and password to
each Sync Server and Remote user. Then, click OK.
Use the HTTP Sync Transport Local Options dialog box to set the login for the Sync
Server. Personal logins for Remote users are set in the individual’s user profile. The
instructions for configuring the user login are in Chapter 18, “Configuring the Sage
SalesLogix Remote Client.”
14. If you selected the Personal login and password option, in the Edit Sync Transfer
Profile dialog box, click Server Settings. In the Login and Password boxes, type the
Sync Server’s login and corresponding password to the HTTP Server.
15. Click OK.
The Sync Services File Path dialog box appears the first time this tab is accessed.
3. In the Sync Services File Path dialog box, type or browse to the shared folder that all
synchronization services will access, and then click OK.
If you did not create the SyncService folder, see “Understanding Logging Access” on page 65
for instructions. By default, the Express installation automatically creates this folder in
\\My Server\SyncService.
4. Right-click the grid, and then click Add Service.
The Service Configuration dialog box appears.
5. In the Service Name box, type a name for this service (for example, the name of the
computer the service is installed on).
6. In the Service Machine box, type or browse to the name of the computer where the
Synchronization Service is installed.
7. In the Service Port box, type the port number on which the Synchronization Service
sends information to the Monitor Console.
The default port is 8950. Leaving this set to 8950 avoids conflicts. If conflicts occur, only
information from one service displays in the Monitor Console.
8. In the Job Name box, type a name for the new job.
The job name is used to display history in the Monitor Console, therefore ensure you use
a descriptive name.
9. In the Database list, select the database on which the job runs.
By default, the database to which you are currently logged on displays in the list.
10. In the SyncServer list, select the Sync Server for which this job is run.
11. In the Sync Data list, select the type of processing you want to perform:
• Sync All (Default) applies network and remote transactions, sends remote changes,
runs subscription rules and sends new accounts, and runs any pending agents.
• Sync Updates Only applies network and remote transactions and sends remote
changes.
12. In the Run on and Daily Schedule boxes, select the dates, times, and frequency of the
synchronization cycle.
13. Select the Enabled check box to activate the job and add it to the synchronization
schedule.
14. Click Apply Job.
You can create multiple jobs for each sync server. To create additional jobs, right-click the
Jobs grid, and click Add Job. Then repeat steps 10-14.
The first time you log on to the Monitor Console, you must set the name of the Sync Server
computer. Then you must register the synchronization service(s) to view data. This process is
detailed in the Monitor Console Help.
By default, the Monitor Console is installed in C:\Program Files\SalesLogix (with the
Administrative Workstation). To open the Monitor Console, double-click
SlxMonitorConsole.exe.
Remote Clients keep a subset of the main office database on their local computer (a laptop,
for example) and use synchronization to transfer changes between their system and the main
office. To synchronize data, the main office and each Sage SalesLogix Remote Client must
have a set of synchronization folders on their computers and have the ability to transfer files.
Remote users can also connect directly to the main office database using a LAN or WAN
connection.
Using Subscription
There are two ways to subscribe to accounts:
• Use subscription rules to request accounts based on specific criteria or conditions.
• As needed, use manual account subscription to select accounts using the Administrator or
Sage SalesLogix Remote Client.
For detailed instructions to create subscription rules, refer to the “New Subscription Rule or
Template” topic in the Administrator Help.
b. To set a date limit, select Files Added Within Last, and then type in a number of
days.
When this value is set, any attachments older than the specified value will not
automatically synchronize to the Remote. The Remote user can request the
attachment, but it will not be sent when creating a Remote database or during the
normal synchronization process.
c. To apply these options to all Remote users, click All Users.
d. Click OK.
3. Each database is placed in the folder specified in the Create Remote DB in server
directory box on the Database tab of the Options dialog box. To create the database(s),
do one of the following.
• To create the database(s) immediately, click Now.
• To create the database(s) at a later time, click Later.
• In the calendar, select a date and time, and then click OK.
The Administrator is unavailable when the timer is active.
• The Create Databases dialog box displays a countdown to the scheduled date
and time.
A test is performed to ensure the settings are configured and that the database can
be created in the chosen location.
The database is created with the file name SLX_userid_dat.sxd.
4. Click OK to confirm successful completion.
If the Remote user’s computer is connected to the network, create a folder on the
Administrative Workstation and copy the database to the folder. Share this folder so that the
Remote user’s computer has access to it.
If the Remote user is not connected to the network, copy the database to the user’s
computer using some form of removable media. Another option is to zip the database, e-mail
it to the Remote user, and instruct the user to copy it to his or her computer and unzip it.
For more information on automated synchronization, see the “Sage SalesLogix Synchronization
Client” topic in the Sage SalesLogix Client Help.
• When SalesLogix Closes - All enabled indexes are updated when you close the
Sage SalesLogix Client.
• Once at - Select the time of day that you want to update all enabled indexes.
• Repeat Every - Select or type how often you want all enabled indexes to be
updated.
5. Click OK.
A Remote Office consists of a group of Network users who access a Remote Office database
through a direct connection or wide-area network. Unlike Remote users, these Network users
do not individually synchronize with the main office. Instead, synchronization occurs when
the Remote Office database synchronizes with the main office.
The main office’s Administrator manages the Remote Office and Remote Office users.
domain, you must change the SLX Service from Local System Account to a domain user
with rights on both domains.
b. In the Library box, type the location of the Remote Office Library folder using UNC
conventions and the shared names.
For example, \\MyServer\Library, not \C:\RemOffice Sync Logs\Library.
c. In the Attachments box, type the location of the Remote Office Documents folder
using UNC conventions and the shared names.
For example, \\MyServer\Documents, not \\MyServer\C:\RemOffice Sync
Logs\Documents.
Note If you are connected to the network, browse to the Remote Office folders.
5. Click OK.
Automating Client installations allows you to deploy customized installations of the Sage
SalesLogix Client to Network and Remote users. Using automated installations the system
administrator can create a configuration file containing the desired Sage SalesLogix settings
and send it to users. Once received, the user can bypass the steps in the Installation Wizard
and use the custom configuration file to install Sage SalesLogix.
There are several advantages to using automated installations. You can:
• Enforce the use of specific settings for all users.
• Specify different configurations for different users.
• Install Sage SalesLogix with minimal user input.
Important When installing Sage SalesLogix using an automated installation, third-party
applications are not installed. Third-party applications must be installed separately and
include the following: Intellisync for Sage SalesLogix (Sage SalesLogix Client) and .Net
AJAX Extensions, SQL Server 2k5 Exception Message Box, and SQL Server 2k5
Backwards Compatibility (Administrative Tools and Servers). Installations for
these applications can be found in the Redist folder on the Sage SalesLogix DVD.
Features
Use the Features section to determine the components you want to install on the Client
computer. The following are the Sage SalesLogix Client install features:
Properties
The following properties can be set in the Sage SalesLogix Client configuration file.
.NET Extensions Allows the display and support of .NET customizations in Sage SalesLogix
as standard database plugins.
Account A company with which there is a current or potential business relationship. Accounts
are owned by an individual user, a team of users, or everyone.
Administrative User A user who can perform tasks in the Administrator normally reserved
for the system administrator.
Administrative Workstation The primary computer for administering and customizing Sage
SalesLogix. Usually, this is either the system administrator’s personal computer or a separate
computer dedicated to Sage SalesLogix. The Administrator, Architect, Application Architect
and Sage SalesLogix Client are usually installed on this computer.
Agents A method of scheduling reports, running Basic scripts, SQL scripts, etc., at intervals
specified in the Administrator and Synchronization Server profile. Agents can be scheduled to
run once or on a regular basis.
Application Architect A development environment containing the tools that allow developers
to rapidly build, customize, manage, and deploy coded and codeless Web application
solutions with one-click functionality.
Architect A development environment for creating customized views, menus, toolbars, and
scripts for Sage SalesLogix.
Archives A folder containing a copy of all files sent to Remote users or Remote Offices, or to
the main office during synchronization.
Business Rule A method that is typically executed via code. A Business Rule is used to define
the constraints that apply to an entity within a package.
Bundle A bundle is a group of plugins or other customizable components that are packaged
together for installation as a unit, rather than having to move them one by one, or re-create
them on every database. Bundles containing Network plugins (.sxb files) are installed using
the Administrator. Bundles containing Web customizations (.zip files) are installed using the
Application Architect.
Concurrent Users The number of users accessing the database at any one time.
Contacts The prospects or customers in a company (account) that users interact with. Each
account can contain one or more contacts.
Contract An agreement between your company and the customer to provide support
services, either for free or for a specified fee.
Customer Service Customer Service allows designated users to track, qualify, and resolve
customer questions and issues within the Sage SalesLogix Client.
Dashboards Part of Sage SalesLogix Client that allows users to display and interact with a
variety of analytical information in a dashboard.
Database Manager Part of the Administrator and Architect that allows you to add, view, and
delete tables and fields, as well as name indexes, in the Sage SalesLogix database.
Defect A record describing a problem in a product or process, or a feature request for a
product or process.
Documents Folder A folder containing files that are attached to an account, contact,
opportunity, or ticket. For example, a Word letter.
Entity A business object, such as account or product that contains business rule methods
and events, relationships, properties, and forms. Entities can also have other related entities
associated with them, either through child relationships or extensions.
Form A Smart Part containing normal content, markup, and controls. A Web form is similar
to Forms created in the Architect.
Host A term commonly used for a Sage SalesLogix database that supports both Network and
Remote users.
Import Wizard Used to import data into Sage SalesLogix from ACT! by Sage, or other
commonly used file formats and databases.
Infiles A folder in which the main office, or Remote users or Remote Offices, place sync files
during synchronization.
Join A database operation that connects two database tables having a common field.
Library A central repository for company information. The library may include product
information, policies and procedures, presentations, and so on.
Lookup Lookups enable users to search for information under any of the major families (for
example; account, contact, ticket, and so on) that shares certain characteristics. Once a
lookup is created, you can save the result as a group. Lookups can be managed from the
Architect or Administrator.
Method A piece of code associated with an entity. A method usually consists of a sequence of
statements to perform an action, and possibly output a value. Methods provide a mechanism
for accessing (for both reading and writing) the private data stored in an entity.
Microsoft .NET Framework A component of Windows used to build and run Windows-based
applications.
Module A unit of work for the application to function correctly. Modules are parts of an
assembly. Modules are always stored in the Bin or reference directory. Modules may contain
Smart Parts.
Monitor Console A tool to remotely monitor the status of the Synchronization Server and its
scheduled jobs.
Namespace A unique identifier that helps you to avoid duplicate entity names.
Network Clients Users that connect directly to the network database to access and manage
customer accounts, contacts, opportunities, tickets, defects, activities, and related
information.
Opportunities Potential sales to accounts or contacts.
Package A group of related entities, forms, Smart Parts, templates, and aliases that are
grouped together under a common name. Packages make it easier to manage your Web
customizations.
Page A unit within a Web Portal. A page is a collection of workspaces.
Plugins Components that customize and add functionality to Sage SalesLogix. Plugins
include views, processes, reports, templates, Visual Basic scripts, and SQL scripts.
Portal Represents a collection of Web pages.
Processes A plugin that represents a series of tasks executed in a specific sequence over a
set time period. Processes are used to perform repetitive tasks, implement a sales process,
or provide an automated way of following up with customers. The Web components may only
schedule processes and change process status.
Project A group of Web packages or plugins that are grouped together for easy retrieval and
use.
Property Properties are contained on each form. Properties control the form behavior and
appearance.
Workspace A container for a Smart Part. Multiple workspaces can be combined in a template
to organize Smart Parts.
WGLogs A folder in which Network users place transaction files as changes are made to the
database.
FTP N
server settings 41, 44, 116, 119
Net Service Name, creating for Oracle 76,
setup 40, 114
138
site for Sage SalesLogix, configuring 40,
Network client 148
114
Network synchronization 39, 113
sync profile 39, 113
Network users
sync transfer profile 40, 114
adding to remote office 132
FTP synchronization 39, 113
Network, sync profile 39, 113
H O
HTTP
Office information
setup 43, 117
entering 16, 80
site for Sage SalesLogix, configuring 42,
support options 19, 85
116
Opportunities 148
sync transfer profile 43, 117
Options
accounting 19, 85
I configuring 17, 82
Import Wizard 148 configuring for users 25, 98
Importing Oracle database structure 140 conflict resolution 84
Indexes, SpeedSearch 81 database 17, 82
Infiles 40, 41, 44, 114, 115, 118, 134 Oracle
folder 148 configuring database 139
Installations, customizing 143 creating database login 140
Installing database files 69
Remote Client 50, 126 import database structure 140
Remote Office 133 Outfiles 40, 41, 44, 114, 115, 118
remote office database 134 Outlook
Sage SalesLogix Network Client 28, 102 integration requirements 11, 65
Sage SalesLogix Server 70 integration with Sage SalesLogix 18, 85
Internet Explorer 10, 62 prerequisite 11, 64
Outlook integration 30, 104
J
Join, defined 148 P
Password
L blank database 69
LAN Developer’s Reference 2 evaluation database 70
Library folder 65 Planning, for implementation 1
Licenses, adding 16, 80 Plugins 148
Logging on Processes
Sage SalesLogix applications 15, 79 defined 148
Login Profiles
creating for Oracle database 140 creating for user security 90
FTP synchronization 39, 114 Remote Office 131
Remote user, creating 48, 124
M support user 96
Mail client 10, 62 sync transfer for FTP 40, 114
MailClient 29, 103 sync transfer for HTTP 43, 117
MDAC 9, 61 Synchronization Service 119
MDF files 13, 69 user 93
Microsoft SQL Express 9, 61
Microsoft SQL Server R
databases 13, 69 Relational database management system
Microsoft SQL Server authentication 10, 63 (RDBMS) 149
Microsoft Word 10, 62 RemOffice Sync Logs folder 66
Monitor Console 46, 122, 148 Remote Client
creating profiles 48, 124
installing 50, 126
W Windows
sharing folders 68
Web Developer’s Reference 2
Windows authentication 10, 63
Web Implementation Guide 2
WinFax
Web Server 20, 86
Message Manager 29, 103
WGLogs folder 134
WinHelp engine 12, 65