QuoteWerks Update Center


Version: Build

Version 4.6 Build 05.09 Summary
35 New, 39 Fixes, and 9 Miscellaneous features Released on 06/10/2011

Download (114 MB)

See a video showcasing the new features.

New Features - Build 5
 1. SugarCRM 6.2 is now supported!

 2. Support for MS CRM 5.0 (Active Directory only). Internet Facing Deployment (IFD) is not supported. Microsoft Dynamics CRM Online is not supported.

 3. Peachtree 2012 is now supported!

 4. Autotask is now supported with the new built-in Autotask link. This new integration is available in the Corporate Edition of QuoteWerks. The integration includes: a) Autotask can be searched to find Contacts to pull into the quote. b) QuoteWerks will create/update a Sales opportunity in Autotask. You can attach to existing Autotask opportunities or create new opportunities in Autotask. c) QuoteWerks will create/update an attachment to the quote under the Attachments tab in the Autotask Opportunity. This can be used to open the quote that the opportunity refers to. If this is a remote install or satellite office, opening that document link will import that quote into that QuoteWerks installation. d) QuoteWerks will create/update the Autotask Quote associated with the Opportunity. Line Items in QuoteWerks are automatically attached to the Autotask Quote. Products that do not already exist in Autotask are created in the Autotask master product database. Recurring revenue forecasting options are also supported. e) QuoteWerks can link to the Autotask Products and Services databases as Product Data Sources. From within QuoteWerks you can search the Autotask databases and add these products and services to your QuoteWerks quote. f) There is a "Display contact in contact manager" button on the SoldTo / ShipTo tab that will open the Autotask Contact in Autotask for the SoldTo, ShipTo, or BillTo linked contact. g) There is a "Display Opportunity in contact manager" button on the QuoteWerks Create/Update Autotask Opportunity window that will open the Autotask Opportunity in Autotask. h) There is a "Display Quote in contact manager" button on the QuoteWerks Create/Update Autotask Quote window that will open the Autotask Quote in Autotask.

 5. ConnectWise 2011.2 is now supported! Starting with this build of QuoteWerks (Build 5), QuoteWerks will only support ConnectWise 2011.2 or higher. The entire ConnectWise Integration has been re-written from the ground up to take advantage of many new public APIs available in 2011.2. As a result, the integration is overall much faster and now almost completely uses their public APIs.

 6. For ConnectWise users, the Primary SalesRep can now be specified When Creating/Updating an opportunity.

 7. For ConnectWise users, support has been added for product class types of "Service" and "Agreement". The forecast creation logic for these product class types now mirrors ConnectWise.

 8. For ConnectWise users, on the Create/Update Opportunity Window, Sales Stages are now sorted by the underlying Sequence Number instead of by their Description.

 9. For ConnectWise users, the Location and Business Unit for a new opportunity default to the default Location and Business Unit set for the selected company in ConnectWise.

 10. For ConnectWise users, the shipping amount specified on the Shipping Amount window accessible from the Document Items tab can now be sent over to the ConnectWise opportunity as a forecast summary line, or an individual product (including cost).

 11. The synchronization of documents like quotes/orders/invoices will now propagate document deletions out between the master installation, remote site installation, and remote pc installations. Once this update is installed, all deletions be recorded and then propagated when the sync process is run. It will not retroactively apply deletes that happened before build 5 was installed. Deletions on the master will propagate out to the remote laptop installation, and also any quotes deleted from the remote installation will be deleted from the master installation. Security rights determine if a user can delete quotes. Before a quote is deleted, a backup is made of it in the \QuoteWerks\DTF folder like jbnlQ1001.b01 just in case it needs to be recovered.

 12. For Corporate Edition users rehosted to SQL, Email Templates (introduced in this build) can now be rolled out to remote installations or bi-directionally synchronized (including deletions).

 13. Email templating system. Under the Tools->Customize E-Mail Templates menu you can now customize all the emails that QuoteWerks sends. The E-mail Templates window can stay open while sending e-mails in QuoteWerks making it easy to quickly make adjustments and preview the results. There are System, Public and user E-Mail templates. System Email Templates are templates like "SYS_EmailQuote", "SYS_EmailPeerReviewRequest", etc. These are the templates that are used when sending these types of emails. The System templates can be directly modified by users with Master Rights. If individual users want their own versions of these templates, they simply clone the System template which creates a copy with the same name, but it is owned by the user. Then, when sending these types of emails, if the user has a template with the same name like "SYS_EmailQuote", then that template will be used. Users can also create their own templates to be used from the Send Email window. There is now a new "Select Template" dropdown on the Send Email window. When a template is selected, the subject and body of the email will be updated with the information from the template. We've introduced a feature called "Template Contexts". Imagine you create a whole bunch of email templates, some that you use when emailing a quote, some that you use when emailing an invoice, some that you use when emailing a management report, etc. If we just listed all the templates, it would be a massive list of templates to choose from that were not relevant to what you were doing. With the Templates Contexts feature, you choose when the template appears in the list of templates to choose from. Public templates can also be created. Public templates would be templates that most users would want to use, typically with company standardized information in them. So, rather than each user create their own copy with the same information, the administrator could just create a Public template that all the users could use. The real benefit here is that changes can be made in one template, and all the users now are using the updated template. Public templates (based on their context) will appear in the list of templates for all users on the Send Email window. The E-Mail templating system only supports HTML formatted text. Because of this, the default "Message Format" option for "HTML" or "Plain text" has been removed. This was located under the Tools->My Preferences, Email tab, and then Defaults subttab. With the introduction of the Email Templates feature set, this setting is no longer relevant. The Email format can still be changed on the Send Email window from HTML to Plain text, thereby stripping out any HTML formatting.

 14. Email snippets. Email Snippets are a great way to centrally organize and maintain information that is used in multiple email templates. If you have two email templates that both need to include the same information, you could of course type that same information into both email templates, and then when you need to make a change, you will need to remember to change it in both the email templates. If you entered that information into a Snippet, and then used a macro in the two email templates to refer to that Snippet, then you could just make changes to the information in the snippet and the changes will automatically appear in the two email templates. There are Public and user E-Mail Snippets. Just like with E-Mail templates, Public Snippets would be snippets of information that most users would want to use, typically with company standardized information in them. So, rather than each user create their own Snippet with the same information, the administrator could just create a Public Snippet that all the users could use. The real benefit here is that changes can be made in one Snippet, all the templates that the snippet is used in will be updated. To use a Public Snippet in an email template or an email signature, simply include the macro PublicSnippet:{snippet name} and replace the entire {snippet name} portion with the name of the Snippet. The macro name to include a Snippet owned by the logged in user is MySnippet:{snippet name}.

 15. Information from external files can be included in E-Mail Templates, E-Mail Snippets, and E-Mail Signatures. Simply include the macro File:{file name and path} and replace the entire {file name and path} portion with something like f:\goldmine\jcl.html. You can use this to insert html or plain text.

 16. The following new macros are only available in email templates RecipientName, RecipientFirstName, RecipientLastName, RecipientEmail.

 17. There are some advanced macros that can be used in the HTML Email Templates, Snippets, and Signatures. They are SystemTemplateBody:{Name}, SystemTemplateSubject:{Name}, PublicTemplateBody:{Name}, PublicTemplateSubject:{Name}, MyTemplateBody:{Name}, MyTemplateSubject:{Name}. These can be used to do some neat things, like create a template that includes all the information from another template and then just adds some more information above or below the other templates information. For example, there might be a public template that contains information thanking the customer for placing an order, and you can then create your own template that adds your own summary of the information above it. The subject version of the macro is used to obtain the subject of the email template. You can use this in the subject line of another template.


 19. You can now have more than one email signature. In fact, you have a Standard, Short, Alternate1, Alternate2, and Alternate3 email signature. There are so many uses for this. During each season of the year, you might have a slightly different e-mail signature (like Happy Halloween, Merry Christmas, Happy New Year, etc) and now you can keep them all instead of replacing it each time. Sometimes you want to include your signature complete with your full address, phone number, title, etc. Other times you will just want to include your Short signature, like just your name, title, and phone number. The short signature is particularly good for QuoteValet "Your Quote is Ready" emails to your customers. The Email signature macros for use in the email templates are SignatureStandard, SignatureShort, SignatureAlternate1, SignatureAlternate2, SignatureAlternate3. Rather than typing in your email signature into each email template you setup, you can use email signature macros in them, making it easy to change your email signature in one place.

 20. There is a new Active Signature feature. When using an email signature macro in a template, you can use SignatureActive instead of SignatureStandard, SignatureShort, etc. When you use the SignatureActive macro, it will be replaced with whatever you set as the Active Signature. Take for example, if you have 20 email templates and in each one you used the macro SignatureStandard, then when you wanted to use a different signature like SignatureAlternate1, you would have to edit 20 templates. With the Active Signature feature, just use the SignatureActive macro in the 20 templates, and then under the Email tab of the Tools->My Preferences menu, just change your Active Signature to Alternate1 and you will not have to modify any of the templates. You can also switch between signatures that might have a monthly special offer included in it.

 21. Added several Misc Access rights for the new E-Mail Templating features which are CannotCreatePublicEmailTemplates, CannotModifyPublicEmailTemplates, CannotDeletePublicEmailTemplates, CannotViewOthersEmailTemplates, CannotCreatePublicEmailSnippets, CannotModifyPublicEmailSnippets, CannotDeletePublicEmailSnippets, and CannotViewOthersEmailSnippets.

 22. You can now right click on a File Link on the Links tab of the Quote WorkBook and email the selected file.

 23. The manual shipping amount specified on the Shipping Amount window accessible from the Document Items tab can now have a cost and an Item Type associated with it. A default ItemType for shipping can be set on the Documents tab under Tools->Options.

 24. On the QuoteValet tab under Tools->Options menu, there are now the options "Use For Peer Reviews" and "Use for Approval Requests" options for QuoteValet. With these settings, when QuoteValet is enabled, you can now choose to not use QuoteValet for these functions, if you prefer to just use the email method for these functions.

 25. Added new Approval restriction of "Don't allow Save to PDF until approved". When the document requires approval, the user will not be able to save a PDF file from the File->Print window, or save a PDF file from the Preview window.

 26. When inserting a heading line (Edit->Insert Heading), there is now an F2Lookup (press F2) to store a list of commonly used headings to select from.

 27. On the Send E-Mail window, ALT-S will now send the email.

 28. When clicking on the [Submit for Peer Review] button on the File->Print window, the email is now sent from the logged in user versus from the sales rep specified in the quote.

 29. When cloning a user, the email templates and email signatures for the user are also cloned.

 30. Added new macro field &APP_LoggedInUserMobilePhone.

 31. On the Print window, there is now a [QuoteValet Express Mode] button. When clicked, the quote will be saved quickly (without prompting for CRM integration), it will be uploaded to QuoteValet, and it will be previewed in your web browser. This is meant to be used after the initial upload of the quote to QuoteValet. This helps speed up the process of uploading, making changes, and then re-uploading. [Service Release: 5.09]

 32. On the Upload to QuoteValet window, pressing the ESCAPE key will close the form. [Service Release: 5.09]

 33. On the Upload to QuoteValet window, after emailing the customer notification email the window will be closed. [Service Release: 5.09]

 34. Added a new "Auto Preview after upload checkbox on the Upload to QuoteValet window. When checked, this will preview the QuoteValet quote in your web browser, performing two actions with a single click. This setting is remembered per user. [Service Release: 5.09]

 35. For ConnectWise users, it is now possible to create a Call activity without specifying a time. [Service Release: 5.09]

