1 v6 Architecture, Customization and Integration December 2004
2 TABLE OF CONTENTS Introduction... 3 Tiered Architecture Concept... 3 Architecture... 4 Business Rules Security Sync Logging Business Rules...4 Data access layer...5 Rules layer...6 Presentation layer...6 User interface layer...7 hardware configuration...7 Data Services: Synchronization... 8 Data Services: Data Security... 9 Record-level security Field-level security Sales Client feature security Support Client feature security Data Services: User Connection Management Customization and Integration Client customization Software Development Kit (SDK) Front office application integration Communicating with other applications from Controlling from other applications Integration in a Web environment Real-time integration with back office data Batch integration with back office data Summary About Sage Software End Notes... 17
3 v6 Architecture, Customization and Integration Introduction Businesses today demand that all their vital data work together to serve the overall needs of the company. What were once discrete silos of information for example, customer data, financials, manufacturing status all are coming together to provide managers with views of their business that they never had before. Of course, making all these disparate sources of information work as one is no easy task. It requires IT solutions that can readily share information and be customized to take advantage of it. was designed and built to provide an affordable, highly reliable, easily customizable, and quickly usable customer relationship management (CRM) solution for driving sales performance in small to mid-sized businesses. With its Web-enabled architecture, provides sales tools to users via networked PCs, laptops, Web browsers, and handheld devices. Data synchronization supplies the same data, Microsoft Windows user interface, and customizations as the networked software to disconnected users. Administration and maintenance of does not require a dedicated IT staff. The Architecture has grown from its client/server roots to a tiered architecture. Network and Web clients for all modules utilize a central database. Data access is provided by the OLE DB (Object Linking and Embedding Database) Provider, which enforces data security and synchronization logging. Tiered Architecture Concept What were once discrete silos of information for example, customer data, financials, manufacturing status all are coming together to provide managers with views of their business that they never had before. In a tiered architecture, the data and presentation are separated into distinct application layers. The user interface layer uses the underlying presentation layer to provide data viewing and manipulation services to the user. The rules layer enforces business and data rules as a service to the presentation layer. The rules layer accesses the data layer (the database) through a data access layer. Table 1. Tiered architecture This model makes applications more scalable. Instead of each client application consuming resources to access the data layer directly, clients communicate with the rules layer. The rules layer can support many clients, thereby reducing resource consumption and improving scalability. Data services such as connection pooling, 2004 Sage Software, Inc. All rights reserved. 3
4 6.0 Architecture, Customization and Integration translation, security, and application logging can be shared across the client population. 1 Architecture Before version 6.0, the application was a two-tiered client/server application. With two-tiered applications, the client process handles the presentation and business logic, including business rules, data logging for synchronization, and user security. Data can be stored on a separate database server or on the same machine as the client for offline (remote) access. The client application connects directly to the data source for the lifetime of the application. Data access is through the Borland Database Engine (BDE) or Open Database Connectivity (ODBC). Customization requires an Application Programming Interface (API) layer to enforce the business logic, security, and sync logging for remotes. The v6 release brings a tiered architecture to. The v6 release brings a tiered architecture to. Business Rules Security Sync Logging Business Rules Figure 1. Before and After Sage Software, Inc. All rights reserved.
5 v6 Architecture, Customization and Integration Table 2. The Tiered Architecture The data layer is the relational database layer. supports Microsoft SQL Server including Microsoft Data Engine (MSDE) and Oracle relational databases. Data access layer The basic data access layer is the native database OLE DB Provider. The Microsoft OLE DB Provider for SQL Server allows ActiveX Data Object (ADO) to access Microsoft SQL Server. The OLE DB Provider for Oracle allows ADO to access an Oracle database. The OLE DB Provider extends the functionality of the native database OLE DB Provider by implementing extended interfaces that are not natively supported by the database. The OLE DB Provider allows ADO to access data without the need for a proprietary API. The OLE DB Provider (technically, a service provider) adds three services to the native database OLE DB (Data) Provider, which are not natively supported. These services are internal to the OLE DB Provider and used automatically via the standard ADO interface no additional or proprietary ADO methods are required. These services bridge the data and presentation layers, and contain some rules layer functions. The OLE DB Provider automatically: The OLE DB Provider allows ADO to access data without the need for a proprietary API. Performs data logging, and creates transaction exchange files (TEFs) for synchronization of data to remote users; Enforces field- and record-level data security on all queries passed to the database; and Manages user connections to the database and enforces licensing. The services are implemented as separately compiled components that can be swapped in and out in the future. This offers great flexibility, enabling changes to the configuration by adding and removing services or by replacing a service with one implemented by an authorized third party, for example. This also helps move more data logic out of the presentation layer (the clients) and into the rules layer. Services can be located on the same machine or distributed across different machines. The OLE DB Provider is not limited to Clients. Microsoft Visual Basic, Application Service Provider (ASP) pages, Crystal Reports, or any other 2004 Sage Software, Inc. All rights reserved. 5
6 6.0 Architecture, Customization and Integration application that uses a standard OLE DB connection may access data as a client. The interface is standard Microsoft ADO, requiring no proprietary API calls to access the data. These data services enforce the data rules and can be considered part of the rules layer, as described in the next section. Each of these services will be discussed in more detail in later sections. Connection management is an important aspect of the new architecture. In older versions of, each instance of the client created a connection to the database upon user login and held that connection, whether it was being used or not, until the user logged out. This restricted scalability because only a limited number of connections to the database could be made at any one time. With v6.0, a pool of connections is available for use on the Server. For each client query, a connection is used from the pool and released when execution of the query is complete. Clients do not hold multiple database connections open while the user is logged in. This improves scalability because typical use involves a salesperson logging in, executing one or two queries to retrieve needed information, and then staying logged in while performing some other activity, such as talking with a client on the phone while referring to the information just retrieved, but not making any more queries. 2 Rules layer Windows clients and the Web host handle business rules. They also control all logic that deals with the flow of data, for example, If A happens, then do B, C, and D. Data rules are handled by the OLE DB Provider, which spans the rules and data access layers. Data rules include the logic required for synchronization, field and record security, and user connections and licensing. The OLE DB Provider controls access to the database and uses the native database data providers (SQL Server or Oracle) to access the data layer. Using Architect, the objects, or plugins, can be easily customized to fit the needs of the customer or individual user. Presentation layer The Sales and Support Clients have a unique presentation layer. The user interface views, basic scripts, reports, document templates, and all other customizable aspects of the clients are stored as objects in the database and retrieved as needed. The clients retrieve these objects from the database or from cache and display them as the user interface. A key benefit of this approach is that remote, disconnected users have exactly the same user interface as network users. Security, data logging for synchronization, and connection management are moved out of the presentation layer, into the OLE DB Provider. This gives a more flexible and organized architecture. Using Architect, the objects, or plug-ins, can be easily customized to fit the needs of the customer or individual user. Additionally, the plug-ins are part of the database so they synchronize to remote users automatically no need to deploy and install each customization update to the clients. See Customization and Integration section of this paper for more information about customization Sage Software, Inc. All rights reserved.
7 v6 Architecture, Customization and Integration The presentation layer of all Web products has two parts: the template entry in the database and the actual DHTML or HTML pages. The Web Manager stores a list of templates in the database that are essentially pointers to the actual Web pages. The templates contain special tags and are referenced through the Web Host to enable security and hypertext link resolution, as well as to manage previous versions. Because templates are HTML files, they contain tags that serve as commands specifying how part or all of an HTML page should be structured. Normal HTML tags can be used to perform simple tasks, such as italicizing a word or phrase. More complex actions, such as some database interactions, require custom tags. supports not only standard HTML tags, but also 13 custom tags that request information for the Web Client or other Web products. Custom tags are compatible with HTML 1.0 and higher. When a Web client calls a URL, the Web Host uses the URL to find the raw template page, reads the tags in the template, and replaces the tags with live data, which is sent to the browser as DHTML and HTML pages. The Web Host is implemented as an Internet Information Server (IIS) Internet Server Application Programming Interface (ISAPI) interface (Web DLL). User interface layer has four primary clients that serve as the user interface. Sales Client is a Windows application that provides a customizable interface for sales and marketing functions. Support Client is a Windows application that provides a customizable interface for customer service and technical support functions. Sales Web Client is a customizable browser-based interface for sales functions. WebTicket is a customizable browser-based interface for customer support functions. In addition, there are several browser-based interfaces to specific functions. These include a LeadCapture form to submit contact information from a public website directly to ; and a Web phone interface that provides contact, calendar, and activity information on an Internet-enabled phone. Using Architect and Web Manager, most of the user interface can be easily customized to fit the needs of the customer or individual user. Read more information about customization in the Customization and Integration section of this paper. hardware configuration The architecture works with many hardware configurations. For example, the various servers can be housed on separate computers or combined as required by the customer. The following diagram represents a basic network configuration to support several users and all components. Refer to the Planning Guide and Implementation Guide for hardware details and recommendations based on specific requirements. Using Architect and Web Manager, most of the user interface can be easily customized to fit the needs of the customer or individual user Sage Software, Inc. All rights reserved. 7
8 6.0 Architecture, Customization and Integration Remote users work with their individual databases on their own machines. Remote Offices can support network users who connect directly to the Remote Office database. Figure 2. A typical hardware configuration. Data Services: Synchronization Data synchronization enables remote salespeople to access up-to-date corporate data on their disconnected mobile devices. The main office contains the host database, the central set of shared synchronization folders, and the Synchronization Server. It supports all users who connect to the host database. remotes include both Remote users and Remote Offices. Remote users work with their individual databases on their own machines. Remote Offices can support network users who connect directly to the Remote Office database. All remotes (users and offices) have a subset of synchronization folders and either the Synchronization Client or the Remote Office Synchronization Server Sage Software, Inc. All rights reserved.
9 v6 Architecture, Customization and Integration Figure 3. The Synchronization Process As each user makes changes to his or her database, tracks the field-level changes and stores them in transaction exchange files (TEFs). tracks the time and date of the change, the user and site that performed the change, and other details. Tracking field-level details about each transaction makes possible sophisticated conflict resolution, efficient processing, and data rollback so erroneous updates can be undone. Unlike synchronization systems based on index scanning or stored procedure schemes, logging makes it possible for updates to be applied across different database platforms. Transaction log files generated by a SQL Server or MSDE database can be applied to an Oracle database with no conversion required. The Synchronization Client for the Remote user or Remote Office transfers TEFs to the shared Sync Logging folders at the Main Office. It also moves files from the shared Sync Logging folders to the remote synchronization folders. These TEFs are then applied to the remote database, so it contains the same information as the host database. Note that the remotes never connect directly to the host database during this process, but only to the shared Sync Logging folders at the Main Office. The Synchronization Server at the main office processes the TEFs received from the Remote user or Remote Office and applies them to the host database. If other remotes also need this updated information, it generates TEFs for them. Additionally, the Synchronization Server processes the TEFs generated by users at the main office, creating TEFs for the Remote users or Remote Offices that require those updates. This ensures that all the databases eventually contain the same information as the host database. Data Services: Data Security Unlike synchronization systems based on index scanning or stored procedure schemes, logging makes it possible for updates to be applied across different database platforms. provides a level of data security not available in the underlying database. The OLE DB Provider enforces this level of security Sage Software, Inc. All rights reserved. 9
10 6.0 Architecture, Customization and Integration Account ownership defines which users have access to an account and the contacts, opportunities, and other information associated with that account. Record-level security record-level security is based on the concept of account ownership. Account ownership defines which users have access to an account and the contacts, opportunities, and other information associated with that account. There are four types of account ownership: Everyone ownership. No security profile prevails. As a result, any user in the system may view, edit, or delete information pertaining to the account, or even delete the account itself. Everyone (View Only) ownership. All users have read-only privileges to the account. Individual user ownership. Security is based on individuals profile security settings. Personal contacts are private and cannot be accessed by others. Personal contacts can be made public, but public contacts cannot be made personal. Team ownership. A team is a group of users who have access to the same accounts. Some team members are designated as team owners and can change account ownerships. All other users on the team have designated configurable security profiles. Each security profile specifies what kind of access each user has to the data, such as read/write authority or read-only. Users can belong to more than one team. Field-level security Field-level security controls data access at the table or field level. Field-level security can be enabled when a table is created through the Database Manager. One-to-many tables do not allow for field-level security. Security profiles are managed through the Security Profile Manager. When a user is added to a team, the user s default field-level security profile is used. Once added to a team, the user s field-level security profile for the team-owned accounts can be changed. Changing a user s field-level security profile in one team does not affect that user s default field-level security profile in any other team to which they belong. Members of the same team may have different profiles. The no access, read only, or read/write access rights may be applied to the fields in a table that has field-level security enabled. One table can contain the same access for all fields. Individual fields can also be assigned different access rights. Sales Client feature security The Sales Client permits the administrator to further restrict users ability to employ specific features of the software: Addition and deletion of accounts, contacts, and opportunities can be restricted. By default, addition and deletion are permitted. Users must have security rights to accounts, contacts, or opportunities to have add or delete rights. The add-and-delete rights set in Feature Security control menu access rights. Users can restrict menu and toolbar functions Sage Software, Inc. All rights reserved.
11 v6 Architecture, Customization and Integration enables users to manage access and calendar permissions to other users calendars. By default, all users have access to all other users calendars and can view activities in single-user or multi-user views. The following rights can be set: Add. The user can schedule calendar items. Edit. The user can modify scheduled calendar items. Delete. The user can delete scheduled calendar items. Sync. Sends the user all activities for the user selected on the Calendar Control list. If cleared, the user can still send activities but won t receive all activities for that user. Support Client feature security The Support Client permits the administrator to further restrict functions the user can perform. Support Client feature security rights and restrictions include: The ability to restrict whether a user can add, delete, and edit accounts, contacts, tickets, defects, return merchandise authorizations (RMAs), and procedures. The default setting is to allow insertion and deletion. If the user can add records, editing and viewing is permitted. Users can restrict lookup functions. Users can restrict menu and toolbar functions. The Support Client permits the administrator to further restrict functions the user can perform. Data Services: User Connection Management User connection management is implemented as a data service as part of the OLE DB Provider. This service enforces licensing to determine who can log on to and who is actively connected to. This service improves product licensing flexibility and management. One new feature enables the administrator to view the list of individuals logged onto. Customization and Integration Client customization Architect is a Visual Basic-like development environment. It is used to build, edit, and manage plug-ins. Plug-ins are objects for customizing standard functionality. They are also used to add custom functionality to. Plug-ins are used to create detailed procedures and to customize the appearance of screens in, as follows: Create forms. A form is a user interface that captures or displays information. Existing forms can be modified and custom forms created. Create Basic scripts. Basic scripts can be used to string together a series of Basic functions and commands used by forms and reports, or 2004 Sage Software, Inc. All rights reserved. 11
12 6.0 Architecture, Customization and Integration called from menu or toolbar items. Basic scripts can be created to perform specific functions in. Build Sales Client processes. Processes are used to execute a sequence of tasks over a set time period. Processes can be built to perform repetitive tasks or to implement sales processes. Customize Sales Client menus and toolbars. Custom menus and toolbars can be created and new items added to existing menus and toolbars. Create or modify reports. The reports included with can be modified or new reports can be created using Crystal Reports. Reports are based on the standard tables (Contact, Account, Ticket, Defect, and so on) or on any custom table in the database. Build templates. Mail Merge templates for letters, memos, and fax cover sheets are included with. New templates can be created or the existing ones edited. Create SQL scripts. SQL scripts can be created to perform specific functions used by views, and reports, or called from menu or toolbar items. The Architect also includes features for building components used by plug-ins, such as pick lists and calculated fields. The Database Manager enables you to extend the database schema to incorporate custom tables that are automatically synchronized to remote users. The Join Manager and Lookup Manager help manage table relationships and searches. To facilitate interaction between and third-party applications, developers can use the standard ADO interface to retrieve and update data. Software Development Kit (SDK) To facilitate interaction between and third-party applications, developers can use the standard ADO interface to retrieve and update data. ADO accesses the database via the OLE DB Provider, which performs data logging and security functions that required a proprietary API with older versions of. The application programming interface (SLAPI) is also available. In most cases, proprietary SLAPI is no longer required, but it remains for backwards compatibility. SLAPI is a set of high-level functions that enable other applications to interact with the database. These functions include database access, table access, table functions, row functions, logging, and miscellaneous functions that provide information from the system. With the SDK you can easily add seamless integration from outside the clients. The SDK includes a set of sample programs that aid access to the underlying database from various languages outside the system. Part of the SDK, the Developer s Reference manual provides functions used to customize to meet specific needs. It includes information about using Visual Basic (VB) and SQL scripts to customize and modify. Basic functions that work with, with examples, are included for reference. The Architect is used to build and save your customized scripts and functions Sage Software, Inc. All rights reserved.
13 v6 Architecture, Customization and Integration The Web application programming interface (WAPI) is a set of routines, protocols, and tools for building or manipulating software applications. SLAPI is not supported on the Web, thus WAPI is used to provide quick and easy access to data, to create Web business rules for Web Client users, and to perform data validation or manipulation. offers 75 WAPI functions to aid in customization of Web products. Knowledge of basic HTML and Basic scripting are prerequisites for Web application customization. Actions are Basic scripts that provide quick and easy access to data. They are server-side scripting tools using a Basic-like language that includes special extensions for interactions with the database and Web Client. Use actions to perform data validation or manipulation against information from the database or posted via HTML forms. You can also use actions to create rules for fields and forms and to serve as business rules for Web Client users. Additionally, Active Server P ages (ASP, ASP.Net) and similar Web technology that supports ADO may use the OLE DB Provider without the need for the proprietary API. Front office application integration Because is used as the primary front office solution in many implementations, integrating data with other systems is a frequent necessity. As systems are more prevalently used to aid interactions with customers, full-featured integrations between these systems is needed to avoid data inconsistencies and other anomalies that can affect the overall customer service experience. Real-time integration involves passing data from another client application or database to the application, and vice versa, while user interactions with the system are taking place. To facilitate the most efficient use of the systems, this type of integration can also require the manipulation of the and/or OEM custom applications in response to user actions. Disconnected users require data synchronization. provides a robust synchronization scheme to handle this data transfer, as described in Data Services: Synchronization section. It uses ADO to interface to the OLE DB Provider, handling synchronization data logging automatically, with no additional development effort. Real-time integration involves passing data from another client application or database to the application, and vice versa, while user interactions with the system are taking place. Communicating with other applications from Depending on the availability and feature set of an open interface, integration from to another application is straightforward. If the interfaces in the application support Component Object Model (COM), then object manipulation can be developed and executed with VBA extensions (VBScripts) in, enabling communication with the application. These scripts are executed without any user interruption. Alternatively, if the application interfaces support a scripting environment that can read the Windows registry, then registry keys and values can be manipulated to pass data from to the application Sage Software, Inc. All rights reserved. 13
14 6.0 Architecture, Customization and Integration If the application has neither a COM interface nor a scripting environment, manipulation can be accomplished through command line parameters. This is a limited method of communication, however, because communication to the called application must be done by loading an executable and data cannot be passed to the application while it is open. If the application does not support any external interfaces or command line parameters, or if direct database manipulation is desired or required (for example, in cases where there is no client application), a few options must be considered: uses Microsoft ADO for data access and has the ability to read and write data to many back-end platforms (such as Oracle, Sybase, DB2) through custom VBScripts when the appropriate driver is present. uses Microsoft ADO for data access and has the ability to read and write data to many back-end platforms (such as Oracle, Sybase, DB2) through custom VBScripts when the appropriate driver is present. This functionality allows programmers to design behind the scenes application integrations that will manipulate data in another database based on actions the user takes in. The opposite can also be accomplished. For example: A user adds customer data with a certain flag to. A custom script can be triggered in the client to verify the data against another back-end database. If verification is obtained, then another call can be made to the database to find additional information about the newly added customer, such as his or her credit limit. This additional data can be written to the database. If verification is not obtained, the user can be halted from adding the data. The limitation of this example is that the bound data objects in cannot be bound to data that resides outside of the database. Integration must occur completely through ADO and custom scripts, and, although it is possible to populate some controls (data grids are a notable exception) in the user interface with data obtained by scripts that query another database, this adds more complexity to the project. A custom application can be developed to act as an interface to the application database in lieu of the Client. The manipulation of this application can occur through COM object manipulation, registry value settings, or command line parameters as described above. If this custom application is going to write data to the database, it must use ADO to read and write data. If ADO is not supported, SLAPI must be used. This is required to notify the synchronization engine that database changes have occurred. Otherwise, Remote users will not receive data changes made by the custom application. A Web-based application can be developed to act as an interface to the application database. A browser control can be displayed in the user interface to display the information. This requires an Internet connection and does not serve disconnected users. A custom ActiveX control can be developed to act as an interface to the application database. The control, when properly implemented, can be used much as a native control within the Client user interface. This gives extreme flexibility but is more complex to develop Sage Software, Inc. All rights reserved.
16 6.0 Architecture, Customization and Integration database via the OLE DB Provider. The OLE DB Provider informs the synchronization engine that database changes have occurred so that changes to data made by the application are communicated to the host database. Real-time back office integration involves the movement of data between two databases on a real-time (or near real-time) basis. As data is added to one system, a mechanism is invoked that causes this data to be inserted or moved into another database. Real-time integration with back office data Real-time back office integration involves the movement of data between two databases on a real-time (or near real-time) basis. As data is added to one system, a mechanism is invoked that causes this data to be inserted or moved into another database. Batch back office integration involves passing data to another database from the database and vice versa on a scheduled basis. This type of integration is transparent to users because it does not affect the application environment. Real-time data migration between a host database and most other databases can be accomplished by creating a custom application to move data. The custom application runs constantly, watching for changes in data. The changes can most easily be trapped at the database level by writing changes to shadow tables that the custom application constantly queries. The actual data tables should not be constantly queried because this adds tremendous overhead to the database server. When the custom application finds new data, it transfers the data between the systems. Any manipulation of data by a custom data migration application must use the OLE DB Provider or the API. This is required to notify the synchronization engine that database changes have occurred. Otherwise, Remote users will not receive changes to data made by the custom application. Batch integration with back office data Data migration between and most other databases can be accomplished as a batch process by creating a custom application to move data on a scheduled basis. Because Remote users are present, all database changes in must be written through the OLE DB Provider or the API. This is required to notify the synchronization engine that database changes have occurred. Otherwise, Remote users will not receive changes to data made by the custom application. The custom application can be written in any language that supports function calls in a 32-bit Windows DLL. provides headers for the DLL functions for Visual Basic, C++, and Delphi Sage Software, Inc. All rights reserved.
17 v6 Architecture, Customization and Integration Summary Increased demand for business applications to work together has spurred many solution providers to find ways for their products to share and manipulate one another s data. has long been recognized as a leader in such integration and customization. With the release of v6.0, the product s ability to communicate with other applications and to be controlled by them has been enhanced. This has been accomplished through: The adoption of a tiered architecture; The lack of a requirement for proprietary APIs to access data; Flexible security settings; Efficient handling of user connections; and A variety of communication and control methods. Virtually every major system implementation requires customization. The ease with which customizations can be made is an important consideration when choosing which business solution to purchase. Generally speaking, the more adaptable the solution is to the business s overall operation, the better it will meet the organization s needs. The ease with which customizations can be made is an important consideration when choosing which business solution to purchase. About Sage Software Sage Software offers leading business management products and services that give more than 2.3 million small and mid-sized customers in North America the insight for success throughout the lives of their businesses. Its parent company, The Sage Group plc (London: SGE.L), supports 4.3 million customers worldwide. For more than 25 years, Sage Software has delivered easy-to-use, scalable and customizable applications through its portfolio of leading brands, including Abra, ACCPAC, ACT!, BusinessVision, CPASoftware, FAS, MAS 90, MAS 200, MAS 500, MIP, Peachtree,, Timberline, among many others. For more information, please visit the Web site at or call (866) End Notes For more on tiered architecture, see the article Application Architecture: An N-Tier Approach, by Robert Chartier found on Some of the information presented here is based on this article. For background information on ADO and OLE DB Providers, visit: For details on synchronization, refer to the technical white paper Data Synchronization Technology for Mobile CRM Users Sage Software, Inc. All rights reserved. 17
18 8800 North Gainey Center Drive, Suite 200 Scottsdale, AZ The information contained in this document represents the current view of Sage Software, Inc. on the issues discussed as of the date this document was prepared. Sage Software cannot guarantee the accuracy of any information presented after the date of publication. The capabilities, system requirements and/or compatibility with third-party products described herein are subject to change without notice. Contact Sage Software for the most current information. Always consult a network specialist to discuss the security risks involved before implementing any Internet solution. Sage Software is not responsible for the content or maintenance of third-party Web sites referred to herein. This document is for informational purposes only and may not be distributed to third parties. SAGE SOFTWARE MAKES NO WARRANTIES, EXPRESSED OR IMPLIED, IN THIS DOCUMENT Sage Software, Inc. All rights reserved. Reproduction in whole or in part without permission is prohibited. Sage Software and the Sage Software product and service names mentioned herein are registered trademarks or trademarks of Sage Software, Inc. and/or its affiliated entities. Platinum is a registered trademark licensed from Platinum Technology International, Inc. BatchMaster is a trademark licensed from eworkplace Solutions, Inc. All other trademarks are the property of their respective owners. 12/
Questions to address while reviewing CRM software Conducting a CRM needs assessment doesn t have to be hard or intimidating. Sage Software has put together the top 10 (plus one) list of things you ll want
Sage Accpac ERP offers the freedom of choice, seamless integration, high performance, and reliability that forwardthinking companies rely on to increase profitability and gain competitive advantage. World-Class
Sage CRM SalesLogix Sage CRM SalesLogix Data Synchronization Technology for Remote CRM Users How to successfully synchronize your data so remote users can share up-to-date customer and sales information
Installation and System Configuration Version 7.0 Sage MAS 500 ERP 4AIN1050-0905 1996-2005 Sage Software, Inc. All rights reserved. The Sage Software logo and the Sage Software product and service names
It s about customers. M Microsoft Customer Relationship Management PUT YOUR CUSTOMERS AT THE CENTER OF YOUR BUSINESS Microsoft Customer Relationship Management THE GOAL: THE NEED: THE SOLUTION: Provide
The Benefits of CRM Internet Architecture Sage CRM Architecture White Paper 2 Contents Introduction... 3 The Sage CRM Internet Architecture...... 4 Interface... 4 Business Logic... 4 Database Access...
Sage SalesLogix Implementation Guide Version 8.0 Developed by Sage SalesLogix User Assistance Sage SalesLogix Implementation Guide Documentation Comments Copyright Address This documentation was developed
4D and SQL Server: Powerful Flexibility OVERVIEW MS SQL Server has become a standard in many parts of corporate America. It can manage large volumes of data and integrates well with other products from
Act! Synchronization Understanding Act! Synchronization Table of Contents Introduction... 1 Synchronization Architecture... 1 Methods of Synchronizing... 1 What Is Synchronized... 4 Features and Capabilities
BillQuick Web i Time and Expense User Guide BQE Software Inc. 1852 Lomita Boulevard Lomita, California 90717 USA http://www.bqe.com Table of Contents INTRODUCTION TO BILLQUICK... 3 INTRODUCTION TO BILLQUICK
It s about customers. M Microsoft Customer Relationship Management PUT YOUR CUSTOMERS AT THE CENTER OF YOUR BUSINESS Microsoft Customer Relationship Management THE GOAL: THE NEED: THE SOLUTION: Provide
Page 1 A. Title Client/Server Technology B. Introduction Client/server is a network architecture that divides functions into client and server subsystems, with standard communication methods to facilitate
Installation and System Configuration Version 7.30 Sage MAS 500 ERP 4AIN1080-1009 1996-2009 Sage Software, Inc. All rights reserved. Sage, the Sage logos, and the Sage product and service names mentioned
Sage 100 ERP Installation and System Administrator s Guide This is a publication of Sage Software, Inc. Version 2014 Copyright 2013 Sage Software, Inc. All rights reserved. Sage, the Sage logos, and the
Sisense Product Highlights Introduction Sisense is a business intelligence solution that simplifies analytics for complex data by offering an end-to-end platform that lets users easily prepare and analyze
IBM RATIONAL PERFORMANCE TESTER Today, a major portion of newly developed enterprise applications is based on Internet connectivity of a geographically distributed work force that all need on-line access
Deltek Vision 7.0 LA Technical Readiness Guide May 15, 2012 While Deltek has attempted to verify that the information in this document is accurate and complete, some typographical or technical errors may
TRUST & WEALTH MANAGEMENT Forward Thinking Financial Technology INNOVEST SOLUTIONS Every day, you ask your clients to envision a better future. Then, you create a growth plan to help them get there. The
Base One's Rich Client Architecture Base One provides a unique approach for developing Internet-enabled applications, combining both efficiency and ease of programming through its "Rich Client" architecture.
Label Gallery Software for Microsoft Windows Terminal Services and Citrix MetaFrame White Paper Version 20100716 2009 SATO CORPORATION. All rights reserved. http://www.satoworldwide.com email@example.com
Inmagic Content Server v9.0 Standard Configuration Technical Guidelines 5/2006 Page 1 of 15 Inmagic Content Server v9 Standard Configuration Technical Guidelines Last Updated: May, 2006 Inmagic, Inc. All
EMC AVAMAR INTEGRATION WITH EMC DATA DOMAIN SYSTEMS A Detailed Review ABSTRACT This white paper highlights integration features implemented in EMC Avamar with EMC Data Domain deduplication storage systems
Title Page Hosted Payment Page Guide ACI Commerce Gateway Copyright Information 2008 by All rights reserved. All information contained in this documentation, as well as the software described in it, is
How to Prepare for the Upgrade to Microsoft Dynamics CRM 2013 (On-premises) COMPANY: Microsoft Corporation RELEASED: September 2013 VERSION: 1.0 Copyright This document is provided "as-is". Information
Interworks Interworks Cloud Platform Installation Guide Published: March, 2014 This document contains information proprietary to Interworks and its receipt or possession does not convey any rights to reproduce,
BusinessObjects Enterprise XI Release 2 Administrator s Guide BusinessObjects Enterprise XI Release 2 1 Patents Trademarks Copyright Third-party contributors Business Objects owns the following U.S. patents,
SDL Tridion R5 Content Management Implementation Guide 5.3 SP1 Read this document to implement and learn about the following Content Manager features: Publications Blueprint Publication structure Users
Inmagic Content Server v1.3 Technical Guidelines 6/2005 Page 1 of 15 Inmagic Content Server Standard and Enterprise Configurations Technical Guidelines Last Updated: June, 2005 Inmagic, Inc. All rights
Phire Architect Hardware and Software Requirements Copyright 2014, Phire. All rights reserved. The Programs (which include both the software and documentation) contain proprietary information; they are
SDL Tridion R5 Content Management Implementation Guide 5.3 SP1 Read this document to implement and learn about the following Content Manager features: Publications Blueprint Publication structure Users
Installation Guide NetIQ AppManager April 2016 www.netiq.com/documentation Legal Notice NetIQ AppManager is covered by United States Patent No(s): 05829001, 05986653, 05999178, 06078324, 06397359, 06408335.
Introducing Microsoft SQL Server 2000 CHAPTER 1 By the end of this chapter, you will be able to Describe the components and architecture of SQL Server 2000 List the editions of SQL Server 2000 and their
FileMaker 11 ODBC and JDBC Guide 2004 2010 FileMaker, Inc. All Rights Reserved. FileMaker, Inc. 5201 Patrick Henry Drive Santa Clara, California 95054 FileMaker is a trademark of FileMaker, Inc. registered
the Availability Digest Raima s High-Availability Embedded Database December 2011 Embedded processing systems are everywhere. You probably cannot go a day without interacting with dozens of these powerful
MAS 200 MAS 200 for SQL Server Introduction and Overview March 2005 1 TABLE OF CONTENTS Introduction... 3 Business Applications and Appropriate Technology... 3 Industry Standard...3 Rapid Deployment...4
EVALUATION OF SERVER-SIDE TECHNOLOGY FOR WEB DEPLOYMENT Dr. Alexander Pons, University of Miami, firstname.lastname@example.org ABSTRACT The deployment of Web applications consisting of dynamic content requires the selection
Last Updated: July 2011 STATISTICA Enterprise Server Security STATISTICA Enterprise Server Security Page 2 of 10 Table of Contents Executive Summary... 3 Introduction to STATISTICA Enterprise Server...
Zendesk + Salesforce Step-by-Step Guide to Integrating Zendesk and Salesforce www.zendesk.com 2 Table of Contents Introduction Getting Started Page 1 Step 1: Installing the Zendesk for Salesforce App in
Home About us Contact us Careers Online Resources Site Map Products Demo Center Support Customers Resources News Download Article in PDF Version Download Diagrams in PDF Version Microsoft Partner Conference
A Performance Comparison of Web Development Technologies to Distribute Multimedia across an Intranet D. Swales, D. Sewry, A. Terzoli Computer Science Department Rhodes University Grahamstown, 6140 Email:
HP Web Jetadmin Database Connector Plug-in reference manual Copyright notice 2004 Copyright Hewlett-Packard Development Company, L.P. Reproduction, adaptation or translation without prior written permission
Sage Accpac CRM 5.8 Self Service Guide Copyright 2005 Sage Technologies Limited, publisher of this work. All rights reserved. No part of this documentation may be copied, photocopied, reproduced, translated,
The CRM software that does it all. Oncontact CRM 7 The CRM software that does it all. Oncontact CRM 7 is the answer. CRM 7 gives your company the competitive edge it needs with a flexible and effective
Table of Contents Introduction Audience At Course Completion Prerequisites Microsoft Certified Professional Exams Student Materials Course Outline Introduction This three-day instructor-led course provides
SQL Server An Overview SQL Server Microsoft SQL Server is designed to work effectively in a number of environments: As a two-tier or multi-tier client/server database system As a desktop database system
IBM i2 Analyst s Notebook SDK Product overview Contents 1 Introduction 2 Who should read this white paper 2 Potential benefits of i2 Analyst s Notebook SDK 2 Key features of i2 Analyst s Notebook SDK 4
Microsoft Terminal Server and Citrix Presentation Server Deployment Environments Understanding the use of Act! in a Terminal Server or Citrix Presentation Server environment Table of Contents Introduction...
SAP Technical Brief SAP Gateway Objectives Unlock the Value of Your Microsoft and SAP Software Investments Bridging the integration gap between SAP and Microsoft environments Bridging the integration gap
QAD Enterprise Applications Training Guide Demand Management 6.1 Technical Training 70-3248-6.1 QAD Enterprise Applications February 2012 This document contains proprietary information that is protected
ORACLE BUSINESS INTELLIGENCE SUITE ENTERPRISE EDITION PLUS PRODUCT FACTS & FEATURES KEY FEATURES Comprehensive, best-of-breed capabilities 100 percent thin client interface Intelligence across multiple
PATROL From a Database Administrator s Perspective September 28, 2001 Author: Cindy Bean Senior Software Consultant BMC Software, Inc. 3/4/02 2 Table of Contents Introduction 5 Database Administrator Tasks
vcloud Automation Center 6.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions
SysPatrol Server Security Monitor User Manual Version 2.2 Sep 2013 www.flexense.com www.syspatrol.com 1 Product Overview SysPatrol is a server security monitoring solution allowing one to monitor one or
for Sage 100 ERP Library Master Document 2012 Sage Software, Inc. All rights reserved. Sage Software, Sage Software logos, and the Sage Software product and service names mentioned herein are registered
Progress DataDirect Connect DATA SHEET PROGRESS DATADIRECT QA AND PERFORMANCE TESTING EXTENSIVE TESTING ENSURES DATA CONNECTIVITY THAT WORKS Progress DataDirect ODBC, JDBC and ADO.NET data connectivity
Inmagic Content Server Workgroup Configuration Technical Guidelines 6/2005 Page 1 of 12 Inmagic Content Server Workgroup Configuration Technical Guidelines Last Updated: June, 2005 Inmagic, Inc. All rights
Turning ClearPath MCP Data into Information with Business Information Server White Paper 1 Many Unisys ClearPath MCP Series customers have Enterprise Database Server (DMSII) databases to support a variety
Compaq Batch Scheduler for Windows NT Mainframe-Caliber Automated Job Scheduling Software for Windows NT This white paper addresses extending the capabilities of Windows NT to include automated job scheduling
Reporting and Data Access Methods Get the most flexibility in creating reports, lists, or other documents Table of Contents Introduction... 1 Data Access Overview... 1 OLE DB Reporting Provider... 2 Background
January 2013 Page 1 This document provides information on how to configure, use, and manage the. www.deltav.com January 2013 Page 2 Table of Contents Introduction... 3 Database Technology... 3 Database
Outbound E-mail 2009 Upgrade Manual SDL Tridion Development Lab BV 1999-2009 SDL Tridion Development Lab BV NOTICE: The accompanying software package is confidential and proprietary to SDL Tridion Development
A Guide To Evaluating a Bug Tracking System White Paper By Stephen Blair, MetaQuest Software Published: October, 2004 Abstract Evaluating a bug tracking system requires that you understand how specific
Collaboration solutions for midsized businesses Buyer s guide Increase productivity by improving collaboration across and beyond your business. Give employees access to the information, people and resources
data sheet Database Connectors Executive Overview Database Connectors are designed to bridge the worlds of COBOL and Structured Query Language (SQL). There are three Database Connector interfaces: Database
Work Smart by Microsoft IT What s new in Access 2013 Customization note: This document contains guidance and/or step-by-step installation instructions that can be reused, customized, or deleted entirely
Siebel Installation Guide for UNIX Siebel Innovation Pack 2013 Version 8.1/8.2, Rev. A April 2014 Copyright 2005, 2014 Oracle and/or its affiliates. All rights reserved. This software and related documentation
Table of Contents Introduction Audience Prerequisites Microsoft Certified Professional Exams Student Materials Course Outline Introduction This three-day instructor-led course provides students with the
Kaseya Kaseya IT Automation Framework An Integrated solution designed for reducing complexity while increasing productivity for IT Professionals and Managed Service Providers. The powerful, web-based automation
KofaxExpress 3.1.0 Installation Guide 2012-05-01 2008-2012 Kofax, Inc., 15211 Laguna Canyon Road, Irvine, California 92618, U.S.A. All rights reserved. Use is subject to license terms. Third-party software
Microsoft Dynamics GP 2013 Architecture White Paper This document describes the architecture for Microsoft Dynamics GP. Date: February 2013 Table of Contents Introduction... 4 Client Types... 4 Desktop
HP Quality Center Upgrade Preparation Guide Document Release Date: November 2008 Software Release Date: November 2008 Legal Notices Warranty The only warranties for HP products and services are set forth
SageCRM Product Overview A complete view of your organization s customer interactions SageCRM is an easy-to-use, fast-to-deploy, feature-rich Customer Relationship Management solution with out-of-the-box
7.0 Self Service Guide Copyright 2010 Sage Technologies Limited, publisher of this work. All rights reserved. No part of this documentation may be copied, photocopied, reproduced, translated, microfilmed,
1 (11) Paperiton DMS Document Management System System Requirements Release: 2012/04 2012-04-16 2 (11) 1. This document describes the technical system requirements for Paperiton DMS Document Management
INFOIMAGE FOLDER ON WINDOWS NT Connector for Microsoft Exchange Unisys Getting Started Guide Copyright 1999 Unisys Corporation. All rights reserved. Unisys is a registered trademark of Unisys Corporation.
.CRF Electronic Data Capture and Workflow System for Clinical Trials Business challenge Most research takes place in different centers simultaneously. These are often located in different cities or even
Vijeo Citect Architecture and Redundancy Study Guide Version 7.30 Schneider-Electric Pty (Australia) Ltd 78 Waterloo Road Macquarie Park NSW 2113 Australia DISCLAIMER Schneider Electric makes no representations