SalesLogix v7.5 Sneak-Peek

SalesLogix v7.5 Sneak-Peek

Objective of Presentation
The content of this presentation has been designed to provide the reader with a high-level understanding of the key features being introduced in Sage SalesLogix v7.5 In addition to this content, Sage is hosting eight ‘Deep Dive’ Webcast sessions that provide additional and more detailed information, as well as practical examples of how to use the new features being introduced. These sessions are recorded and posted to Partners Online.

Presentation Contents
Usability/User-Interface Improvements List Management Mash-ups Personal Workspaces Comprehensive Web CRM Lead Management Web Services Process Orchestration Application Architect Improvements 3

Usability/User-Interface

User Experience Situation Problem
Market requires a product that is easy to use and makes users more efficient at their jobs Problem Interaction methods in Web client need to catch up to the Network client. Current User Interface does not guide the user; needs to be more intuitive. The look and feel can be improved to better match current industry standards. The market is constantly demanding products that are easier to use and that improve user efficiencies. The SalesLogix Network client has always had good user-interface features that make users more efficient. Prior to version 7.5, the SalesLogix Web client did not offer all of the user-interface strengths that the SalesLogix Network client offers. Also, the user-interface did not always guide the user as a good UI should, and was not always intuitive. SalesLogix 7.5 has made great strides in all of these areas. 5

User Experience Solutions General look-and-feel improvements
Enhanced Drag-and-Drop tabs Multi-Tab Expansion to the Middle Pane List Management Improvements Groups in Tabs UI Redesign Multi-Select & RMB Task Pane Interaction Summary View SalesLogix version 7.5 has greatly improved the look and feel of the Web client. These improvements include everything from simple look-and-feel improvements to significant user-experience and changes in functionality to enhance efficiencies. 6

User Experience: User Interface Clean-up
Header Toolbar Title Bar Groups Relocation Lookup Relocation Navigation Task Pane Footer The look-and-feel of the application has been improved to make the application easier to read and access data, provide more information with less space used and improvements to navigation. 7

User Experience: Header and Toolbar
Old New The Header and toolbar have had the following enhancements: Different look-and feel for buttons: The buttons on the toolbar now include a drop-down arrow control for easier access to the menus. Improved Icons: The icons used have been improved, improving the look and feel of the application Help button: The Help button has been removed from the toolbar and placed in the top right corner of the header Reminders: The Reminders button has been added to the tool bar and removed from the navigation bar. A visual indicator of the number of reminders has been added, and the button changes color when there are new reminders that have not been viewed Groups: The groups button and drop-down control has been remove from the Header and Tool bar section 8

User Experience: Title Bar, Groups, Lookup
Old New The title bar, groups and look-up control have been improved in the following ways: Tabs: Tabs have been added for easy access to groups and to look-up and look-up results. The tabs can easily be navigated with left/right arrows when there are more tabs than what can be displayed Groups button: The groups button has been improved to include navigation to all of a given user’s groups, as well as the ability to manage those groups by editing and deleting them. Look-up: The look-up control is now represented as a tab. The user can still execute the same, powerful look-ups by clicking on the tab at any time. Title for Data Type: The type of the data being displayed in the main view is now clearly described by a title in the title bar section. This makes it very easy for users to know exactly what data they are looking at. 9

User Experience: Navigation Bar
Hide/Show navigation bar using this control Old New The navigation bar has been improved in following ways: Hide/Show: The Navigation Bar can now be hidden or displayed through the use of a collapse button on the right-hand side of the Navigation Bar. This provides more space to display important information. Moving the cursor to the left side of the Navigation Bar makes the bar reappear New Icons: New icons improve the look and feel of the navigation bar Reminders button: The Reminders have been removed and added to the tool bar instead for easier access and visibility Grouping: The navigation bar buttons have been logically organized into functional areas that can be expanded or collapsed through an accordion-style interface Button Highlighting: The navigation bar will now clearly show the button that has been selected by using a highlight color to indicate that it has been selected. When something outside of the navigation bar is clicked on, such as the Options link, the navigation bar does not highlight any of the buttons. 10

User Experience: Task Pane
User can collapse and expand each task areas Task panes provide context-sensitive actions that can be applied to list or detail views A task pane area has been added to most of the list and detail views in the Web client. The task pane offers several components that provide functionality that makes it easier to work with the data in SalesLogix. These task panes have the following attributes: Context-aware: System knows what records are selected, or what detail record is being operated on. Each task that is performed through the task pane passes this context on to the action that is being taken. For example, if an activity is being scheduled, the system understand the context of the lead or contact that the activity is for. Pro-Active: The system anticipates the user needs by offering specific tasks that can be accomplished for a given view in SalesLogix. Expand / Contract: Task areas within the task pane can be expanded or collapsed as needed to provide more space for the task areas that the user is interested in accessing Properties: The contents of a given task areas, such as filters, can be personalized to show only the information that a specific user wants to see. Hide/Show: The user can hide/show the task pane ini the same way that they can hide/show the navigation bar 11

User Experience: Footer
Date and Idle or Logoff message appears here The footer in the Web client has been enhanced to display the following information: Copyright information Date and time Time idle and time before auto-logoff The system will now auto-logoff a user after 20 minutes of idle time 12

User Experience: Drag and Drop
User can drag and drop tabs in detail view. Shadow tab displayed during operation. Arrow indicator shows where tab will be after drop. The ability to drag and drop tabs to new locations has been added to the Web client. The following functionality has been added to make this experience easier for an end user: A shadow or ghost image is displayed the indicates the tab is being dragged. The image is a box with the name of the tab. Also, a green checkbox is displayed when the cursor is positioned in a place where the tab can be dropped. Otherwise, a red box with an ‘X’ is displayed, indicating that the tab cannot be successfully dropped in the current location of the cursor. An arrow indicating the position of the tab is displayed when the cursor is in a position that the tab can be dropped. 13

User Experience: Middle Pane/Multi-tab Expansion
Drag and Drop to middle pane displays blue line where new middle pane will be placed. SalesLogix 7.5 offers the ability for users to expand the middle panes that are visible and to use the scroll bar to navigate between them. There is no limit to the number of middle panes that can be dragged from the tab section into the middle-pane section. This feature is helpful to users who prefer to use the scrollbar to access their data instead of the tabs. Dragging and dropping tabs into the middle pane is easy to do. The user sees a shadow image with the name of the tab being dragged, and there is a green checkbox or a red ‘X’ box indicating whether or not the cursor is in a place where the tab can be dropped. There is also a blue line indicating the position of the tab after the drop has occurred. Shadow image with name of tab and green check-box indicates drag-an-drop in progress. 14

List Management

