Contents:

• Overview
• Customization
• Fallback Edge
• Working with Rules
• Logic Rules
• Things to Know & Best Practices

 

Overview 

The Branch Decision Node allows you to make branching logic based on the criteria on a routed record or on a record you previously matched using a Match Node. Use a Branch node to determine if a certain condition is met and then determine which path the routed Prospect record should take. This node allows for unlimited outcomes. If you have multiple rules that require more than 2 outcomes (such as geo, industry, company revenue size etc), you must use the Branch decision node.

Example: Bridgette is the LeanData admin for Lighthouse Development and has been tasked to edit their BookIt! Calendar Graph. For their initial deployment the Revenue Operations team decides that they will only route BookIt! Prospects that reside in Canada, Mexico, and the United States of America. All other inquiries will be routed to a special landing page.

 

Customization

When you select a Branch Decision node, you need to determine what object you’re evaluating to see if a condition is met. 

For Calendar Router, you have the following options:

• Prospect: The condition is being evaluated against the incoming Lead that is being processed through the router flow.
• Prospect to Lead (P2L): The condition is being evaluated against a matched Lead from a prior Lead Match Node.
• Prospect to Account (L2A): The condition is being evaluated against a matched Account from a prior Account Match Node.
• Prospect to Opportunity (L2O): The condition is being evaluated against an Opportunity from a prior Opportunity Match Node.
• Duplicate Lead (DupeL): The condition is being evaluated against a potential duplicate Lead from a prior Dupe Lead Match Node.
• Duplicate Contact (DupeC): The condition is being evaluated against a potential duplicate Contact from a prior Dupe Contact Match Node.

After you have selected the type of Branch Decision node, you have a number of options to configure the node.

• Node Name: By default, the Node Name is set to Branch. You can change this label to anything you need. We strongly recommend giving this node a meaningful name such as the subject of the decision. This will help others understand the purpose of the node. For our example, we would call this node, Region Decision.
• Description: 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.
• Rules: The Branch node includes 1 rule by default. You can edit this rule with 1 or more conditions to help route your records. Click on Edit Condition to create logic for this edge. Each rule creates an edge.
• Default Edge: The Default Edge on the Branch node is designed to give your records a path if they do not meet any of the rules/edges of the node. This edge is set to End of Flow by default but you can connect it to another node if needed. 

New Rule: The New Rule option lets you create as many additional rules and conditions as needed for the Branch Logic.

 

Fallback Edge

A new Branch Decision Node includes 2 edges for the decision: a blank edge to edit and the default edge. The default edge is called a fallback edge. This edge is designed to catch all the records processed through the node that do not meet the other rules set on the node. The fallback edge can be set to send the records to another node or to just end the flow. If you set the fallback to end of flow, LeanData will take no further action on the record.

 

Working with Rules

The default rule uses the built in LeanData Logic tools to help you build your Branch node. When you add additional rules you have the option to select SOQL or Logic to build your rules to create branched logic for your Router flow.

 

Rule Type: You have 2 options for building rules in the Branch decision node:

• SOQL: The SOQL (Salesforce Object Query Language) option gives you a box that you can enter custom SOQL queries to search your database. There is also a Description that you can add notes about the SOQL code. Your Implementation Consultant can help you create the appropriate SOQL queries or you can see Salesforce’s help system for more information on SOQL. Using this option is uncommon.

• Logic: The Logic option gives you tools native to LeanData to set up the criteria for the decision of the node.

 

Logic Rules

When you select, Logic Rule for the basis of the Decision Node, you will see tools to help you build the logic behind the decision being applied to the record.

Please Note: Each of the Branch node types have different settings for the conditions. Using the Prospect  Decision Node will show different options from Prospect to Lead Decision Node.

Under the option, Logic Rule, for the Prospect Branch Decision Node,you will find the following:

• Prospect Variable: The Prospect Variable selector will give you a list of all the variables that were mapped on the New Prospect Trigger Node.
• Operator: The Operator gives you a condition to apply to the Prospect Variable for the decision. (Example: Contains, does not contain, starts with, is null, etc).
• Value: The Value is the value you are evaluating against in your Prospect Variable.

Please Note: By default, the conditions will have an error message: Invalid condition. Once you start building your conditions with the mapped Prospect Variables, the error message will disappear.

To Add a Logic Rule to the Decision Node:

1. Click on the Branch Decision Node.
2. Click the pencil icon to the right of the node. The edit window opens on the right side of the page.
3. Click Edit Condition on the default rule or New Rule to create an additional rule as needed. The screen displays the Prospect Variable, Operator, and Value boxes.
4. Select the desired Prospect Variable to apply the decision to. If you start typing the first letters for the desired field such as st for status, you will see the list filter for just fields that have the text combination you entered.
5. Select the desired operator.
6. Enter/select the value you are evaluating against in your selected field.
7. Set other fields as needed.
8. Repeat steps 3-7 as needed for additional rules.
9. Save.

Logic Rules with Matched Records

When working with Matched records such as Prospect to Account, the options you will see depend on the type of node you are configuring. If you are configuring a Prospect to Account Branch Node you will see Matched Account fields in your Logic. If you are configuring a Prospect to Lead, you will see Matched Lead fields.

 

The matched record fields you can access depends on the type of Branch node that you selected and if you have previously matched to a record of the same type. For example, in order to access Matched Account Fields, you need to have previously matched to an account in the Calendar Router Flow and the Branch node type you selected needs to be Prospect to Account. These two factors will configure the node to pick up matched account fields as you can see in the screenshot above. 

Value/Variable

The Value/Variable selector lets you choose between a specific Value to compare like Revenue greater than 10 million. With the Variable option you will be comparing the matched field with a variable field such as Industry Equals Industry. Only records that have the same industry as the Prospect Industry will satisfy this condition.

Please Note: If you select a specific Branch node (Prospect to Account for example) and have not previously matched to the same object type, (Account), you will still be able to configure the node with the matched fields but you will get an error when saving the node configuration.

Working with Multiple Conditions

When you edit or add rules, you can have multiple conditions.  When you have a rule with multiple conditions you are given the option to specify the relationship between the conditions. By default, you will see an AND relationship. You can change this to OR as needed. You can also use parentheses to group conditions together. Example: ((1 AND 2) OR 3).

 

Things to Know & Best Practices

• Use Logic rules rather than SOQL conditions as much as possible.
• If you need only 2 outcomes, you may use a True/False Node instead of a Branch node.
• Change the names of the Labels as needed to help identify certain paths in the flow.
• Change the names of your Nodes so you can easily decipher the condition or criteria going through that node.
• Add descriptions wherever you can.
• You can only use a Decision node that references fields on a matched record if you had previously found a matched record in a corresponding match node.