ProspectSoft CRM Version Release Notes

Transcription

1 Software Update ProspectSoft CRM Version Release Notes Target Readership This document is intended for release by anyone currently running a ProspectSoft CRM release earlier than If you are running a ProspectSoft CRM version earlier than EBF 2 then you should check the release notes documentation for earlier versions to see what is changed in these releases. Purpose These Release Notes describe all enhancements, fixes and other changes included in this release and any patches since the last full version release. This document does not deal with the details of how to carry out an upgrade, except where there are specific issues related to upgrading to this version. For general information on upgrading, please refer to the ProspectSoft CRM Installation Manuals. Important Please review the Important Notes section on the next page before installing this version of ProspectSoft CRM. This is especially important if you are integrating ProspectSoft CRM to any accounts package, are not using Microsoft Windows XP SP2 or higher, are not using Microsoft Office 2003 or higher, use Opera 16, or are running an EBF numbered 1xx or 2xx. Page 1 of 28

2 Important Notes During the upgrade process the system will try and insert new problem type and analysis codes of '_UNKN_' at all levels. This code is now reserved by the system for the support of PAM with ProspectSoft Web Solutions and if encountered before upgrading to , the upgrade process will not be allowed to start. In the unlikely event of this happening these pre-existing codes will need to be changed with so that they do not conflict with the reserved code. Please contact your support provider if you need assistance with this. Remote users that are upgrading from version 5.x will need to go to the settings screen and configure their profile for offline use before they can log into their offline database. For more information on upgrading from version 5.x to version 6 please review the release notes. All users who wish to take advantage of ProspectSoft CRM s off line pricing when linked to IRIS Exchequer must ensure that the Exchequer Toolkit is upgraded to Version or later. Installing on a system that is not currently running version 6.00.xxx is likely to require the computer to be restarted. This applies to servers as well as client machines. Users that wish to integrate with the Sage (Line) 50 accounting system should upgrade to the latest version of the ProspectSoft CRM Sage Integration when installing this version (currently version 5.27 at the time of writing which together with Prospectsoft CRM supports Sage 50 Professional 2010). ProspectSoft CRM 6 requires Windows XP Service Pack 2 or higher when using a Windows client operating system or Windows Server 2003 and above when using a Windows Server operating system. Microsoft Office 2003 and higher are now the only supported versions of the Microsoft Office suite. Office 2000 and Office XP are no longer supported. ProspectSoft CRM 6 should work with most XML API applications that were written for version 5, however some compatibility issues may exist in some applications and testing should be done to ensure that everything functions as expected. For more information on the changes to the XML API see later in this document. This version of ProspectSoft CRM may not include custom EBFs (numbered 1xx or 2xx) from previous versions. Please contact your ProspectSoft CRM support provider if you are running one of these EBFs to check if this version is compatible with your system. If using the installer to upgrade version or to this version then the install will complete successfully, however the first time you run ProspectSoft CRM the "configuring ProspectSoft CRM 6" message will be displayed. This process should be allowed to complete, at which point you will need to restart your computer. ProspectSoft CRM should then run as normal. Page 2 of 28

3 Important Notes (continued) Opera 16 integration is no longer supported. This and future versions of ProspectSoft CRM will only support integration with Opera II accounting systems (limited support is still available for Opera II SQL). The licensing options for small business CRM systems included with the demonstration profile are based on the old small business systems and do not represent the new rules of the newly rereleased small business CRM packages from ProspectSoft. These will be updated in a future version. If installing ProspectSoft CRM 6 alongside ProspectSoft CRM 5 and using the demonstration profile, please ensure that you use the version 6 Reset Database wizard to reset the database rather than the version 5 wizard. The version 6 wizard is called "Reset Demo Database" as opposed to "Reset Database" and is in the "ProspectSoft CRM 6 Tools" folder of the Start menu. There is now a single install for the live and demonstration versions of ProspectSoft CRM. The live and demonstration databases can be accessed using the profile drop down list on the login screen. For more information please see later in this release notes document. Although more than one copy of the ProspectSoft CRM application can be opened at any one time this is not recommended even when connecting to different profiles as it can cause issues with XML API applications and utilities such as "Save to CRM". In some rare cases a message may be displayed on upgrading that states that division records have been found with null operating companies. If this occurs please contact your ProspectSoft CRM support provider who will be able to provide you with a report that you can use to analyse which division records are the cause of the problem. Page 3 of 28