List Management Improvements
Situation: SalesLogix users will sometimes take longer to find information that they need Users need an easier way to build groups. SalesLogix Group Builder is a powerful tool for advanced, technical users, but does not address the requirements for non-technical users User need to select records and add them to an ad-hoc group Problems No easy way to build a temporary list to work from No easy way to manipulate the lists The process to create group is not easy enough for non-technical users Current SalesLogix users face challenges when creating and using lists or groups. SalesLogix, prior to version 7.5, offered group building and list management capabilities that were more suited to a technical user. The process for creating and working with lists was not as simple as it should be for non-technical users. SalesLogix 7.5 has greatly enhanced the list management capabilities within SalesLogix in version 7.5. 16

Solutions Groups in Tabs UI Redesign Multi-Select & Right Mouse Button menu Task Pane Interaction Summary View To improve List management capabilities in SalesLogix 7.5, the following capabilities were added: Ability to use filters to refine group query to a smaller set of data. This is done through means that are completely non-technical. Easy access to groups through tabs UI redesign for working with groups The ability to multi-select records in a group and perform an action through right-mouse-button menu has been added The ability to work with groups through task panes The ability to view groups in a summary format 17

Groups in Tabs Tabs Right mouse button UI Redesign Multi-Select & RMB Task Pane Interaction Summary View The ability to work with lists has been enhanced by improving the navigation between them. Users can now navigate through the different tabs quickly and easily. They can also access lists through the group button. Users can work with lists by performing certain actions ‘en-masse’ using the task pane or the right mouse button menu. 18

Groups in Tabs UI Redesign Scroll instead of paging Number of results displayed at top Multi-Select & RMB Task Pane Interaction Summary View Number of results indicates where user is at in the list Users can now browse through the entire group using a scroll bar – just like it works in Windows-type applications. Users can jump to different points in the list by clicking on the bar, or moving the drag control. SalesLogix 7.5 offers a richer Web client experience that matches functionality found in many Windows applications. For example, users can now browse the list of records in a group using a scroll bar. The user no longer has to guess which page the data is on and click on a link to get to that page. The paging mechanism is gone and has been replaced with a more efficient scrolling action. SalesLogix only returns the data one page at a time, but to the user, it appears that all of the data is being displayed and that they can scroll through all of it. When users click on the scroll bar, the window jumps to the set of records corresponding to that point in the scroll bar. An indicator at the top of the page displays the total number of records and the range of the records being displayed. 19

Groups in Tabs UI Redesign Multi-Select & RMB Task Pane Interaction Summary View Right-mouse button menus give quick access to important functionality like ‘save selected items as group’ Lists can easily be manipulated through the multi-select and right mouse button menu capability on the Web client. Users can control-click and shift-click to select multiple records in the list, in the same way that many Windows applications work. This makes it easy for end-users to quickly take action on a subset of the records displayed in the group. For example, users can multi-select records and then add those records to a group. Users can shift-click or control-click the records they are interested in, and then take action through the right mouse button menu. 20

Users can drag columns to different locations in the grid Columns can be sorted through menu selection or by clicking on header SalesLogix users can further manage their lists by controlling the information that is displayed and the order in which the columns are displayed. The Web client will now allow users to drag columns to different locations in the grid. Similarly, the user can change the sorting order of the rows in the grid and decide which columns should be displayed and which should be hidden. Users can hide or show columns in the grid simply by clicking on the checkbox next to the column name

Groups in Tabs UI Redesign Multi-Select & RMB Task Pane Interaction Filters Common Tasks Group List Summary View Filters are a new and exciting feature in the SalesLogix 7.5 Web client. Any end user can easily refine the query results displayed in any SalesLogix group to show exactly what they need to see. This is accomplished simply by checking the boxes next to the filter values that they would like to filter the list by. No query writing is necessary for this end user task! It is as simple user procedure to filter the group. For example, the user can filter the list to only show active, customer accounts that are in the cities of New York, Boston, London, Stockholm, Brisbane and Moscow. To accomplish this, the user would do the following: Expand the City filter and check the boxes next to New York, Boston, London, Stockholm, Brisbane and Moscow Expand the Type filter and check the box next to Customer Expand the Status filter and check the box next to Active Done! The list displayed is now filtered to show only active customer accounts in those cities. Once the user is done working with the new, filtered list, he or she can reset the list to the full group by clearing the filters. Modifying the list is as easy as clearing or setting new filters. For every column that displays in the group, a filter is displayed in the Filters task area. Users can hide unwanted filters as desired. 22

Groups in Tabs UI Redesign Multi-Select & RMB Task Pane Interaction Filters Common Tasks Group List Summary View Note that the list of accounts has been filtered to accounts managed by Brian McNulty and Cathy Hughes. 23

Groups in Tabs UI Redesign Multi-Select & RMB Task Pane Interaction Filters Common Tasks Group List Summary View The task pane can also be used in the detail views for each of the entity types in SalesLogix. The common tasks areas provides a list of quick actions that can be taken, which include: the account, contact, etc. Add a note Schedule an activity, such as a meeting, phone call or task 24

Groups in Tabs UI Redesign Multi-Select & RMB Task Pane Interaction Filters Common Tasks Group List Summary View Another task area that has been created is the Group List navigation. This task area allows users to easily jump from one detail record to another by clicking on the account name in the Group List. The list of accounts that appear in this task area is the list of accounts that display in the group (after any filters have been applied). 25

Groups in Tabs UI Redesign Multi-Select & RMB Task Pane Interaction Summary View One of the goals for the SalesLogix 7.5 release was to bring more information to the top of the application so that users can spend less time digging for the information and more time selling, marketing or supporting the products and services that they offer their customers. One way that this has been accomplished is through a Summary list view. This is an alternative view of the record in a group that breaks away from the traditional row-column grid format, and organizes the data logically as the user would expect to see it. For example, address information is formatted in the way that users are conditioned to see them – the letter address format. Another benefit the Summary view provides is summarized information. In the Accounts Summary list view, the user can quickly determine the number of contacts, opportunities, tickets and open activities for that account, because the data has been summarized and displayed in the summary view for that account. Additionally, users can hover over these summarized results to see a full list of the contacts, opportunities, etc. and then drill to a specific record as desired. 26

Mash-ups

Mashups – Situation An increasing number and variety of Application Programming Interface (API’s) continue to become available every day. These API’s provide users with access to every type of data and services, and represent a new landscape of resources from which they can cultivate the timely and meaningful information necessary to maintain a competitive edge. The information available to CRM professionals goes beyond the confines of their CRM application. In order to remain competitive, CRM users are being forced to look to many different sources of information, including those that are outside the boundaries of the CRM system. 28

