All Collections
Release Notes
Release Notes: V115
Release Notes: V115

See what features, functionality and fixes were shipped in Version 115 (January 2024).

Written by Martin Clark
Updated over a week ago

💡 Got a new idea, feature or enhancement suggestion for us? Head to the Ideas Portal to log it or vote on an existing idea!

Please note: We use Release Rings to systematically deliver new features in a way that minimises risk. This means that updates aren't rolled out to every user on the day they're shipped. Instead, they're gradually delivered to a small percentage of customers each day within specified Release Rings. Of course, if customers report issues with an update, we'll pause the rollout while we investigate. So, if you can't see the newest updates yet, don't worry - you'll receive them in the next few days or weeks.

🏃 Automation Flows Preview

This release contains an early preview of a very exciting new feature. Automation Flows will trigger a series of automated actions to be run at given time intervals following a specific trigger. The initial version supports just one type of trigger for automatically chasing Quotations. This takes the form of a configurable series of follow-up emails that can be triggered by sending a particular email to a customer.

For example you can configure an Automation Flow to send "Quote Chase 1" two days after sending your "New Customer Quote" email, and then follow-up a week later with "Quote Chase 2" and a month after that with "Final Quote Chase". Importantly each of these email templates could contain merged data related to the Quote, including the Quote-to-Order workflow buttons!

If you're interested in giving it a go, then just head to the System Settings and search for "Automation", turn it on and create your first Automation Flow, but do remember that this feature is in Preview so make sure you're monitoring your Flow carefully and giving us your feedback so that we can iterate and improve this exciting new feature.

In future, we'll expand the types of actions and types of triggers this system is capable of using. And, as with all preview features we'll decide which subscriptions will or won't include this feature when it has been further developed and is ready to be taken out of preview. In the meantime it's available to all customers to give it a try and give us feedback.

🌍 URL Type Custom Fields

You can now specify that custom text fields should be displayed as URL instead of plain text on records and reports. This will cause these custom fields to appear as a clickable link when read-only, or with a “go to site” button when shown as an editable field.

🪴 New Growth Metrics (Private Preview)

New “Attract”, “Sell” and “Close” metrics has been added to the Growth Engine Dashboard to complete the full set of metrics in the Growth Formula and Growth Playbook. These measure new Enquiries and Opportunities being created and closed in “Customer Acquisition” pipelines.

The Growth Engine Dashboard and Growth Metrics are in Private Preview at the moment while we work hard to test, review and refine the concept with selected customers. If you've got a particular interest in the Growth Playbook and would like to get involved in the Private Preview then please contact your Customer Success Manager. At this stage, spaces are limited and customers must have a minimum of two year's data in their CRM to partake, but once we're ready we'll be releasing this to more customers via a Public Preview, hopefully in the next couple of months.

🐛 Other Enhancements & Fixes

  • We now import purchase orders for Cin7 Omni which allows for future stock calculations and an accurate “Date next available” on Product items.

  • The Cin7 order stage field is now imported and pushed to Cin7 Omni orders when confirmed.

  • The delivery forename and surname in Cin7 Omni are now populated via new fields in the delivery details on a Quote.

  • Added support for tax per line in Cin7 Omni via a system option. This option is enabled by default in new trials, but disabled in existing systems to maintain backwards compatibility with existing customer processes.

  • The Enquiry conversion screen now suggests Companies and Contacts that match the data in the Enquiry.

  • Data import menu items have been added to the various groups in the left-hand menu to improve discoverability.

  • Added the ability to bulk update discounts on Quote lines.

  • Added support for Sierra Leone SLE currency.

  • Unlicensed users will no longer receive notification emails.

  • Fixed search crashes when attempting to search for a Contact that you're in the process of creating.

  • Fixed some crashes when generating entity descriptions.

  • Fixed a crash caused by the OData token expiring in the middle of a request.

  • Fixed OData lite accepting some invalid queries if non-boolean fields were used in a boolean filter.

  • Fixed a bug where the Overview Dashboard would show blank data on the first of the month, depending on when your nightly maintenance (which creates the summary monthly statistics) last ran.

  • Fixed a crash with Problem creation when the Problem Analysis Matrix was enabled.

  • Fixed a crash when import a product via Excel into an Operating Company with no other products.

  • Fixed a crash if a QuickBooks Online customer was deleted in the middle of a sync.

  • Fixed an occasional crash in the document management API when it first attempted to load information about a given Workspace/Database structure.

  • Improved the performance of Unleashed contact and sales shipment imports.

  • Fixed a crash when Unleashed warehouses were deleted.

  • Fixed crash caused by oddly named bespoke fields on documents.

  • Fixed crash when adding CRM Library files as attachments to emails when those files had non ascii characters in their names.

  • Fixed crash when sorting Reports by grouped fields, then removing the group.

  • Fixed issue where the “Convert to Quote” button on a Sales Order would disappear after reloading.

  • Fixed bug where resetting prices on a Quote line wouldn't reset the flag for whether the price had been manually overwritten.

  • Fixed crash when grouping by a “unit” type field.

  • Fixed a crash when attempting to retrieve a very large number of Xero customer records during the secondary invoices import.

  • Product item description can no longer be set when creating a product in Sage 50 since it has no field to map to.

  • Added the ability to define which OData API domain each workspace uses to help with staged migration to new OData deployments.

  • Updated the duplicate resolution banner to say when a previously detected potential duplicate customer has already been resolved, if clicking through from an old duplicate notification email.

  • Added some search keywords to the sync and document template system options.

  • CMS product item plugin will now show the a larger version of the image when mousing over additional images.

  • Updated the email Quote system options to appear in a single component.

  • Improved sales ledger name sanitisation for Sage 50 to avoid invalid characters being used.

  • Fixed a bug where unlinking upsell items would leave some fields incorrectly set.

  • Fixed a bug where obsoleting tax codes in Unleashed would leave them available in CRM.

  • Reverted a pricing update that prevented custom descriptions being used on Quote lines.

  • Added a “website domain” field to Company records which should contain the company’s website domain with other data removed, based on the website field.

  • Job Title is now mandatory when creating new users in the CRM.

  • Renamed “Change Parent” to “move [entity]”.

🖱️ Get immediate updates about the status of CRM services by subscribing to the CRM Status page. You'll then be the first to know about any important updates or maintenance affecting the CRM, our website, APIs, automation or integrations - so you don't have to wait for a response from our Support team. Plus, we'll post updates on progress by the minute - right from the time something was identified through to its resolution!

Did this answer your question?