4 Contents Contents Enhancements... 7 Added facility in database for postcode based location searching 7 Support for clickable URLs in user defined reports 7 Option to remove Select Product Category popup on new lead 8 New Lead Type functionality 8 New obsolete field on User Defined Tabs admin table 8 New Dashboard button on toolbar 8 Enhanced database performance 9 Added functionality to support PAM in ProspectSoft Web Solutions 9 New options for displaying items in Web Catalogue 9 Import of warehouse codes for IRIS Exchequer orders 10 Mobile user databases no longer close after last connection 10 More efficient licence check process 10 New Customers Near Postcode Division level advanced search 10 Enhanced performance on user defined console tabs 11 Divisions with no contacts report now also in Maintenance folder 11 New database fields to support Up-sell version Searching for status description on Lead Advanced Search 11 New Divisions with Inactive or Obsolete Account Managers report 11 Job Costing Multiple Operating Company Support Demonstration Data Enhancements Updates to allow use with ProspectSoft Web Solutions web sites 13 New Divisions nearby xtra tab XML API Enhancements Added ability to set leadtypecd through lead object Updates Formatting on Web Product Variations tab 15 Non-replicating tables message for proxy tables 15 Erroneous Current licence invalid messages 15 Error 76 when using Automatically Select Running Profile on XML API Login Screen 16 Page 4 of 28

5 Web Allow Split on Web Catalogue Product Item tab renamed 16 Product groups containing single quotes causes e-commerce searching error 17 Price list code on Opera II special pricing import 17 e-login tab default values 17 Web description and code fields are not searchable 18 Inconsistent column names on Product Item list screens 18 Document relationships take a long time to create 18 IRIS Exchequer version checking when opening transaction document 19 PDF Reader for drill down on Opera II SL transactions 19 At a glance tabs do not fit on one page 19 Lead Status Movement report does not have version 6 header 20 Campaign and Campaign Activity Summary reports do not react to enabled modules 20 Recalls by User report does not have version 6 header 20 Cannot drill down from Product Category admin table XML API Updates Can't cancel Exchent new SL window 22 More properties on Exchequer Create SL 22 Can't use WindowAction to cancel new SL EBF 2 Enhancements Less intrusive Outlook Contact Sync EBF 2 Updates Opera II VAT effective dates 24 Opera II Payment import incorrect EBF 1 Enhancements 'PayDue' field in sales history 25 "Ancestor / Summary" tab speed improvements 25 Query efficiency improvements EBF 1 Updates Non-Stocked items not allocated in Opera II 26 Opera "Product Item Supplier" fields 26 Product selection for lead not restricted by operating company 26 Profile data not created correctly on first start-up 27 Array boundary exceeded when drilling down 27 Page 5 of 28

6 Error when scrolling through Product Items using "Video" buttons 27 Spelling and typographical errors 28 Page 6 of 28

7 Enhancements Added facility in database for postcode based location searching Ref: New functionality has been added to the database to allow reports written in the report writer software to calculate the distance between the outcode section of two postcodes (i.e. for the postcode HP14 3RQ the outcode is HP14 ). This can be particularly useful for finding the rough distances between two customers for example. Note: This functionality is best seen in use with the new reports for live and demonstration databases as described later in this document. Support for clickable URLs in user defined reports Updated in EBF 202 Ref: , User defined reports that are imported into ProspectSoft CRM can now be set to include clickable hyperlinks. To accomplish this using Infomaker simply set the 'Tag' property on a column to one of the following: url=auto o Where the column itself contains a URL that should be opened url= o Where the column contains text but the URL should be opened when the column is clicked on. url={column_name} o Where the column name indicated between the brackets contains the URL that should be opened. This is most useful for adding a friendly clickable URL to dynamic URLs that change row by row as this can be set to point to a column that has been made invisible. When using this tag it is recommended that the column's text should be set to underlined blue and it's pointer set to Hyperlink to maximise the user experience. Note: You can specify other tags as well as the URL tag by separating them with a semi-colon. Page 7 of 28