Mashups – Problem Information overload
Difficult to find, filter, and compile data Multiple sources, inside and outside the company Building interfaces using current means takes time and resources that may be unavailable Sales teams, Business Analysts spend time and effort to produce limited results With so much information available from so many different sources, it is difficult for many CRM professionals to get their hands around the information and to apply it to their jobs. These users often suffer from an information overload. Too much time is spent finding, filtering and compiling the data. Users are forced to sift through many locations, including both inside and outside sources. In order to build interfaces to these other sources of data it takes time and valuable IT resources. The end result is that a lot of time and money is spent trying to gather and summarize information, with only limited success. 29

Embed information within the SalesLogix Web client
Mashups – Approach Objective: collaborative compilations of internal and external data, rich user interfaces Embed information within the SalesLogix Web client Create as quick forms User selects input control(s) at runtime View relevant data quickly The SalesLogix 7.5 Web client makes it easier to pull information together from multiple sources through mash-ups. IT can create these mash-ups and embed them directly into the SalesLogix application. Mash-ups can be created as quick forms. Users have the ability to control certain aspects of the mash-ups at runtime. The mash-ups provided in SalesLogix 7.5 allow users to view relevant data quickly. 30

= + One example of a mash-up that can be built in SalesLogix (this particular mash-up is not available out of the box), is to send SalesLogix information to Google Maps, and have Google generate a map image that combines the map data with the SalesLogix data. For example, SalesLogix could send a list of addresses for accounts in the SalesLogix database. These accounts can then be located on the map, and a marker applied to it. This type of mashup might be useful to a sales person that has completed one appointment early and wants to know if there are any other accounts close by that he or she can visit. 31

Timeline Visualization
Interactions with a customer and related activities span numerous opportunities, tickets, etc. “Health of a relationship” often measured by activity density Years of relationship activity takes up “real estate” In order to effectively work with accounts and to service customers, it is important to understand how your organization has interacted with that customer over time. These interactions include activities, tickets, opportunities and more. One possible indicator of the health of an account is the density of activities over time. The higher the density, the better the heath of that client. Displaying all interactions for customers with which you have relationships over multiple years can take up a lot of area on the computer screen. 32

Interactions and activities are recorded in various locations within SalesLogix Displayed in list view or calendar view List view: user must read Calendar view: screen breaks along calendar divisions One problem with displaying this information is that it often spans diffent views within SalesLogix. For example, some relevant information for an account is in the Tickets tab, while other information is in the Opportunities tab. The information is not easily tied together, as the user is forced to hop between two different tabs. Another problem with the way data has traditionally been displayed is that continuity is lost, For example, grids that display many rows of information do not help the user to visualize how events occurred over time. Also, time-based views like the Calendar view display information by week, day or month, forcing the user to jump from one view to another to get a picture of what has happened over time. 33

View tickets and activities Timeline visualization resolves many of the problems mentioned earlier by putting everything together in a single view that spans all time. Users can continually scroll through the timeline until they find the data they want. In addition, they can see where the data is by looking at the timeline band at the bottom of the control. SalesLogix has include two timelines for the Web client out-of-the-box. These timelines include one for Accounts and another for Tickets. Users can click on any item in the timeline to see more details. When they find the one they want, or see something interesting, they can drill directly to that record in the SalesLogix database. View opportunities and the activities associated to them Use the slider control to view data over time and to find where the data is 34

Personal Workspaces

Personal Workplaces – Situation
Static Welcome Page – no personalization All customization at design time No chart control Problem Cannot personalize workplace Changes require IT intervention No visualization of data In the SalesLogix release, Sage introduced a new concept into the Web client – the Welcome Page. The intent of this feature was to bring relevant information together into a single place that could become a spring board for accomplishing many tasks within SalesLogix. While this concept has proven to be important, there are some features that were needed in order to make this solution more useful to end users, and in order to allow it to function as a dashboard as well as a personal workspace. One of the key problems is that end users cannot personalize the personal workspace to display the information that they want. All customization is done at design time and in most cases require an IT resource to make the changes. Another problem is that there are no chart controls built into SalesLogix, making it difficult to create visualizations of the data.

Personal Workplaces – Approach
‘Smart Parts’ used to create workplace components Portal-like drag and drop features Add/remove, move/rearrange components Rename workplaces and components Workplace templates; ability to change template Spark line control can be used to graphically display high-level trends Component library for each tab Include RSS feeds and other external data Ability to create multiple tabs through customization The SalesLogix 7.5 Web client has been enhanced to make personal workplaces more useful and easier to customize and personalize. The following features have been provided: Portal-like drag-and-drop formatting of the page has been added Spark line control graphic has been added As in 7.2.2, content is created using a smart part in the application architect RSS feeds can be hooked up to smart part Additional tabs can be created through customizations so that a user can have more than one dashboard 37

Personal Workspaces Rearrange the content to the desired location through drag-and drop With SalesLogix 7.5, users now have the ability to drag components to any location on the page. The personalization persists from one session to the next, which allows the user to make the personal workspace appear exactly as he/she wants it to. A ghost image of the component is displayed as the user drags the component from one location to another. When the component is position in a place where it can be dropped, the other components in the page are re-arranged, and the component is placed where it will reside after the user ends the drag operation is complete.

Personal Workspaces Add new content, edit options and more with the tab drop-down menu. Users can also personalize their personal workspace tabs by adding content, changing the layout, changing the name and more. Change the layout of the personal workspace to one of several layouts Add new content to the page.

Personal Workspaces: New Content
Keep recent contacts fresh in your memory Keep track of critical opportunities as they close Several new components have been added to provide users with more information about the work that they do. These components include the following: Recent Notes Displays notes that have recently been created to help refresh the user’s memory about important facts for each contact, lead or account Campaign Responses Keeps marketing users up to date on the status of their campaigns Reports number of responses Reports number of responses over last 10 days Displays responses using spark line graphic control Closing Opportunities Displays the opportunities that are estimated to close Provides insight into probability of closure Gives user idea of size and importance of each opportunity Monitor campaign responses to measure campaign effectiveness

Comprehensive Web CRM

Comprehensive Web CRM – Situation, Problem
SalesLogix is a full-featured CRM solution across multiple clients Prior to version 7.5, Web client still missing some core CRM functionality. Needs to be brought to the same level as SalesLogix network client The current release of SalesLogix offers a comprehensive CRM client for Windows, but the Web client is still missing some key CRM functionality. SalesLogix 7.5 fixes the deficiencies of the Web client by adding enough CRM functionality to =make it a comprehensive CRM solution. 42

Comprehensive Web CRM – Sales Orders
Sales Orders have been added to the Web client. These transactions are created from within a tab in the Opportunity detail view. The sales orders function nearly identical to how they function in the Network/Windows client. For example, products are carried over from the opportunity to the sales order. Also, when the Sales Order is saved, the user is given the option to serialize the products. 43

Comprehensive Web CRM – Defects
Defects have been added to the SalesLogix Web client in version 7.5. Defects function nearly identical to the SalesLogix network/windows client. 44