Misc Features - Build 5
 1. Added the field DocumentHeaders.SoldToCMCounterpartRecID text (50) Used to store the id for the quote counterpart in the CRM system.

 2. The Internet tab of the Tools->My Preferences menu was renamed to "E-Mail".

 3. When running any of the node installation msi installers on a terminal server, the msi installer option to install for all users is now being set.

 4. Removed the &DI_&FirstLineDescription macro from the subject of default system email templates. [Service Release: 5.01]

 5. When saving a document as a template, the DocDate, DocDueDate, and ExpirationDate fields are now cleared. [Service Release: 5.01]

 6. For GoldMine users, the list of GoldMine users returned from GoldMine was no longer returned in alphabetical order, so a sort is now applied by QuoteWerks. [Service Release: 5.01]

 7. For ConnectWise users, the Location List and Business Unit List is now ordered alphabetically. [Service Release: 5.01]

 8. When the Print Window is displayed, it the layout last used with the document is missing you are now notified in the status bar. [Service Release: 5.09]

 9. For ConnectWise users, there was an issue where a cryptic error exception would be displayed when attempting to create/update a call activity if the activity type of 'call' had been renamed or deleted from ConnectWise. Now a friendly error message is shown describing how to resolve the issue. [Service Release: 5.09]

Fixes - Build 5
 1. Error 53 when running a word merge on a DOCX file type.

 2. For Windows 7 users, when printing and choosing to print more than 1 copy, only 1 copy was being printed.

 3. When previewing a quote generated from a Microsoft Word merge, a file like "Word Quote_2011-04-22_4-21.46pm" would be created in the \QuoteWerks\Resources folder.

 4. When using the File->Insert Document menu, the pictures for any line items containing pictures would not appear in the print output until the quote had been saved and re-opened.

 5. For some Etilize part numbers pictures would not be retrieved, and an error message would be displayed about the Etilize part number not matching.

 6. For Etilize users, sometimes Etilize returns more than one part number for an item for each distributor. Sometimes one of the part numbers is discontinued and the other is valid. For Tech Data we now use the last part number in the list, for all other distributors, we use the first part number in the list.

 7. Would receive error 13 type mismatch when saving a quote if the DataLink was used to retrieve a value from a CRM application into a date field and the value retrieved from the CRM application was not a valid date.

 8. If a Synchronization failed, and you selected the Utilities->Sync menu again without exiting QuoteWerks, the wizard would start at the last step. You also did not get to see the error summary page.

 9. If a multiple escalated approvals were required for a quote approval, after the first escalated approver approved the quote, the File->Approve Quote menu would be disabled, so the second escalated approver would not be able to approve it.

 10. For QuoteValet users, if a quote was opened from an external link like a document link in a CRM package or from a DTF file, when the quote was opened, it was not getting updated with QuoteValet Activity.

 11. When editing an HTML signature and using the macro drop down list to insert a macro, macros that started with "&DH_&" like "DH_&FirstName" were being inserted as "&DH_".

 12. The last position and size of the Send email window was not being remembered.

 13. The Word merge macros were case sensitive, but should not be, so if they were not typed in exactly with the same upper and lower case letters, the macro would not be found.

 14. For ConnectWise users, an issue where DTF attachments would be duplicated on the Documents Tab of a ConnectWise Opportunity has been resolved.

 15. For ConnectWise users, an issue where forecast lines would be duplicated in ConnectWise upon Convert to Order, Invoice, etc. has been resolved.

 16. For ConnectWise users, an issue where Call Activities were intermittently not being updated has been resolved.

 17. For ConnectWise users, if an item marked as recurring in QuoteWerks was set to 'Include First Payment in Document Totals' the value of the associated Forecast created in ConnectWise was incorrectly inflated by the amount of that first payment.

 18. For ConnectWise users, in rare situations, the Create/Update Opportunity window would either not be displayed, or would be displayed twice.

 19. If macros are used in the DocName, invalid characters are now stripped from the macro data.

 20. For ConnectWise users, if including the first months payment in a recurring revenue item, an extra period was being calculated when it was sent over to ConnectWise.

 21. If QuoteValet tenant account credentials were removed, effectively disabling the QuoteValet integration, when printing would receive an error message about the QuoteValet credentials being invalid.

 22. QuoteWerks manufacturer field is 40 characters long. In cases where Etilize returned a manufacturer name longer than 40 characters, it will be truncated and no error message will be displayed.

 23. If a user with administrator rights Approved a document, and that user was not specifically named as an approver for that sales reps documents, or if that user was only in a group and that group was specified as the approver, the quote would be approved, but the sales rep would be informed that it was not approved.

 24. For ACT!, ACT! for Web, Outlook BCM, and MS CRM users, when line item detail was being written into the sales opportunity, if the quote included a group that was optional, the individual items were incorrectly being included in the sales opportunity line item detail.

 25. When creating a new quote from a template and then creating another new quote from the same template during the same session of QuoteWerks would receive error about the document already being in use.

 26. If using the following fields in a print layout would receive an error about them not be found in ReturnArrayValue(). ApprovedMethod1, ApprovedMethod2, ApprovedOn1, ApprovedOn2, ApprovedBy1, ApprovedBy2, ApprovalRequestedMethod, and ApprovalRequestedOn.

 27. For Outlook 2010 public folder users, the public folder macro was not being merged for the public calendar or public journal folders. [Service Release: 5.01]

 28. When upgrading from QuoteWerks 3.0 would receive error "the field name SoldToCMCounterpartRecID was not found..." [Service Release: 5.01]

 29. Issue with synchronization between time zones where one observed DST and the other did not. [Service Release: 5.02]

 30. For ConnectWise users, when updating an opportunity with individual line items, if a line item had a quantity of 0 the line item would be sent over with a quantity of 1. Now, line items with a quantity of 0 are not sent over. [Service Release: 5.09]

 31. For ConnectWise users, error would occur if the ConnectWise Integration was configured to both (send over product data as a rollup) AND (send shipping over a product). Now, under this configuration the shipping goes over under the rollup and a warning is presented at the time of setup indicating this behavior. [Service Release: 5.09]

 32. For ConnectWise users, error would occur while creating/updating an opportunity in ConnectWise if the link was configured to create individual line item data and one of the line items contained an apostrophe in the manufacturer part number. [Service Release: 5.09]

 33. For ConnectWise users when attempting to link to an existing opportunity, closed opportunities were being displayed in the list. [Service Release: 5.09]

 34. When a new document was created from a template and an expiration date was specified in the template, it was getting overwritten in the new document. Now it is only calculated if no expiration date is saved into the template. [Service Release: 5.09]

 35. If the save button was clicked while editing an email template, while in the advanced direct HTML editing mode, the template would not be saved. [Service Release: 5.09]

 36. When setting up Approval Settings, if no Approvers were specified there was no warning. [Service Release: 5.09]

 37. If the apostrophe character was in the data fields merged into an email template it would be displayed as "'" [Service Release: 5.09]

 38. Once a document has been approved and locked, unlocking the document will now remove the approval, approval request and peer review request history. The removal is logged in the document's transaction log viewed under the File->Properties menu. [Service Release: 5.09]

 39. When converting a Quote to an order using the File->Convert to Order menu that has been uploaded to QuoteValet for customer acceptance, afterwards when closing the order, you would be asked if you wanted to upload the changes to QuoteValet. [Service Release: 5.09]

Previous significant build released just days prior
Misc Features - Build 4
 1. Internal Build. This build was not released to the public and is not available for download.