8 Option to remove Select Product Category popup on new lead Ref: A new system option ( Fixed product category for leads ) has been added to allow the specification of a default product category for use when creating leads. If this option is set with a valid product category code then the select product category window will not be displayed when creating a lead and the value from this option will always be used. Note: This change also impacts on the new Lead Type functionality enhancement described below. New Lead Type functionality Ref: A new admin table and drop down list for specifying a Lead Type against a Lead record has now been added to ProspectSoft CRM. If the above mentioned Fixed product category for leads system option is set then the Lead detail window will display a new optional Lead Type drop down where the user can select a type from a list configured in the new Lead Types Admin Table. New obsolete field on User Defined Tabs admin table Ref: The User Defined Tabs admin table has been updated with a new Obsolete field that allows users to obsolete user defined tabs when they are no longer needed. New Dashboard button on toolbar Ref: , A new Dashboard button has been added to the ProspectSoft CRM toolbar and View menu to make it easy to access your dashboard reports even when you have a large number of windows open. It is now also possible to switch back to the Dashboard by using the keyboard shortcut of CTRL + SHIFT + D. Page 8 of 28

9 Enhanced database performance Ref: A number of new indexes have been created on the database to improve performance for both ProspectSoft CRM systems and ProspectSoft Web Solutions e-commerce websites. Added functionality to support PAM in ProspectSoft Web Solutions Updated in Ref: , , Functionality has been added to this version of ProspectSoft CRM to support the use of the Problem Analysis Matrix on a ProspectSoft Web Solutions web site. From a ProspectSoft CRM point of view the change consists of a new Unknown type being added to all problem type and analysis levels. This new type is marked as obsolete and is not available as an option in the CRM but allows users of a ProspectSoft Web Solutions web site to be able to log problems without specifying all levels of the PAM (so long as the web solutions plug-in has been configured to allow this). If an Unknown type or analysis is selected by a user of the ProspectSoft Web Solutions website then this will be highlighted in red in the CRM interface to notify the user so that they can ensure that the PAM is fully specified as soon as they have the information available. Important Notes: A problem will be reported at the start of the upgrade process if the system encounters a problem type or analysis code of '_UNKN_'. This code is now reserved by the system for the support of PAM with ProspectSoft Web Solutions and if encountered, the upgrade process will not be allowed to start. In the unlikely event of this happening these pre-existing codes will need to be changed with so that they do not conflict with the reserved code. It is possible to revert your ProspectSoft CRM installation to the previous version and continue working while this change is made. Note: This enhancement is only relevant to users with a ProspectSoft Web Solutions website where the PAM is required for problem tracking and/or searching. New options for displaying items in Web Catalogue Updated in EBF 116 Ref: 64271, The option to allow products to be shown or hidden on a ProspectSoft Web Solutions e-commerce site has been extended to allow items to be set to appear with a hidden add to basket button, a hidden price and add to basket button, or hidden entirely. During this change the alignment of items in the Web Catalogue tab has been changed to make things more clear. Note: This enhancement is only relevant to users with a ProspectSoft Web Solutions e-commerce web site. Page 9 of 28

10 Import of warehouse codes for IRIS Exchequer orders Updated in EBF 108 Ref: A new field which defines the warehouse code that each sales or purchase order is going from/coming to has now been added to the ProspectSoft CRM database and now included in the sales history and purchase history imports when using ProspectSoft CRM connected to the IRIS Exchequer accounting system. Mobile user databases no longer close after last connection Ref: The settings for mobile user databases have been changed so that they do not close when the last connection to the database disconnects. Not closing the database ensures that the database cache is still available between ProspectSoft CRM sessions and improves performance. This change is made to both new and existing Offline ODBC DSNs when using ProspectSoft CRM and above. Note: The database can still be shut down by right clicking on the database icon in the system tray and selecting Exit, although please note that you should ensure that ProspectSoft CRM, Replication, and any other applications that are using the database are shut down first. More efficient licence check process Ref: The check performed by ProspectSoft CRM to determine how many users are currently using the database has been changed to be more efficient. This improves both the speed of logging into the application and the speed of loading the View / Disconnect Connected Users screen. New Customers Near Postcode Division level advanced search Ref: A new advanced search at Division level has been created named Customers Near Postcode. This advanced search allows for divisions to be searched by a combination of account manager and distance from a given postcode. This new search makes use of the new 'outcode' based location functionality as described earlier in this document. Page 10 of 28