Comprehensive Web CRM – Contracts
Contracts have been added to the SalesLogix Web client in version 7.5. Contracts function nearly identical to the SalesLogix network/windows client. 45

Comprehensive Web CRM – Returns
Returns have been added to the SalesLogix Web client in version 7.5. Returns function nearly identical to the SalesLogix network/windows client. 46

Comprehensive Web CRM – Assets
Assets have been added to the SalesLogix Web client in version 7.5. Assets function nearly identical to the SalesLogix network/windows client. 47

Lead Management

Lead Management Activities for Leads Lead De-duplication Situation
Single note field to capture interactions Cannot create activities or notes for leads Situation Leads come from many sources De-duped when converted Target lists contain Leads and Contacts Problem Must convert lead to capture interactions Some information not captured Users converting leads too soon Problem Leads database has duplicates Target list has duplicates Wasting resources and impacting image Activities for Leads Prior to version 7.5, SalesLogix users could capture notes about a lead in a single text field. It was not possible to create activities for leads. The problem that users faced was that they could not capture all of the interactions that they had with a lead unless they converted the lead to a contact. Many SalesLogix users follow a business process where they may have multiple phone calls or tasks that must be completed before they can qualify a lead and then convert it to a contact. Version 7.5 allows users to create as many activities and notes as needed during the qualification process and keeps those activities associated to the contact that is created (or merged to) when the lead is converted. Lead De-duplication Leads can come from many sources, such as trade shows, purchased lists and a corporate Web site. Prior to version 7.5, SalesLogix users could only check for duplicates when the lead was converted. This created situations where more than one person would work with the same lead, or where the same person was added to a marketing campaign more than once. The result was a waste of company time and resources, and a less favorable impression left on those leads that were contacted more then once for the same promotion. Version 7.5 corrects these issues by allow users to check for duplicates as the leads are entered or imported into SalesLogix. Users can check to see if the lead already exists as a lead or contact, or if the account already exists and the lead needs to be added to the account. During lead import, SalesLogix users can choose to automatically merge duplicate leads, reducing the time and effort required to keep the database free of duplicates. Approach Activities and Notes can now be associated to leads When converted, information carries over to contact Users can wait until appropriate time to convert Approach De-dupe leads on import, conversion and manual entry Advanced de-duplication features Option to auto-merge leads on import

Lead Management Lead Routing Import Actions Situation Situation
Leads imported or manually entered Users manually assign lead owners individually or en masse Situation Assign owner, delete en masse Can’t create notes, activities or other actions on import Problem Manual efforts waste resources Leads go cold because of time lost or errors made during routing Difficult to route if complex rules apply Problem Manual efforts waste company resources Leads are processed inefficiently Lead Routing Prior to version 7.5, lead routing was a manual process, unless third-party tools, such as Knowledge Sync were used to route the leads to the appropriate person or team. This created problems for SalesLogix users because it took longer to get the leads to the right person for qualification. In many cases, this meant that the leads were older and less-likely to still be interested in the company’s products or services. In version 7.5, leads can be automatically routed to the correct person or team for processing. The Process Orchestration feature can be used to create simple or complex lead routing rules to get leads to the right person immediately upon creation. Import Actions Prior to version 7.5, SalesLogix users could not perform any actions en-masse on the leads being imported into the system. This meant that SalesLogix users were forced to manually create activities, notes or perform other actions on the leads. Version 7.5 allows SalesLogix users to create activities, notes, responses or add leads to campaigns ‘en-masse’ on all leads that are imported into the system. This means greater efficiencies for SalesLogix users and better information being captured about leads. Approach Leveraging Process Orchestration to accomplish lead routing Sample process included – modified by customer or partner to fit their processes Approach Option to create notes, activities, responses and campaign targets on import Enter generic information; then, applied to each lead

Lead Management Responses Situation Problem Approach
Must be tied to campaigns Capture limited information Use contact status to track potential opportunity. Problem Can’t capture non-campaign responses Hard to track real interests of lead until opportunity created Responses Prior to version 7.5, SalesLogix users could only create responses for a given marketing campaign. Responses had to be associated to a marketing campaign. For SalesLogix users, this meant thay customer responses not tied to a campaign could only be entered through a note or a comment field. This information could not be easily tracked, making it difficult to find out what the leads, contacts and accounts were really interested in. Version 7.5 has resolved this issue by allowing responses to be entered without associating them to a marketing campaign. Responses also capture more information about the true interests of the lead or the contact, including what products the lead or contact were interested in. Approach Relaxing requirement to associate responses to campaigns Enhancing responses to include additional information Creating Response tabs and groups

Lead and Contact De-duplication * Ranges are configurable
Lead Management: De-duplication Lead Import SLX Insert Contact/Account Insert Lead Convert Lead Duplicate Score (0-100) Lead and Contact De-duplication Spelling Grammatical variations Phonetics Thesaurus One of the new Lead Management features in version 7.5 is the ability to de-duplicate leads as they are being entered or imported into the system. There are four points of entry that the system allows users to check for duplicates: Lead import Manual lead entry Manual contact entry Lead conversion The search mechanism that finds duplicates is based on the same technology used by the SpeedSearch feature in SalesLogix. When checking for duplicates, there are four methods that can be used: Fuzzy Fuzzy searching searches for matches with slight variations. This method is very good at finding words that have been spelled incorrectly, or that are slightly different in their spelling. A fuzziness level determines the number of differences that can exist between the search text and the text it is being compared to. For example, if the user has selected Fuzzy search and sets the level to 2, then the following names would be found if the lead being entered or imported was ‘John Adams’: John Adams Jon Adams John Adamms Jon Adam All of these names have a single difference in either the first or last name, or in both names. The higher the fuzziness level is, the more matches will be found. Phonic The Phonic search method finds words that sound the same but are spelled differently. This search only works for English language words. The following first names would be found if the lead being entered had a first name of ‘Kaitlyn’: Kaitlyn Katelyn Kaitlin Stemming This search method looks for words that are grammatically similar, but are not spelled the same. This search only works for English language words. The following account names would be a match if the account being entered was ‘Swim World’: Swimming World Swimmer’s World Thesaurus This search method searches for words that mean the same thing but that are different. This search only works for English language words. The following account names would be a match if the account being entered was ‘Strong Man Fitness’: Muscular Man Fitness Brawny Man Fitness Stout Man Fitness Scoring Regardless of the search method used, SalesLogix assigns a score between 0 and 100 to each of the matches returned by the search. Perfect matches (i.e. spelled exactly the same) are the only matches that will get a score of 100. All other matches receive a score that corresponds to how close the words match. The closer the match, the higher the score. The system allows users to define what range of scores should cause the system to consider the match as a duplicate, a possible duplicate or not a duplicate. Merging Duplicates SalesLogix users can optionally instruct the system to auto-merge leads that fall in the duplicate range as they are being imported into the system. If the duplicate range is defined as , then only exact matches will be auto-merged. The Auto-merge feature saves the user time because the duplicate does not have to be manually resolved. Imported leads falling into the ‘possible duplicate’ range are notimported into the system and are flagged so that the user can go back and manually resolve the duplicates by choosing to merge them, or by importing the lead without merging it. For leads or contacts that are manually entered, the user simply searches for the duplicates and then decides at that time whether or not it is a duplicate record, merging the record if necessary. Potential Dupe 50-89 Duplicate 90-100 Not Duplicate 0-49 Auto-merge Manual-merge Import Lead Import * Ranges are configurable Manual Create Manual Merge Conversion & Manual Entry

