Submit a request and our team will get back to you quickly.

Multi-CCIO Performance Release Notes

Matching & Routing

Scalability Performance Optimization
LeanData Matching & Routing now support even more throughput! Without increasing any processing demands on your Salesforce org, LeanData can process more records in a shorter amount of time. This means that you can qualify, assign, and convert more prospects.

You can now benefit from the improved performance without making any changes to your settings; this enhancement is built into the platform.

 

Field & Permissions Lists for Tagging & Routing
Easily coordinate updates in LeanData with your Salesforce Admin, IT, and other cross-functional teams. You can now download and share the list of all fields used within LeanData Tagging and Routing to provide more visibility into your Matching and Routing dependencies. This visibility can help you accelerate LeanData implementations, migrations, and updates within Salesforce, and help you prevent changes in Salesforce from impacting your GTM processes.

This new feature is available on the Admin > Settings page for deployed graphs, and via the File menu on the Flowbuilder graph.

Use Cases

• When you place an “Update” node in your graph, the Integration User will require Edit access for the fields that get updated in the node. You can use the “Download List of Fields” feature to confirm that “Read/Write” access is required, and then provide this list to your SFDC admin. This will help them quickly check and update the existing permissions for the Integration User, prior to you deploying the graph, and prevent routing and processing interruptions.
   
• When migrating Tagging or Routing from your Sandbox to Production, first download the list of fields and provide them to your SFDC Admin. Your admin can then quickly determine fields and level of access the Integration User will need to ensure Tagging and Routing in your Production environment will function as planned.

Fuzzy Matching for Street Addresses
Find better matches without having to normalize street addresses! Now, when you use the “equals” operator in filters and tiebreakers, LeanData will perform fuzzy matching on street address fields. This can save you hours of time by eliminating the need to normalize street addresses in order to find the best match, enabling you to more quickly match and route the right records to your team.

This enhancement is now part of the existing “equals” operator in all filters and tiebreakers, for both Matching and Routing.

Use Cases

• Match a lead, which has a street address containing “Dr.”, to an account, which has the same address except that it is spelled with “Drive.” Although the two address fields represent the same location, but are not the same fields character-for-character (“Dr.” versus “Drive”), the equals operator will consider them a match for the tiebreaker.
• • For instance, 2901 Patrick Henry Dr. will be considered a match to 2901 Patrick Henry Drive.

 

Round Robin Configuration Wizard
Managing Round Robin pools just got easier! When updating the order of your Round Robin members in unweighted pools, there is no hidden logic - the order of the members listed will correspond with the order they will receive records. This makes it easier for you to edit the order and explain it to any of your stakeholders.

When editing pool members, you will now be presented with a wizard to easily add, remove, or reorder pool members, as well as select which member is the next up. You can now see who received the previous record, who is expected to receive the next record, and easily select who will be the “Next Up”. You can also use this wizard with multiple pools at once by selecting the check box next to multiple pools and clicking “Edit Users in Pools.”

Use Case

• Reorder a Pool to determine the order in which users will receive records. Share the info with stakeholders knowing exactly who will receive the next set of records.

 

Proactive Notifications for State/Country Settings
Stay aligned with your State/Country settings in Salesforce with better visibility! You will now see new error messages within deployed graphs if there is inconsistency in your use of State/Country fields or State/Country codes between Salesforce and any LeanData Routing Trigger nodes. In the past, when there was a mismatch across these settings, records would not be picked up for routing by your Trigger node, and routing could silently fail. This new feature ensures you have the information needed to resolve mismatched configurations and route every record quickly and accurately.

Use Cases

• If you have enabled State/Country codes in Salesforce, but your Trigger nodes in LeanData have been set to detect changes in State/Country fields, then you will see error messages in the deployed graph and also be notified via email. The email will notify you that the State/Country settings are mismatched, impacting routing triggers, so that you can quickly resolve the issue.
• If you have disabled State/Country codes in Salesforce, but your Trigger nodes in LeanData have been set to detect changes in State/Country codes, then you will also see error messages in the deployed graph and be notified via email as in the above example.

Example email notification:

 

Merge Fields for URLs
URL fields can now be updated using merge fields! You now have more flexibility when populating URL information on Leads with the ability to create a unique URL for any record that gets routed. This can help you and your reps save time when searching for account information, troubleshooting routing, or synchronizing information across systems.

This new functionality can be found in Update nodes within any FlowBuilder graph.

Use Cases

• Marketing Automation: Create a unique URL for the Lead in a different system by combining a prefix for marketing automation appended with the ID of the record in the Marketing Automation.
• Audit Log Links: LeanData admins and reps can insert the full audit log link in a URL field for full visibility into the routing path a record took.

 

Full Audit Log Links for Notifications
Spend less time searching your audit logs! When sending notifications from within Routing, you can now include a link to the full audit log for each specific record. This eliminates the need to filter and search through Audit Logs when you’ve been notified about a specific record; just open the link from directly within the notification.

This new feature can be found in the following areas:

• Action nodes > Success/Failure Notifications > Insert a Field > Full Audit Log Link
• Send Notification node > Chatter/Email > Insert a Field > Full Audit Log Link
• Slack Integration node > Insert a Field > Full Audit Log Link

Use Cases:

• Lead Conversion Notifications: When notifying a sales manager about a new lead that converted, provide them with a link to view the Lead’s full routing path until conversion.
• Troubleshooting Notifications: When sending a failure notification from an action node, provide the link to the full audit log so that you can quickly access the log, understand the context for the error, and make adjustments to the graph sooner.

 

Copy Nodes Across Graphs

Build processes faster without “reinventing the wheel!” When creating a new graph or editing an existing graph in FlowBuilder, you can now copy individual nodes or branches of multiple nodes from other graphs and paste them into the graph you want to work on. You no longer need to recreate all of your routing logic, even if you need to copy nodes from a sandbox environment and add them into your production environment. This can help you save more time when building graphs and help you avoid costly mistakes when building out new graphs. 

And if you use Multi-Graph, you’ll be happy to see that you can also copy nodes from a graph in one business unit to a graph in another business unit. Quickly share effective routing logic across your enterprise!

Use Cases:

• Kickstart process changes with familiar logic: Copy the matching and deduplication branch of nodes from an existing graph into a new graph, if you know that the same logic will be used for deduplication and only need to create a new logic for assignments afterwards.
• Migrate logic from Sandbox to Production: Copy a branch of new Assign, Update, and Send Notification nodes that were developed within your Sandbox environment, and paste them into a deployed graph in your Production environment if you like how they worked in your Sandbox. 

Figure: Nodes and edges are copied from first graph

 

Figure: Nodes and edges are pasted into the second graph

 

FlowBuilder Full Screen & Toolbar

Get a better view of your graph in fullscreen! FlowBuilder graphs will now open in a new browser tab to make it easier to both view and edit your process. Existing settings have been reorganized and are now placed in a toolbar at the top of the FlowBuilder page. The additional real estate on screen also paves the way for more exciting features coming this year.

 

Bug Fixes

Our team is continually improving each product to provide you with the very best in-product experience. Please contact support for a list of bug fixes made during this release.