11 Enhanced performance on user defined console tabs Ref: In order to enhance general system performance ProspectSoft CRM now only retrieves user defined data on console tabs when they are selected rather than during a record load. Divisions with no contacts report now also in Maintenance folder Ref: The Divisions with no contacts report is now included in the Maintenance folder for more consistent access with the other maintenance reports. It still also exists in the Contact Reports folder to be consistent with the expected location for users that already use this report. New database fields to support Up-sell version 2.5 Ref: Two new fields have been added to the Up-sell proditemlinks table to support service items and invisible items. If you are currently using the Up-sell XML API application and are interested in upgrading or would like to learn more about these features then please contact your support provider for more information. Searching for status description on Lead Advanced Search Ref: , The Lead Advanced Search has been updated to allow searching on the Lead status description field as well as the status code. Searching on the status detail description is now also supported. New Divisions with Inactive or Obsolete Account Managers report Ref: A new Divisions with Inactive or Obsolete Account Managers report has been added to the system to allow an easy lookup on all division records that have an account manager set that is either inactive (was previously an account manager but is no longer) or marked as obsolete. Page 11 of 28

12 Job Costing Multiple Operating Company Support Updated in EBF 102 Ref: The tables that are used to store IRIS Exchequer Job Costing fields within the database have been updated to include an "operating company" field and as such now support multiple operating company environments. Page 12 of 28

13 Demonstration Data Enhancements Updates to allow use with ProspectSoft Web Solutions web sites Ref: The demonstration database has been updated in this version to ensure that it can be used out of the box with a ProspectSoft Web Solutions web site. The changes made include: Added Product Item Grouping information to products for e-commerce web sites Granted web login details to the following users with the password of password : o Michelle Durie (michelle_durie@hotmail.com) o Ken Stokes (kens@altman.co.uk) Added a new e-commerce delivery charges report (br_rber_cmsdeliv_demo) with improved functionality for different delivery types and removed the old report (cms_deliverycharge_demo2). Set the unidentified user basket contact e-commerce option to the contact John Young (ID: 2545). This ensures that all pricing appears correctly on a ProspectSoft Web Solutions e-commerce database for a user that is not logged in. Added generic e-commerce product descriptions for all products to ensure that they show up correctly on a ProspectSoft Web Solutions e-commerce website. New Divisions nearby xtra tab Ref: A new xtra tab named Divisions nearby has been introduced for the demonstration database at division level to show all divisions that are physically near to the current division. This xtra tab makes use of the 'outcode' location based searching described earlier in this document. Page 13 of 28

14 XML API Enhancements Added ability to set leadtypecd through lead object Ref: It is now possible to use the ProspectSoft CRM XML API Lead object to set the new leadtypecd field introduced in version For more details on the purpose of the leadtypecd field see the enhancement description for the new Lead Type functionality which is located earlier in this document. Page 14 of 28

15 Updates Formatting on Web Product Variations tab Reported in Ref: Symptoms: The Web Product Variations tab has an incorrect background colour. It should be set to white to match the standard ProspectSoft theme colour but is instead set to a grey colour. Solution: This has now been updated with the correct formatting. Non-replicating tables message for proxy tables Reported in Ref: Symptoms: When logging into ProspectSoft CRM version to a database that contains proxy tables a message appears stating that these tables appear to be required to replicate but are not configured correctly. This message should not appear. Solution: This message will now no longer appear for proxy tables as they are not designed to replicate. Erroneous Current licence invalid messages Reported in EBF 8 Ref: , , Symptoms: Current licence invalid messages are being displayed on a small number of ProspectSoft CRM systems where the licence is still valid. Logging out and back-in again allows the user to access the system and continue working with no change in licence key. Further investigation has shown that this seems to be a database connection problem. Solution: Although on a number of cases it is possible that a network issue prevented connection to the database it was also found that in some limited cases the check of the license key might conflict with other database operations that were occurring at the same time. The licence key check has now been changed so that it only fires while no other database connection activity is occurring. Page 15 of 28