Activities for Leads Activities can now be associated to either a contact or a lead. Activities can have their own attachments. Activities for Leads SalesLogix 7.5 will now allow activities to be created and associated to leads. When the activity is created, it will automatically determine if the activity was created in the context of a lead or contact record, and default the lead or contact information automatically. If there is no context of a specific lead or contact, then the user can choose which type of record they want to associate to the activity. When the lead is converted, the activities remain associated to the contact to which the lead was converted. This includes open and completed activities and notes. SalesLogix users can use this feature to record all of their interactions with a lead prior to becoming a contact in the system. Activity Attachments SalesLogix users can attach files to activities in version 7.5. This allows users to associate meaningful files to the activity, such as a meeting agenda. The attachments remain with the activity even after the activity has been completed, allowing users to retain important information about the activity.

Lead Import Wizard: Step 1
Assign lead owner as Everyone, an individual person, or a team. A lead import wizard has been introduced in version 7.5 that makes it easier for SalesLogix users to import leads and provides more functionality than in previous releases. The first step of the lead import wizard allows the user to perform the following: Select the file being imported: The user simply browses to the location of the file and selects it. The “current lead list file” text box is populated with the name of the selected file. Select Default Owner: The user can choose between assigning an individual, a team or everyone as the owner of the lead. If a lead routing workflow is being used, lead routing may change the default owner to a different person or team, as specified in the Lead Routing workflow. The value set for default owner is also saved in the template definition being used for the lead import. If the template selected in Step 3 of the wizard has a different default owner than the one selected in Step 1, the default defined in the template overwrites the default selected in this step. Select Default Lead Source: The user selects a default lead source to assign to the lead. The value set for default lead source is also saved in the template definition being used for the lead import. If the template selected in Step 3 of the wizard has a different default lead source than the one selected in Step 1, the default defined in the template overwrites the default selected in this step. Add leads to group: The user determines whether he or she wants the leads to be added to an existing group or to a new group. This step is optional. The checkbox must be checked in order for the leads to be added to a group. The default name for the new group option is the system date and time, however, the user can change this to whatever name they prefer to use. Create a new group for the imported leads, or add to an existing ad-hoc group.

Step 2 in the lead import wizard allows the user to confirm that the correct delimiter is being used to parse through the lead import file. There were no changes to this functionality in version 7.5. The preview window displays how the file is parsed to extract the leads for import.

System automatically maps fields it can, then allows user to choose template or manually map fields. Step 3 of the Lead Import Wizard allows the user to determine how the data in the lead import file is brought into the lead database. The system maps the information in the file with the fields in the database using the following methods: Automatic mapping: The system automatically maps fields that have identical names Templates: The user can select a template created for a previous lead import. If the file being imported has the same fields and is structured the same as the file that was imported when the template was created, then all of the mapping information from the template will carry over to the current lead import. If there are differences between the lead import file structure and the structure that is saved in the template definition, then the fields map not be automatically mapped when the template is applied. Manual mapping: The user can manually map a field in the lead import file to the corresponding field in the lead table. Note: The template that is selected contains more than just the field mapping information. For example, it also contains the default owner and default lead source that is assigned to each of the imported leads. If these values are different than the values selected in step 1, then the system will overwrite the values assigned in step 1 with the values defined in the lead import template used in step 3. Manage templates through the Save Template dialog.

Searching for duplicates is optional. Search for duplicate leads, contacts or both Choose the fields that must match in order for a record to be flagged as a duplicate Step 4 of the Lead Import Wizard is where the user defines how the system should search for duplicates. The user can define the following: Check for Duplicates: The system can be instructed to complete skip this step and not check for duplicates. Duplicate checking is optional. If this is not check, all leads will be imported into the system, regardless of whether there are duplicates or not. The default value for this check box is that it is checked. This option is useful if you have a business process that does not require any checking for duplicates at the time of lead import. Type: Users can choose to search for duplicate records in the Leads database, Contact database or both. This is useful if you have a business process that compels you to keep one of the two types free of duplicates, but the other type should have duplicates. Match Filters: The user can choose which fields must be a match in order for a record to be flagged as a duplicate. For lead import, all match filters selected must be a match in order for the record to be considered a duplicate. Advanced Options: This button invokes a dialog that allows the user to determine the type of matching methods that the system should use, and how the scores should be assigned to potential matches. Matching methods include Fuzzy, Phonic, Stemming and Thesaurus. Auto-merge: The system can be instructed to auto-merge any records that are clearly duplicates. The records can be merged using an ‘Existing Record Wins’ method, which does not overwrite data in the existing record. Information that is in the lead, but is blank in the existing record (i.e. the lead or contact being merged to), will be copied to the existing record. The second method for merging is ‘Lead record wins’. This method directs the system to use the values in the fields for the lead record being imported, and overwrites the values in the existing record. This option is useful if you have lead data that is known to be more accurate than the data in your database. Run Test: This button allows the user to perform a test on the first 100 leads in the file to determine how effective the current duplicate searching criteria and methods will be at determining if the imported lead is a duplicate with another record in the system. If the file being imported has 10,000 records, the test is only performed on the first 100, and the statistics are then reported. If the percentage of potential matches is too high or too low then the criteria or methods can be changed to produce a better duplicate search. Run a test to determine the effectiveness of your search criteria. Optionally choose to auto-merge duplicates

