Fixes

Better understanding of custom objects

Enhancements

We've made improvements so that Meldus more effectively understands the custom objects in your Salesforce org.

Perhaps you have a complex Salesforce org where you've created lots of custom objects and relationships. Or you rely heavily on AppExchange apps from Salesforce ISV partners that bring with them their own custom object data model. In either case, Meldus is now much more adept at providing the same great insights from data in your custom objects as it does with standard Sales and Service Cloud objects.

Fixes

Fixed an issue to ensure that any error responses from Salesforce are fed more clearly to Meldus's AI engine, leading to a much higher success rate on our built-in retry mechanism.

‍

Improved handling of clarification requests

Enhancements

We've greatly improved the way Meldus handles requests for clarification about a response to a previous question you've asked.

You can now ask Meldus to provide clarification of how it arrived at a previous answer to a question. You can ask it to clarify the fields that it selected, the Salesforce data objects it interrogated, or the filter criteria it used. Meldus will provide a simple explanation, but with enough specifics to clarify how it arrived at the answer it provided.

This improvement aims to give you even greater confidence in the answers you get from Salesforce using Meldus.

Fixes

• Fixed the text response handler to display the typing indicator consistent with the card response handler, to more clearly display when Meldus is creating a response.
• Adjusted AI logic to better handle requests that require multiple Name fields from related objects in Salesforce, to avoid duplicate field name errors.

Clarified wording of Connect to Salesforce card

Enhancements

We received handy feedback that, for new users, the step of connecting to Salesforce can be a little daunting. Newcomers to Meldus needed more clarity around how Meldus connects to Salesforce, how it uses that connection, and that users can disconnect at any time.

We've now clarified the wording on our Connect to Salesforce card to provide more information and streamline the connection step for new users.

Fixes

Fixed an issue in the Tour that caused a tour step to fail for users who are yet to connect to Salesforce.

Fixed Salesforce connection re-login requests

Enhancements

Adjusted wording on the Getting Started card, to help guide early users to the awesomeness of Meldus more easily.

Fixes

Fixed an issue affecting some users where the Salesforce connection required re-login too frequently.

‍

"My" and "I" questions

Enhancements

Introduced handling of “my” and “I” questions, such as:

• Give me a summary of my open opportunities
• How many accounts do I own in California with closed deals this year?
• What’s in my calendar for next week?

Meldus is now able to better use the context of your Salesforce user login to return results from Salesforce that you own or that relate to you. So let your ego run wild and ask the "my" questions you need.

Fixes

Tuned the bot’s exec summary to better summarise calendar events chronologically.

Fixed an issue where the bot formatted date parts such as years, quarters and months as numbers; now correctly formatted as text.

Locale-based dates

Enhancements

Introduced locale-based dates. Dates in results from Salesforce are now formatted based on your locale setting in Salesforce, and dates and times reflect your timezone setting.

Fixes

Tuned the bot’s understanding of more complex, multipart user questions and improved its ability to separate them into executable commands to Salesforce. We continue to fine tune the bot so it answers questions as often as possible with one command to Salesforce, and resorts to a multi-command approach only when absolutely necessary. It’s a tricky business, but we’re getting better all the time!

Improved performance for no rows

Enhancements

Removed retry on no rows returned: the bot previously made a second attempt to answer a question if the first attempt returned no rows from Salesforce, in case the empty result was caused by the bot making an error. As the bot has improved its accuracy, we removed that retry mechanism, which improves performance and usability, especially for multipart questions.

Fixes

Removed name personalisation from the exec summary to avoid confusion as to the ownership of records returned from Salesforce. For example, the bot was summarising a company-wide sales pipeline with “Hilda, your pipeline shows strong performance …”, which could create confusion.

Long number abbreviations

Enhancements

Introduced shortcut commands to apply number abbreviations in Salesforce results tables:

• mel short num: Meldus will use number abbreviations in results returned from Salesforce. E.g. 280.7k; 1.26M
• mel long num: Meldus uses the full number value in Salesforce results. E.g. 280,734.33; 1,264,765.76
  

Fixes

Minor fix to font rendering in charts on Mac OS.

Improved Salesforce connection handling

Enhancements

Extended Salesforce token refresh period.

Fixes

Fixed a minor bug with disconnecting from a Salesforce sandbox connection.