16 Error 76 when using Automatically Select Running Profile on XML API Login Screen Reported in Ref: Symptoms: An Error 76 File Not Found error will be displayed when opening an XML API application in the following circumstances 1. The user has previously selected the Automatically Log In and Select the Running Profile option in the login screen for that application. 2. The application is running on a server installation of ProspectSoft CRM that has no Demonstration profile. 3. The user is opening the XML API application while ProspectSoft CRM is running. Solution: This has now been addressed and all XML API login screen options should work as expected for all installation types of ProspectSoft CRM. Web Allow Split on Web Catalogue Product Item tab renamed Reported in Ref: Symptoms: The Web Allow Split check box on the Web Catalogue tab for Product Items is causing some confusion due to the fact that items that are not set up to split in the accounting system cannot be set up to split online. Solution: The confusion with this tab is due to the fact that it is not possible to set products that are not set to allow splitting in the accounting system to split on a ProspectSoft Web Solutions e-commerce site. To do so would cause problems when the order was confirmed into the accounting system. This option was designed to prevent splitting of items when purchased online that could be split ordinarily (for example in the case where you would like to be able to split a pack under exceptionally special circumstances but do not want many orders coming in with this request). As such the check box has now been changed to a description of Prevent Web Split. The default is not to prevent splitting online for those products that can be split in the accounting system. Note: The database still stores the same field values as previously and as such no user defined reports that use this field will need to be changed. This change will only be noticed by users running a ProspectSoft Web Solutions e-commerce web site. Page 16 of 28

17 Product groups containing single quotes causes e-commerce searching error Reported in EBF 109 Updated in EBF 110 Ref: Symptoms: If a product group contains a single quote (apostrophe) then any searching performed via a ProspectSoft Web Solutions e-commerce website that includes that group fails. Solution: Product groups that contain single quotes are now dealt with correctly when performing searching on a ProspectSoft Web Solutions e-commerce website. Note: This update will only be noticed by users running a ProspectSoft Web Solutions e-commerce website. Price list code on Opera II special pricing import Reported in Updated in EBF 111 Ref: Symptoms: The import of the special pricing data for the Opera II accounts system is limiting the price list code field ( o_cdetl.cd_code ) to 4 characters instead of the maximum possible value of 8 characters. Solution: The import has now been amended to ensure that the correct number of characters are imported. e-login tab default values Reported in Updated in EBF 111 Ref: Symptoms: If a user has not selected the On Hold or Force Password Change at Next Login check boxes from the e-login tab at contact level at least once then no value will be stored in the database for these values. This can result in people not being able to log into the website without on-hold being checked and then unchecked. Solution: ProspectSoft CRM has now been updated to ensure that contacts can be granted access to a ProspectSoft Web Solutions website by entering a password and clicking 'Save'. No other action needs to be taken. Page 17 of 28

18 Web description and code fields are not searchable Reported in EBF 112 Updated in EBF 113 Ref: Symptoms: Searching in a ProspectSoft Web Solutions e-commerce web site does not search product web descriptions and codes. Solution: The search functionality now includes these fields. Inconsistent column names on Product Item list screens Reported in Ref: Symptoms: The column headers on the Product Item list screens that you see when searching for products from the Products option in the menu bar or when adding an item to a quotation have a column header for a field named Memo. The field being referenced here is called Extended Description in the other areas of ProspectSoft CRM. Solution: The column headers in the affected lists have now been made consistent with the rest of the product and renamed to Extended Description. Document relationships take a long time to create Reported in EBF 1 Ref: Symptoms: Creating a relationship either from or to a record in the document table takes a very long time on databases with a large number of document records. Solution: The way that information is retrieved about these relationships has been updated in this version of ProspectSoft CRM to be as efficient as possible. Users should see a reduction in the amount of time that it takes to create these types of relationships. Page 18 of 28