Ranges are defined that determine if a lead is most likely a duplicate, possibly a duplicate, or most likely not a duplicate. The Find Duplicates Test dialog appears when the ‘Run the Test’ button is selected. Step 4 of the Lead Import Wizard offer the ability to set advanced options for duplicate searching and to run a test to determine how effective the search will be. Find Duplicates Test The Find Duplicates test searches through the first 100 records of the lead import file and projects the percentage of records in the file that will be flagged as duplicates. This test is useful when you are unsure about the settings that you have chosen for duplicate searching and want to test them out before importing the file. Advanced Options The advanced options screen allows the user to specify what searching algorithms should be used to find duplicates. The following information is repeated from an earlier slide, which describes these searching methods, and how the scores are assigned to the leads: Fuzzy Fuzzy searching searches for matches with slight variations. This method is very good at finding words that have been spelled incorrectly, or that are slightly different in their spelling. A fuzziness level determines the number of differences that can exist between the search text and the text it is being compared to. For example, if the user has selected Fuzzy search and sets the level to 2, then the following names would be found if the lead being entered or imported was ‘John Adams’: John Adams Jon Adams John Adamms Jon Adam All of these names have a single difference in either the first or last name, or in both names. The higher the fuzziness level is, the more matches will be found. Phonic The Phonic search method finds words that sound the same but are spelled differently. This search only works for English language words. The following first names would be found if the lead being entered had a first name of ‘Kaitlyn’: Kaitlyn Katelyn Kaitlin Stemming This search method looks for words that are grammatically similar, but are not spelled the same. This search only works for English language words. The following account names would be a match if the account being entered was ‘Swim World’: Swimming World Swimmer’s World Thesaurus This search method searches for words that mean the same thing but that are different. This search only works for English language words. The following account names would be a match if the account being entered was ‘Strong Man Fitness’: Muscular Man Fitness Brawny Man Fitness Stout Man Fitness Scoring Regardless of the search method used, SalesLogix assigns a score between 0 and 100 to each of the matches returned by the search. Perfect matches (i.e. spelled exactly the same) are the only matches that will get a score of 100. All other matches receive a score that corresponds to how close the words match. The closer the match, the higher the score. The system allows users to define what range of scores should cause the system to consider the match as a duplicate, a possible duplicate or not a duplicate. Merging Duplicates SalesLogix users can optionally instruct the system to auto-merge leads that fall in the duplicate range as they are being imported into the system. If the duplicate range is defined as , then only exact matches will be auto-merged. The Auto-merge feature saves the user time because the duplicate does not have to be manually resolved. Imported leads falling into the ‘possible duplicate’ range are notimported into the system and are flagged so that the user can go back and manually resolve the duplicates by choosing to merge them, or by importing the lead without merging it. For leads or contacts that are manually entered, the user simply searches for the duplicates and then decides at that time whether or not it is a duplicate record, merging the record if necessary. Different search methods can be enabled or disabled to search for duplicates.

Define the import actions that you would like performed against each imported lead. You can define values for any of the fields that can be applied to all leads, for each of the import actions Step 5 of the Lead Import Wizard allow the user to define the import actions that should be performed on the leads that are in the file. All of these actions are performed, even if the lead is auto-merged with a contact. This means that if you want a response to be created for the lead, indicating that the lead is interested in a certain product, the response will be created for the contact if the lead is auto-merged with a contact. This allows the user to track the responses that must be acted upon as potential opportunities, regardless of whether the import record ends up being a lead or a contact. These actions include the following types: Note: Create a note that will appear in the History/Notes tab of the lead. Response: Create a response and record the interests of the lead or contact (if merged with a duplicate). You may optionally associate the response to a marketing campaign. If the response is associated to a campaign, the lead or contact (if merged) will be added to the marketing campaign as a target. Campaign Target: Add a lead or contact to a marketing campaign as a target, without creating a response. Phone Call, Meeting, To-do: Create/Schedule any of these activity types for the lead or contact (if merged).

Step 6 offers the user an opportunity to review the selections made and to go back and make changes, if necessary, before kicking off the lead import process. Review your selections before kicking off the lead import process. Make any necessary changes.

Step 7 of the Lead Import Wizard acknowledges that the lead import process has started and reports the progress of the import as it occurs. The number of records import, that failed to import, that have been flagged as duplicates or that were flagged as duplicates and merged with an existing record are reported. If it does not appear that the import is going as planned, the process can be aborted. If the user wants to perform other work while the lead import is being executed, he or she can leave the Step 7 page and the import process will run in the background. At any time the user can navigate to the Lead History page to view and monitor the progress of the lead import. Monitor progress of the lead import. Leaving this page does not stop process from running.

Lead Import History: List View
Lead import processes can be tracked and monitored through the Lead History page. The lead import logs can be used for auditing purposes to determine why certain records made it into the system and other records did not. This view provides the following information: Import number (unique ID assigned by the system) Description: the filename Create Date: The date the lead import file was imported Status: The status of the lead import process Imported Count: How many records were imported (or have been imported so far if the process is still running) Duplicate Count: How many records were or have been flagged as duplicates. Merge Count: How many records were or have been merged with an existing contact or lead. Error Count: How many errors were or have been generated during the import process. View the history of all of your lead imports. List view gives at-a-glance statistics for each import.

Lead Import History: Detail View
The Lead Import History Detail screen provides detailed information about the lead import process, including: Lead Import Number Description: The file name. Total Records: The total number of records in the file Total records processed: Some records in the file may not have been processed if there was an error, such as data corruption. Total records imported: Duplicate records that are not auto-merged, are not imported into the system and are not reported in this number. Total Errors: The number of records that could not be processed due to some error with the data. Total Warnings: Number of warning generated. Does not necessarily impact whether a record is imported or processed. Total Duplicates: Number of records that were flagged as duplicates and not imported Total Auto-merged: Number of records that were flagged as duplicates and auto-merged when they were imported Duplicates Tab: Duplicate records are listed in the duplicate tab. The user manually merges these records by clicking on the resolve link. A dialog appears that shows the matches that were found and allows the user to choose which match to merge the record with, or to import the record without merging (if none of the matches found are truly duplicates). The merge screen allows the user to specify exactly which fields should be kept between the import record and the existing record (see section describing lead conversion for example). History Tab: Contains error messages and warnings. Reports the auto-merges that occurred during the import. Resolve duplicates (one-by- one) that were found during import, and not auto-merged.

Lead Conversion Specify duplicate search methods to use. The match filters tab is similar to the match filters form for lead import. When converting a lead, the same process used in lead import for searching for duplicates and merging leads is used. Merging leads allows the user to choose the exact fields that are kept for the existing record (i.e. keep the lead information or keep the existing record information). Other functionality offered in this feature includes: The ability to create opportunity when the lead is converted or merged to a contact User selects record to merge, and then merges record

Manual Merge Choosing these radio buttons tells the system to use the data from that record by default. User can manually select which fields have the correct data that will be used during the merge The manual merge form displays all of the relevant records for the lead and contact being merged, and allows the user to select which data to keep. The fields in this form can be customized to display custom data that has been added to SalesLogix. Select Default Record: The radio buttons at the top allow the user to specify a master record that has the majority of the data that should be kept. Choose Specific Fields: The system allow users to choose specific fields that they want to merge. This is useful when one of the records being imported has some information that should be preserved, even thought the other record has most of the information.

