407-248-1481
QuoteWerks Update Center
example: QuoteValet "payment option" -deposit
Version 5.2 Build 1.33 Summary
Version 5.2 Build 1.33 Summary
| 28 New, 25 Fixes, and 2 Miscellaneous features Released on 11/08/2016 View all features/fixes from all builds of version 5.2  See a video showcasing the new features. | ||
| New Features - Build 1 | ||
| 1. ConnectWise 2016.6 is now supported! [Service Release: 1.28] | ||
| 2. ConnectWise 2016.5 is now supported! [Service Release: 1.28] | ||
| 3. QuickBooks USA 2017 is now supported! [Service Release: 1.28] | ||
| 4. QuickBooks Australia 2016 is now supported! [Service Release: 1.28] | ||
| 5. QuickBooks Canada 2017 is now supported! [Service Release: 1.28] | ||
| 6. Peachtree/Sage 50 version 2017 is now supported! [Service Release: 1.28] | ||
| 7. There is now an "Installation Password" feature that can be used to prevent an unauthorized person from updating a QuoteWerks Installation. This is especially useful for preventing remote installations from updating without the permission of their IT administrator. It is also useful for IT administrators and resellers in preventing some random user from updating the network installation of QuoteWerks. Now, before an installation update can begin, if an Installation Password has been set by the administrator, the user will have to supply a valid Installation Password before they will be able to proceed with installing the update. [Service Release: 1.28] | ||
| 8. When a QuoteWerks update was just installed and a workstation runs QuoteWerks for the first time, it will now prevent other workstations from running QuoteWerks while QuoteWerks is upgrading the data to the new Build. [Service Release: 1.28] | ||
| 9. Most data stored in .ini files has been moved into database tables. All of the settings that have been transferred to database tables can be viewed from the new Settings Manager accessible by clicking on the [Settings Manager] button on the System tab of the Help->About menu. The Settings Manager is also available from within the Medic Utility by selecting the Utilities->Settings Manager menu. For complete details please see the help file topic "Appendix: QuoteWerks Version 5.2 INI to Database Changes". [Service Release: 1.28] | ||
| 10. Licensing enforcement no longer uses the .lck file based system. It now uses a Database license metering system. There are some powerful capabilities that come along with this change. Now, if a user is logged into QuoteWerks and locks their machine and leaves for the weekend, users with Master Rights can now revoke their license making it available for other users. When this user comes back they will only have the option to save and close their currently open quotes and exit. The Misc Access right "NonMasterRightsUser_CanRevokeOthersLicenseAllocation" can be granted to non Master Rights users to give them this capability. [Service Release: 1.28] | ||
| 11. Administrators can now force QuoteWerks to terminate. When an IT administrator wants to make sure everyone is out of QuoteWerks (to apply an update for example) they can force the termination of running instances of QuoteWerks. Any unsaved quotes will be saved as recovery documents. It is not ideal to terminate QuoteWerks this way, but if the admin has no other options, then at least they have the ability to terminate the running exe. The Misc Access right "NonMasterRightsUser_CanTerminateOthersRunningInstances" can be granted to non Master Rights users to give them this capability. [Service Release: 1.28] | ||
| 12. From the QuoteWerks Login window holding down SHIFT while clicking OK will launch the Logged In Users window where you can see what other users are logged into QuoteWerks. This window will only appear if have entered the correct password for the username. If you have rights to revoke licenses or terminate running instances you can do that from this window. An extra capability of this feature is that if a user is at this login screen and cannot login because there are not enough licenses, an administrator can walk over to this machine, choose their username, enter their password and get access to the Logged In Users window where they can revoke someone else's license. After closing this window, the login window will re-appear for the regular user to then login normally. [Service Release: 1.28] | ||
| 13. Licensing events are now recorded. Certain events are always recorded like license revokings, forced terminations are now recorded, reaching max Primary license count, reaching max Real-time license count, and reaching max QuoteValet license count. Other events like "[] Record failed login attempts", and "[] Record successful login/logoff (includes duration)" can be turned on/off under the Security tab of the Tools->Options menu. You can display the Event Viewer by clicking on the [Event Viewer] button on the Utilities->LoggedInUsers menu. [Service Release: 1.28] | ||
| 14. When a login fails because there are not enough licenses, the Logged In Users window will automatically be displayed. [Service Release: 1.28] | ||
| 15. If you attempt to login using a UserName that is already logged into QuoteWerks, you will be given the option to revoke the license from the other logged in instance so that you can login. [Service Release: 1.28] | ||
| 16. For Autotask users, when creating or updating an Autotask Quote the QuoteWerks Customer PO# now populates the PurchaseOrderNumber field in the Autotask quote. [Service Release: 1.28] | ||
| 17. For ConnectWise 2016.3 and higher users, QuoteWerks recurring products can now be written to a ConnectWise Opportunity Item as a recurring product (utilizing this newer feature in ConnectWise). This feature is only available in the new ConnectWise REST API. It is not available in the older ConnectWise SOAP API, so you must enable the ConnectWise REST API in QuoteWerks setup to use this new feature. [Service Release: 1.28] | ||
| 18. For ConnectWise 2016.3 and higher users, when the ConnectWise REST API is enabled, there is now an option on the REST API tab of the ConnectWise Setup window to "write QuoteWerks SoldToPONumber 'Cust PO#' to ConnectWise Opportunity". [Service Release: 1.28] | ||
| 19. Bundles can now be searched by Begins with, Contains, and Ends with. The last selection is remembered per user. [Service Release: 1.28] | ||
| 20. Configurations can now be searched by Begins with, Contains, and Ends with. The last selection is remembered per user. [Service Release: 1.28] | ||
| 21. When rehosting to SQL you can now specify an existing Database to rehost to. This is useful so that you do not have to supply a SQL server UserID that has the security rights to create databases. [Service Release: 1.28] | ||
| 22. Added new Misc Access rights CannotModifyFieldValue:DI_CustomDate01, CannotModifyFieldValue:DI_CustomDate02, CannotModifyFieldValue:DI_CustomNumber01, CannotModifyFieldValue:DI_CustomNumber02, CannotModifyFieldValue:DI_CustomNumber03, CannotModifyFieldValue:DI_CustomNumber04, CannotModifyFieldValue:DI_CustomNumber05, CannotModifyFieldValue:DI_CustomMemo01, CannotModifyFieldValue:DI_CustomMemo02, CannotModifyFieldValue:DI_InternalPartNumber [Service Release: 1.28] | ||
| 23. For API users, added the events: BeforeSynchronization(sXMLData, bCancel) AND AfterSynchronization(sXMLData) [Service Release: 1.28] | ||
| 24. For API users, the event BeforeSaveDocument(ByVal iSaveAction As Integer, ByRef bCancel as Boolean) now fires for the AutoSave events with an iSaveAction=4. [Service Release: 1.28] | ||
| 25. For API users, added event AfterSaveDocumentEx(ByVal iSaveAction As Integer, ByVal iResult As Integer, ByVal sXMLData As String). This event provides more information than the existing AfterSaveDocument() event. [Service Release: 1.28] | ||
| 26. The creation of user login names is no longer limited by the 8 character user INI file name generation. You used to receive a message like "The User Name specified cannot be added because it conflicts with the {username}.ini file of JLEWE.INI" [Service Release: 1.28] | ||
| 27. Under the [Addons] section of the siteboot.ini file there is a new AutoRunXUsers= key. Here you can specify a comma delimited list of users that you want the addon for. For example the AutoRun1=notepad.exe and the AutoRun1Users=John Lewe, Brian Laufer [Service Release: 1.28] | ||
| 28. For API users, added a series of methods to read/write/delete settings from the new Settings table since the data has been moved out of ini files into the database.
Application.SiteSettingRead (sSectionName as String, sKeyName as String)
Application.SiteSettingWrite (sSectionName as String, sKeyName as String, sKeyValue as String)
Application.SiteSettingDelete (sSectionName as String, sKeyName as String)
Application.SystemSettingRead (sSectionName as String, sKeyName as String)
Application.SystemSettingWrite (sSectionName as String, sKeyName as String, sKeyValue as String)
Application.SystemSettingDelete (sSectionName as String, sKeyName as String)
Application.UserSettingRead (sUserName as String, sSectionName as String, sKeyName as String)
Application.UserSettingWrite (sUserName as String, sSectionName as String, sKeyName as String, sKeyValue as String)
Application.UserSettingDelete (sUserName as String, sSectionName as String, sKeyName as String, sKeyValue as String) [Service Release: 1.28] | ||
| Misc Features - Build 1 | ||
| 1. For Autotask users, for the next release of Autotask 2016.2, numeric API queries no longer support the Begins With operator. Changes were made to accomodate this. [Service Release: 1.28] | ||
| 2. Added more detailed logging of the version 5.2 upgrade process in the event.log. [Service Release: 1.33] | ||
| Fixes - Build 1 | ||
| 1. On installations rehosted to SQL many years ago, when upgraded to v5.1 build 6.01 - 6.06 in some cases, would receive error "INIFileName was empty for user..." when starting QuoteWerks. This version 5.2 Build 1 upgrade will correct this issue for all versions in all scenarios. [Service Release: 1.28] | ||
| 2. AutoSave was being prompted during changes in the User Maintenance. [Service Release: 1.28] | ||
| 3. Fixed issue with the re-establish connection for SQL database lost connections. [Service Release: 1.28] | ||
| 4. Under Utilities->User Maintenance, when deleting a user or creating a new user, the Auto-Save would be triggered. [Service Release: 1.28] | ||
| 5. On the Open Document window when resizing the width past a 27 inch monitor size the grid would suddenly shrink. [Service Release: 1.28] | ||
| 6. When using Product Lookup and Etilize, clicking on a website link for SYNNEX was not working because SYNNEX changed their website. [Service Release: 1.28] | ||
| 7. When using Product Lookup and Etilize, clicking on a website link for Ingram Micro was not working because Ingram Micro changed their website. [Service Release: 1.28] | ||
| 8. For ConnectWise 2016.3 and higher users, there is now an option to use the new ConnectWise REST API. This new API contains the fix for the issue where Group Member quantities sent to ConnectWise were not being calculated correctly by ConnectWise. ConnectWise was not applying the group header quantity multiplier. The older ConnectWise SOAP API does not contain a fix for this issue. [Service Release: 1.28] | ||
| 9. For Autotask Users, no vendors would be returned when creating Purchase Orders in Autotask 2016.2. [Service Release: 1.28] | ||
| 10. For Etilize Users, the 'My Favorites' would return no results if a product was added to the 'My Favorites' that was obtained from the Product Content Server rather than from Etilize. [Service Release: 1.28] | ||
| 11. For Synnex users, would receive "Error, warehouse code not found for SYNNEX warehouse..." [Service Release: 1.28] | ||
| 12. For Autotask Users, when updating an existing Autotask Quote that had a Project associated with it, the project would be removed. [Service Release: 1.28] | ||
| 13. For Autotask users, when receiving an item from the Purchasing window and entering the Serial Number at the same time, would receive an error and the item would not be received in Autotask. [Service Release: 1.28] | ||
| 14. For salesforce.com users, when saving an opportunity would receive error 13 when writing opportunity line items that included a product with a part number that was duplicated in salesforce.com, both with the same part number, but one was active and the other was inactive, would receive error 13. [Service Release: 1.28] | ||
| 15. For salesforce.com users, when saving an opportunity would receive error 13 when writing opportunity line items that included the same part number on multiple line items in the quote, would receive error 13. [Service Release: 1.28] | ||
| 16. Increased SQL Query timeout from 30 to 60 seconds in the Open Document, Management Reports, and Tools->Find Quoted Item areas. [Service Release: 1.28] | ||
| 17. Salesforce was removing all opportunity line items when 'Write Products into Opportunity' was unchecked. [Service Release: 1.28] | ||
| 18. For salesforce.com users, receiving runtime 13 error when a user was creating an opportunity with lineitems where the Manufacturer Part # was matching multiple products with the same name field in a salesforce.com pricebook. [Service Release: 1.28] | ||
| 19. When using the new ConnectWise REST API option to write products to the ConnectWise opportunity, the line items were not being written in the same sequence as they were in QuoteWerks. [Service Release: 1.28] | ||
| 20. If you display a layout FPC file in the editor, then close the editor, then preview/print the report and if you click cancel on a dialog input field, an error would occur. [Service Release: 1.28] | ||
| 21. If a document was locked and the Misc Access right of "CannotUnLockDocuments" was set you would incorrectly be prompted with "Unlocking will remove Approval - Proceed?". [Service Release: 1.28] | ||
| 22. For Dell Punchout users, the multi-line description that came from Dell was appearing as a single line in QuoteWerks. [Service Release: 1.28] | ||
| 23. On startup before the version 5.2 conversion is run received error opening recordset in ConnOpenRecordset() SQL=SELECT KeyValue from SystemSettings WHERE SectionName='QuoteValet' AND KeyName='TenantAccountNumber' [Service Release: 1.29] | ||
| 24. During the version 5.2 conversion the Most Recently Used (MRU) documents were copied into the MRU Templates list. [Service Release: 1.29] | ||
| 25. When sending an email and choosing the "Don't Log' option for "Log sent e-mail in CRM", this option was being ignored and the email was getting logged anyway. [Service Release: 1.29] | ||
©1993-2024 Aspire Technologies, Inc.
407-248-1481 (9am-5pm ET M-F)
Please Wait...