19 IRIS Exchequer version checking when opening transaction document Reported in Updated in EBF 100 Ref: Symptoms: When trying to open the document view for a sales or purchase ledger transaction in ProspectSoft CRM connected to an IRIS Exchequer version 6.x accounting system an error message will be displayed stating the functionality is only available in Exchequer version 5.50 or greater. Solution: IRIS Exchequer 6 and later have changed the format in which the version number is returned from the Exchequer COM toolkit. ProspectSoft CRM has now been updated to support checking of the version number formats returned by both Exchequer version 5 and version 6. PDF Reader for drill down on Opera II SL transactions Reported in Ref: Symptoms: Drilling down into Opera II transactions in the sales ledger or screen is opening the user s default web browser with the contents of the PDF rather than the default PDF reader for the system. Although the contents of the PDF can be seen having the PDF opened in the web browser prevents extra features that might be present in the PDF reader application such as the ability to send the PDF by . Solution: ProspectSoft CRM will now open PDFs from Opera II sales ledger transactions in the systems default PDF reader application. At a glance tabs do not fit on one page Reported in Ref: Symptoms: The At a glance tabs do not fit on one page except on systems with screens running at a very high resolution. Solution: These tabs have now been updated to fit better on screens with varying sizes and resolutions. Page 19 of 28

20 Lead Status Movement report does not have version 6 header Reported in Ref: Symptoms: The Lead Status Movement report does not have the correct version 6 formatting on the Lead No. field. Solution: This report has now been updated to use the new version 6 formatting. Campaign and Campaign Activity Summary reports do not react to enabled modules Reported in Ref: Symptoms: The Campaign Summary and Campaign Activity Summary reports are not respecting the users enabled ProspectSoft CRM modules which means that some displayed information is not useful. An example of this is the information regarding the percentage of targets quoted which should not be shown if the users do not have the quotation module. Solution: Both of these reports have now been updated to ensure that they respect the current modules in use on the ProspectSoft CRM system. Recalls by User report does not have version 6 header Reported in Ref: Symptoms: The Contact Details header on the Recalls by User report is not displaying using the new version 6 styles. Solution: This report has now been updated to ensure that all column headers are displayed using version 6 styles. Page 20 of 28

21 Cannot drill down from Product Category admin table Reported in Updated in EBF 1 Ref: Symptoms: It is not possible to drill down from the Product Category Admin Table even though this used to work in previous versions. Now, a message is displayed stating that "The required record does not exist on this database". Solution: This problem was due to a change made in EBF 1 to improve the efficiency of the drill down process. This change meant that drilling down into a product category required a field named "prodcatg" to exist in the report where previously either "prodcatg" or "prodcateg" would work. ProspectSoft CRM has now been updated so that drilling down into a product category can once again be enabled by using fields of name "prodcatg" or "prodcateg". Page 21 of 28

22 XML API Updates Can't cancel Exchent new SL window Reported in Updated in EBF 103 Ref: Symptoms: Setting the '.cancel' property on the 'w_response_create_slaccount_exchent' window's 'open.before' XML API event does not correctly cancel the opening of the window. The window opening is cancelled which is correct, however messages appear after the window has been cancelled that relate to the creation of sales ledgers. These messages are not appropriate. Solution: Using the '.cancel' property with the XML API on this window will now not cause any messages to be shown. Further to this, other windows in the application that are now cancelled from opening with the XML API should behave more appropriately as they now run through the same process that would be run if the user clicked the "Cancel" button on these windows. More properties on Exchequer Create SL Updated in EBF 103 Ref: , A new property containing the XML of the IRIS Exchequer "Create Sales Ledger" window has now been added to the event properties for all events on this window. Other properties containing details of the information that the user has entered have also been added. Can't use WindowAction to cancel new SL Reported in EBF 104 Updated in EBF 105 Ref: Symptoms: When trying to use the XML API Window Action Object to click the 'Cancel' button on the Exchequer Create Sales Ledger window an error number 2 "Null Object Reference" is being reported from the system. Solution: Using the XML API Window Action Object to click the cancel button in this way no longer causes errors. Page 22 of 28

23 EBF 2 Enhancements Less intrusive Outlook Contact Sync Updated in EBF 2 Ref: This version of ProspectSoft CRM includes a new version of Outlook Contact Sync that is designed to be less intrusive and work better while running in the background. In this new version the synchronisation progress indicator has been removed and replaced with a pop up "toaster" message when synchronisation has completed. Page 23 of 28