Insert Contact/Account & Lead Dupe Checking
Search for duplicate leads, contacts and/or accounts Match with any or all of filters in order for record to match SalesLogix version 7.5 allows users to search for duplicate accounts, contacts or leads when manually creating leads or contacts in the system. The searching allows the user to find matches based on a logical ‘OR’ or based on a logical ‘AND’ condition of all of the match filters select. In other words, the user can specify if all of the fields have to match, or if any of the fields have to match in order for the system to count the record as a match. If a duplicate record does exist, the user has the option to open the record that they believe is the matching record. The user can then perform any changes needed to that record, such as adding a response, an activity or a note. Open the record that looks like a duplicate and edit that record instead of creating a new record.

Lead Management: Responses and Interests
= Potential Contact = Potential Opportunity Lead Responses can be independent of campaigns Associated directly to contacts, leads and accounts Can be center of work Capture customer interests and other new information Responses Campaigns Contacts Leads Accounts Leads can be viewed in two ways: Potential Opportunity: May already be a person in your CRM system, but lead represents a new opportunity for a sale Potential Contact: May not be in your CRM system. Has potential of being a customer with long-term relationship and many sales over time. Prior to SalesLogix 7.5, most user would qualify and convert leads to contacts as soon as possible, giving the contact a status such as ‘Prospect.’ When the lead was converted opportunities were created in some cases, but in other cases the business processes followed did not create opportunities until a later time. If an opportunity is not created at the time the lead is converted, it can be difficult to track what the original interest was that generated the lead in the first place. The changes to responses in version 7.5 help with this problem. Responses have been enhanced in version 7.5 to allow them to be entered without an association to a marketing campaign. This makes it easier to create responses that register the interest of the person. Additional information has been captured on the response to record the interest that generated the lead in the first place. 67

Lead Management: Lead Processing
Acquisition Qualification Conversion Opportunity Lead-centered process: Purchase lists Create responses Manual entry De-dupe against leads only Process using lead lists Simple qualification steps Gather minimal information Merge with duplicate contacts Create contact with ‘Prospect’ status Add contact to account Perform additional assessment Create opportunity Response-centered process: Purchase lists Create responses Manual entry De-dupe against leads and contacts Process using response lists Advanced qualification Gather extensive information Confirm no duplicate contacts exist Create new contact Add contact to account Create opportunity There are now multiple options for SalesLogix users to process leads, so that they can choose the option that best matches their business process. These processes are as follows: Lead-centered Process A lead-centered process allows users to work with a list of leads to qualify and convert leads without having duplicate records in the system. Using this process, the SalesLogix user would focus on keeping leads free of duplicates, but wait to check for duplicate contacts until the lead is converted. Any notes, responses and activities created for the lead are carried over to the contact. Once converted, the contact may be put into Prospect status if it is a new contact, or if the contact is an existing customer the user may choose to create an opportunity. In either case, the user can continue to track the potential sale, and keep track of the original interest that generated the lead. Response-centered Process For SalesLogix users that have business processes that want to keep their system free of duplicates for both Leads and Contacts, they can choose to work off of responses instead of leads. Every lead that is created can have a response. If the lead is merged at any time with a duplicate contact, the response (with the original information about the interest) is preserved. The potential sale can be tracked through the responses, and the leads can remain in the system for as little or as long as needed before becoming contacts. Activity-centered Process If the SalesLogix prefers to track potential sales through activities, and drives all work off of an activity list, they can use responses to keep track of the original interest of the lead, and focus on converting the lead to a contact. The center-of-work would be the activity list. Activity-centered process: Purchase lists Campaign responses Manual entry De-dupe against leads and contacts Process using activity lists Advanced qualification Gather extensive information Confirm no duplicate contacts exist Create new contact Add contact to account Create opportunity 68

Responses Keep track of the interest that the lead or contact has, and the interest level. Responses are no longer required to be associated to a marketing campaign. This allows responses to be used more freely to track the interests of leads or contacts. Responses have been enhanced to include the following information: Interest: This is a pick-list that can be defined by the SalesLogix customer for all the users to benefit from. The intent of this field is to capture the type of interest that the customer has. These could be literature requests, product inquiries or some other interest. Interest Level: Tracks the level of interest that the lead or contact has shown. Products: Tracks specific products or services that the lead or contact may be interested in purchasing. Associate products that the lead or contact is interested in

Web Services

Internal consumption by our web client External data access
Web Services Internal consumption by our web client Improved performance and scalability External data access Integration with other applications, front office/back office Product extensions Customer/partner customizations and verticals

Addressable resources (URLs) RESTful Web Services
URL parameters for queries (scope): Representation is not necessarily XML (flexibility) RESTful Web Services Simple interface (HTTP) for domain specific data Standard verbs: GET, POST, PUT, DELETE HTTP Status Codes for success/failure: 200 OK, 404 Not Found Leverages existing Web Architecture Programmable web like browse-able web

Web Services: Example URLs Compared to SOAP
REST SOAP GET /Accounts POST /GetEntityList GET /Accounts(ID001)/Contacts POST /GetEntityList GET /Accounts?orderby=Name& where=Type eq ‘Partner’ POST /GetEntityList POST /DeleteEntity DELETE /Accounts(ID001)

Web Services: SData protocol
SData is a simple standard for reading and writing data between Sage applications Built on leading industry standards HTTP, XML, ATOM/RSS, REST Designed to be used in widely varying situations Not tied to any particular platform Will be used to establish contracts for integration Common RESTful interfaces can be applied to different application “trunks”

Web Services: REST Framework
Provides both consumer and producer support for REST and SData web services Consumer: Process incoming request Route to appropriate adapter Provide results back to consumer Producer: Provide simple, common interface for processing web service requests Provide formatting support (Atom, RSS, JSON) for web service results

Web Services: Application of REST in Sahara
RESTful services in Sahara Process orchestration Lookups Summary View Legacy Groups SData Full CRUD support for all SLX entities HTTP Digest (extended from SData Framework) – SLX authentication Consumer Provider

Process Orchestration

New Process Orchestration runtime host Entity Eventing Service “Special” type of process introduced Web Service integration

“Goal-driven” process Combination of state machine and sequential workflows. A series of stages that can contain multiple steps. Stages can also be grouped for scoping Steps can be optional or required. Completion of all required steps within a stage completes the stage. Steps can be completed outside of the currently “active” stage.

Simple Sequential Process
Process Orchestration Simple Sequential Process Based on sequential workflow Some event (like creation of an entity) will kick off one or more actions. Example: On creation of a Lead entity, execute the “Lead Ownership” policy Policy details: IF Lead.State == “AZ” THEN Lead.Owner = “Bob” ELSE Lead.Owner = “Bill”

Process Orch: Types of activities (steps) supported
Schedule Activity: ToDos, Phone Calls, Meetings, etc. Assign Ownership (SecCodeID) Set User (UserID) Launch child process Others TBD…

