Do you want to re-use the same notification text in multiple action nodes, but don’t want to edit each of them every time the text changes? Here is a way you can use variables to create and manage notification snippets throughout your graph.
Have you ever needed to provide reporting on how many records passed through certain points of your Routing Graph? If you need this information in a native Salesforce report, here is how you can set up your LeanData graph to capture that data in an easily reportable way.
Learn how to prioritize urgent records in your CRM by offloading less time-sensitive records to a recurring routing job. This ensures that urgent records are processed quickly, while less critical records are still assigned.
Getting started with LeanData routing is easy whether you already know what you want or you are looking for some ideas. LeanData’s provided routing templates are a great way to get started quickly.
LeanData is great for updating records, but what if you need a way to remember and reference what a value was before LeanData updated it? Here is a way to reference pre-routing values in notifications.
If your organization uses many complex criteria for routing, you may end up with a visually cluttered graph. Here’s how to set up a Data Table in LeanData to consolidate many different decisions and actions into a single node.
At some point in your routing graphs, you may need to reference the specific entry edge through which a record entered the graph. Here is one way that you can store the entry edge of a record so that you can use it in a later routing decision.
Combine LeanData's matching capabilities and FlowBuilder interface with the fine-grained merging capabilities of Cloudingo using the Cloudingo Merge Lead Integration Node in FlowBuilder. Here’s one example of merging two leads with different preferences for different fields.
Sometimes when you're using both LeanData Tagging and Routing, you may notice that LeanData routes to a different Account than it is tagged with. Here is a way to prioritize the Account Match stored in the Reporting Matched Account field.
When using Round Robins, sometimes you actually want to assign two different User fields with the Round Robin. Here is how to do that, whether you want to assign to the same User or to different Users within the same Round Robin Pool.
Sometimes you are uploading a large list or making some bulk changes to records, and you want to skip or bypass LeanData routing for these records. Here is a way to exclude these records from LeanData Routing without affecting routing for other records.
If you use multi-select picklists, you might want to use something like the “contains” operator to look for one of several different values in a field. Even though there isn’t a contains operator , here are two ways you can set up your nodes to look for a one out of several options in a multi-select picklist.