24 EBF 2 Updates Opera II VAT effective dates Reported in Updated in EBF 2 Ref: Symptoms: The dates at which new VAT rates should be applied are being correctly imported from the Opera II accounting system but are not being correctly applied. This results in users needing to change VAT rates immediately on a given day rather than having them apply automatically on the appropriate date. Solution: For ProspectSoft CRM systems integrated with Opera II the dates at which new VAT rates should be applied are now used correctly and new VAT rates will not apply until the specified date. Opera II Payment import incorrect Reported in Updated in EBF 240 Ref: Symptoms: ProspectSoft CRM is not correctly importing payment information into the sales history for some customer accounts when connected to the Opera II accounting system. Solution: The issue was due to the trimming of white space on some account codes in the payments import. This has now been updated to ensure that data is always trimmed and the correct information imported. Page 24 of 28

25 EBF 1 Enhancements 'PayDue' field in sales history Updated in: EBF 1 Ref: A new 'PayDue' field has been added to the 'SalesTrans' table. This is populated by the Payments import process for Pegasus Opera II and IRIS Exchequer. This field is not yet being set for Access Dimensions or Sage 50 but will be updated soon. This field is also now available for use in ODBC accounts integrations. For clarity: In the 'SalesTrans' table, 'inv_duedate' is the delivery due date, 'PayDue' is the Payment due date. "Ancestor / Summary" tab speed improvements Updated in: EBF 1 Ref: The "Ancestor / Summary" tab has been changed to be much more efficient, especially on larger databases and more active records. As part of these changes the tab will no longer search to see if objects lower down the hierarchy exist. i.e. it will no longer grey out the child folders if they are empty. Query efficiency improvements Updated in: EBF 1 Ref: Several database queries have been updated to use an equivalent but more efficient SQL statement to avoid unnecessary processing. Also, multiple database queries have been updated to ensure that the selection criteria that is used is the most efficient and specifically, to allow for better use of database indexes on large data sets. These improvements will be minor in themselves but will add up to an important improvement on some networks where many queries are executed across many users. Page 25 of 28

26 EBF 1 Updates Non-Stocked items not allocated in Opera II Reported in Updated in EBF 1 Ref: Symptoms: When confirming an order with non-stocked items on it, the stocked items are allocated correctly but the non-stocked items do not get allocated. This makes using Opera batch processing to delivery notes difficult. Solution: Non-stocked items are now allocated if the order contains only non-stocked items or where any stocked items are allocated i.e. Non-stocked items (such as a memo line) are not allocated if all the stocked items on that order are out of stock (so that the system does not deliver just the memo line). Opera "Product Item Supplier" fields Reported in Updated in EBF 1 Ref: Symptoms: The currency of the price and the economic order quantity fields are not being imported into the "Product Item Supplier" table. Solution: These are now imported. Product selection for lead not restricted by operating company Reported in Updated in EBF 1 Ref: Symptoms: When creating a lead and selecting a product category, the product category list is showing all product categories for all operating companies rather than just the one for that lead. Solution: The list is now filtered appropriately. Page 26 of 28

27 Profile data not created correctly on first start-up Reported in Updated in EBF 1 Ref: Symptoms: On some systems ProspectSoft CRM is not correctly configuring profiles for first use. As part of this process some files should be copied, however this is not happening and only the directories are copied and database connections configured. Solution: This problem was traced down to the system having either compressed or encrypted files set for the Default Data and Settings directory within the ProspectSoft CRM Program Files location. Due to these settings the files were not being identified as files that needed copying ProspectSoft CRM has now been updated to ensure that files are copied even if the source files are encrypted or compressed (or both). Array boundary exceeded when drilling down Reported in Updated in EBF 1 Ref: Symptoms: Sometimes when drilling down from a list into a detail view the system displays a message of "Error 3. Array boundary exceeded". Solution: The drill down functionality within ProspectSoft CRM has been re-written to avoid this error. During the process the functionality has also been made more efficient. Error when scrolling through Product Items using "Video" buttons Reported in Updated in EBF 1 Ref: Symptoms: If a user uses the "Video" buttons to step through a list of product items while viewing an xtra tab a "-194" error message is displayed on screen. Solution: This problem was due to the xtra tabs on product items requiring both a product reference and an operating company code. The system was only trying to set the product reference and so this error occurred. ProspectSoft CRM has now been updated to ensure that both values are now set. Page 27 of 28

28 Spelling and typographical errors Reported in Updated in EBF 1 Ref: Symptoms: Some message boxes in the system contain spelling and/or typographical errors. Solution: These have now been corrected. Page 28 of 28