Process Orchestration: Entity Eventing Service
New data change events implemented at OleDB Provider level Managed code entity eventing service integrates with data change events Process Orchestration host consumes entity eventing service Can be configured to kick off workflows based on data changes Service could be consumed by other applications…

Gobi 7.2 Web Client Architecture
SalesLogix Presentation Tier Administrative UI Configuration Application UI Rich DHTML/Ajax Client Page Layout Templates Custom views/navigation Web Browser ( IE, Firefox, Etc.) Corporate Firewall SalesLogix Web Application Tier Application Architect Application Portal Deployment Generated Aspx Pages and Smart Parts Business Rule Handler Data Persistence and Session Management One-click Portal Deploy Supports Server Farms Customization SalesLogix OleDB Provider Entity Definition Business Rule Creation Form Designer App Portal Builder ASP.NET / AJAX IIS SalesLogix Data Tier Remote Clients / Remote Offices Transactional Data SalesLogix Server License Manager Logging Server Slx Sync Server DB Server (MS SQLServer, Oracle)

Process Orchestration: Architecture
SalesLogix Presentation Tier Corporate Firewall Orchestration Host SalesLogix Web Application Tier Application Architect / Visual Studio Process Orchestration Web Service Process Orchestration Service Process Orchestration Application Enhancements Process Design Entity Eventing Service Process Deploy SalesLogix Data Tier Remote Clients / Remote Offices Transactional Data SalesLogix Server Persistence & Tracking License Manager Logging Server Slx Sync Server DB Server (MS SQLServer, Oracle)

“Gobi” Application Architect Integration The Process Manager Host will be deployed just like an application portal. In future release - Process definitions, Actions and Policies are implemented as Project and Bundle items, which allows processes to participate in the Project Explorer and with Bundling. SalesLogix Presentation Tier Corporate Firewall Orchestration Host SalesLogix Web Application Tier Application Architect / Visual Studio Process Orchestration Web Service Process Orchestration Service Process Orchestration Application Enhancements Process Design Entity Eventing Service Process Deploy SalesLogix Data Tier Remote Clients / Remote Offices Transactional Data SalesLogix Server Persistence & Tracking License Manager Logging Server Slx Sync Server DB Server (MS SQLServer, Oracle)

RESTful Web Service Interfaces Process Query Service – View into process What is the current stage of a process? When did stage transitions occur? What steps executed and when? Did a specific process complete? What exceptions were thrown? Process Manager Service – Control processes Get list of processes Start/Stop a process Raise an event Pass in user interaction Administrative override of processes For example – Move a process to the next stage SalesLogix Presentation Tier Corporate Firewall Orchestration Host SalesLogix Web Application Tier Application Architect Entity Model Process Orchestration Web Service Portal Model Process Orchestration Service Process Orchestration Application Enhancements BundleModel Entity Eventing Service Process Model SalesLogix Data Tier Remote Clients / Remote Offices Transactional Data SalesLogix Server Persistence & Tracking License Manager Logging Server Slx Sync Server DB Server (MS SQLServer, Oracle)

Persistence Service Service of workflow runtime that is responsible for persisting long-running processes to storage, as well as pulling processes out of storage into memory. Tracking Service Subscribe to events in the workflow runtime and persist information about the events to storage. SalesLogix Presentation Tier Corporate Firewall Orchestration Host SalesLogix Web Application Tier Application Architect / Visual Studio Process Orchestration Web Service Process Orchestration Service Process Orchestration Application Enhancements Process Design Entity Eventing Service Process Deploy SalesLogix Data Tier Remote Clients / Remote Offices Transactional Data SalesLogix Server Persistence & Tracking License Manager Logging Server Slx Sync Server DB Server (MS SQLServer, Oracle)

Application Architect Improvements

Application Architect: Workspace Management
Workspace Manager App Architect remembers last project for logged in DB Workspace list shows associated DB name Only one VFS workspace shown at a time (for current DB) Project Backups Save a project to ZIP file, including support files Restore from project backup Shipping Slx release project backups with product

Application Architect: Wizard Improvements
Access wizards from main toolbar New wizard pages added to establish context New Entity Wizard improvements Fewer clicks for new properties Assign large/small icon to entity Set display value

Application Architect: Quick Forms
Quick Form design improvements New Data Sources toolbar allows drag/dropping properties onto forms Adding Image control New and improved Code Snippet Action New code-generated form interface parameter provides IntelliSense for properties, current entity, and current workitem User VB.NET or C# No need to merge on upgrades!

Application Architect: Portal Management
New template mapping tool Much easier to change page templates Workspaces don’t need to have same name

Application Architect: Deployment Explorer
Central deployment management Manage multiple deployment targets and portals in one place Save multiple configurations (Test, Production, Local) Create deployment snapshots Save a snapshot of one or more portals Deploy from saved snapshot Don’t have to worry about changes made to project from one deployment to another when using snapshots New deployment type…

Application Architect: Deployment Explorer
Deploy to remote users (Disconnected Web Client)! Select a list of remote users to deploy web client to New Personal Server based on Cassini hosts multiple web sites on remote computer No IIS required Personal Server part of remote client install along with Sync Client Portals deployed through existing Sync architecture and automatically registered with Personal Server on local machine

Application Architect: Other Improvements
Bundle Management Create bundle from project differences Includes ability to select project backups Image Management Global image resource manager being made available from Project Explorer Ability to bundle images on their own Future “Global string resource manager” will follow same pattern Code Snippets CTRL-F: Search and Replace!

Network/Windows Client New Features

Enhancements in v7.5 Network/Windows Client
Activities for Leads Activity Attachments Activity main view more open to customization Ability to enable/disable (i.e. hide/show) tabs Ability to change values in timeframe filter Sparklines (available as additional control) Process Orchestration Timeline Visualization (through customization) Intellisync Visual Analyzer (Compatible release will follow v7.5) Exchangelink (Compatible release will follow v7.5) A number of the new features in the Web client are also available for use in the SalesLogix Network/Windows client. There are also some new features that only apply to the Network/Windows client. The features in the Web client that also are available in the Network/Windows client include the following: Activities for leads Activity attachments Spark lines Process orchestration Lead routing Timeline visualization (through customization) Third-party solutions, including Intellisync, Visual Analyzer and Exchangelink The new features that are only applicable to the Network/Windows client include the following: The activity main view is more open to customizations Tabs in the Activity main view can be enabled/disabled The time frame filter on the Activity main view can also be customized

SalesLogix v7.5 Sneak-Peek

Similar presentations

Presentation on theme: "SalesLogix v7.5 Sneak-Peek"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

SalesLogix v7.5 Sneak-Peek

Similar presentations

Presentation on theme: "SalesLogix v7.5 Sneak-Peek"— Presentation transcript:

Similar presentations

About project

Feedback