- Matching to Related Lists
- Use Cases
- Get Records Match Node
- Configuring the Related List Fields
- Advanced Settings
- General Decision Node
Related List/Object Based Routing (Get Records) allows you to query any object relevant to the record you are routing in your graph. With Related List/Object routing you can use related lists on the routed record and records you are mapping to, for decisions, actions, and routing. Using the relationship to a related List/Object gives you the ability to query and get records associated with the related List. Related List/Object Based Routing is an advanced feature for admins with the need to access information through related Lists/Objects. Matching to Related Lists/Objects can be found
Example: Kevin is the LeanData Admin for OnPoint Communications. When a Lead is routed, Kevin wants to check the related List of Products. The lead is stamped with the products the Lead is interested in. The products can help determine the correct rep to route the lead.
Please Note: This feature is designed for advanced Salesforce users.
Matching to Related Lists
The most common type of setup and relationship that customers are enacting and executing on, is a related list. Using Related List Based routing enables you to use related lists on the routed record in your Flowbuilder Graphs. This feature is similar to Related Activity or Campaign Member based routing.
Leads in Salesforce typically have a related list such as a list of Activities inside Salesforce. John Smith might have multiple interactions with SDRs during the buying cycle. Those activities get logged under John Smith’s name.
These Activities (a Salesforce Object) have a lookup relationship to John Smith. The ID of John Smith will be stamped on these activities. We currently use the Related Acti
This section gives you several use cases to understand Related List/Object Routing.
Product Interest Based Routing
OnPoint Communications is a large software and hardware vendor. In Salesforce their products are stored on an object called Products. Leads and Opportunities can be stamped with the Product.
John Smith has indicated interest in products A,B, and C. If he expresses interest in another product, he can be routed to the rep that is trained in how to follow-up on his product interest. Related List routing would let us route based on most recent interest.
Enabling Custom Territories
GlobalWorld has a custom Territory object. They could also have a product like Enterprise Territory Management. They stamp the lead with the associated territory. Connected to the Territory is a related list of Territory members like an AE, SDR, and Product Specialist. Related List Routing will help us find the best match on the Related List of Territory Members.
Opportunities, Products, and Buying Groups
In this use case the Related List lives on the Opportunity that we match to instead of the routed Lead. Related List matching supports lists on the routed record but also lists on any other object in a Graph through matching. So we can query the list on the opportunity for products that John might be interested in. This is important to the buying group, because we can determine if John is part of the buying group for this Opportunity’s products or if he should be part of a buying group for a new Opportunity’s set of products. This feature allows us to check a list that lives on a matched object, not just the match object itself.
Several nodes in Flowbuilder are specifically designed to help work with related Lists/Objects.
Get Records Match Node
The Get Records Match Node gives you the tools to match a Lead to a related List/Object. You will find the Get Records Match Node with the other Match Nodes on the Node Selector in your Router Graphs. You can customize the Get Records Match Node as needed. Options include:
- Node Name
- Search Criteria
- Filter Records
- Store Records
- Advanced Settings
By default, the Node Name is set to Match Node. You can change this label to anything you need. We strongly recommend giving this node a meaningful name such as the goal of the Match Node or simply Related List Match. This will help others understand the purpose of the node.
This field is not required but we recommend adding a description to document any customizations made to the node. If someone else needs to take over the management of the flow, the description will help them to understand the goal of the customizations.
Configuring the Related List Fields
There are 3 steps to configuring the node for the Related List Search.
Step 1: Search Criteria
Step 2: Filter Records
Step 3: Store Records
In our example below we will mimic an Opportunity Match to demonstrate how the Get Records Match Node works.
Step 1: Search Criteria
In this section we will describe how to set up your Related List search.
What object are you looking for?
The Search Criteria step first asks you to choose the object you want to access.The picklist will display all of the relevant Salesforce objects that can be queried. Select the desired object.
How do you want to get records?
There are 2 radio buttons under this option: Related List Search and SOQL Search. SOQL Search will be enabled in a future version.
Related List Search
This picklist will include the Routed Lead and Matched Account (L2A Match Node must be in the flow prior to the Get Records Node). You can navigate through the Routed Lead or Matched Account lookup to find the Related List you desire.
If there is an Object that has a related list such as the Matched Account, you will see it displayed twice on the Object picklist. If there is an arrow next to the Object, it means there is a lookup relationship to a different object, and you can follow and select a related list on the next object. Selecting the option with no arrow will confirm that the related list you wish to use lives on the selected object itself. In the example above you can select the Matched Account or navigate lookup relationships on the Matched Account to identify a related list on a different object. The Routed Lead only has the arrow because there is no related Opportunity List on the Lead. The picklists include protection so you cannot select a invalid option.
Step 2: Filter Records
The Filter Records section gives you the tools to Filter for just records that meet specific conditions or exclude records based on specific conditions. You can select no filter if needed.
Step 3: Store Records
The Store Records step gives you the tools to store the records returned in Step 2. Currently, you can select One Record. Our example shows Opportunity as the record to be stored based on choosing Opportunity in Step 1 above. You will be able to select All Records in a future version.
With One Opportunity selected, you will need to provide tiebreakers to enable LeanData to pick the best matched record when multiple matched records are returned. There is a default tiebreaker rule provided. Created Date Max will select the most recent record.
Set Variable to Selected Record
This setting can add the record to an existing Variable or a new Variable that you name. Saving the results of Get Records allows you to use them in other Router Nodes.
To set a Variable:
- To search for a Variable enter the first few letters of the variable name.
- To save a new Variable, enter a new variable name. For new Variables you will see (custom) at the end of the name
- To set the variable, click on its name.
There are 3 exit edges from a Match Node. Under the Advanced settings you can select a target node for each of the edges for what you would like LeanData to do in each of these scenarios.
- Match: LeanData has identified a best match based on the algorithm, after applying your Tiebreakers and Filters.
- No Match: LeanData has not identified a match, after considering your Filters.
- Multiple Matches Identified: If LeanData has more than one match remaining after your Filters, and you would like to take a different action than identify one best match, you can direct this edge to your desired action. This option is disabled by default. Upon enabling, you will also have to remove any Min/Max tiebreakers.
General Decision Node
The General Decision Node has 2 main functions, it allows you to make routing decisions on any Variable in the graph and it can be used to make decisions with Get Records (Related Object/List Routing) results.
Example: Vince is the LeanData admin for Lighthouse Development. He currently needs to create a Graph that will use Get Records to get a Lead’s Product Interest stamped on the Lead. The Graph also needs to make routing decisions based on the Product Interest. Vince uses a General Decision Node to select the Product and route to reps that have the best product knowledge.
Select Items to Compare
In the select items to compare section, you will be setting the items that you want to compare for the decision. You will be able to select the Routed Lead, any matched Objects, or any saved Variable on the left side and the right side.
When you set an Object for Item 1, the node will use the object’s fields for the routing conditions. For example, if you selected a Variable for an Opportunity returned with Get Records, the node will use those fields for the condition.
Configure the conditions as needed.
- Set the field for the Object selected for Item 1.
- Set the Operator to use for comparing the field from Item 1 with the Value/Field of Item 2.
- Select the Value or field from Item 2 to compare to Item 1.
Set the target for the condition.
Related List/Object Based Routing (Get Records) allows you to query any object relevant to the record you are routing in your graph and make routing decisions based on the results. You can store results in Variable to be used in your Router Graph
For questions or additional assistance please contact LeanData Support.