Contents:
Overview
The Account-to-Opportunity Match Node is used to identify one of the Opportunities under the Account record for use in routing decisions. When an Account enters the node, the node will look at the Opportunities associated with the Account and apply the defined Filters and Tiebreakers to select one of those Opportunities.
Please Note: This match node operates differently than the match nodes within Lead Router. The Account-to-Opportunity Node is only used in the Account Router and only identifies Opportunities under the Account being evaluated.
Example: Tim is the LeanData admin for EdenPoint Development. In his Account Router flow, he needs to identify the most recent active Opportunity on that Account. He configures the A2O Node, with Filters and Tiebreakers to find any active Opportunities under the Account and select the most recently created one. Using the Filters, he ensures that no inactive Opportunities are considered, and he uses Tiebreakers to select the most recently created Opportunity.
Each Match node includes Tiebreakers to select the best record if there is more than 1 possible Opportunity. These Tiebreakers function just like the Tiebreakers in Tagging. The Tiebreakers in the node are local only to the node. Any changes made to the node’s Tiebreakers do not affect the Tagging Tiebreakers or even the Tiebreakers in other match nodes.
Customization
You have a number of options to configure the node.
- Node Name
- Description
- Filter Matched Opportunities
- Prioritize Matched Opportunities
- Set Variable to Matched Opportunity
- Advanced Settings
Node Name
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 Opportunity Match. This will help others understand the purpose of the node.
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.
Filter Matched Opportunities
Use Filters to include or exclude Opportunities based on the conditions you set on the node. In our example, we are excluding Opportunities that are closed won or closed lost. We have set the filter to exclude any Opportunity where the Stage equals Closed Won or Closed Lost to prevent these Opportunities from being considered.
Value/Field
The Value/Field selector lets you choose between filtering for a value in a field on the Opportunity record, and comparing a field on the Opportunity record with a field on the routed Account record.
When using Value, you are looking for a specific value in a field on the Matched Opportunity record. For example, if you wanted to filter out Opportunities that are Closed Won or Closed Lost you would set the Matched Opportunity Field to Stage, set the Operator to Equals, and pick the values Closed Won and Closed Lost from the Value pull-down.
When using Field, you are comparing the value of a field on the Matched Opportunity record with a field on the routed Account record. When this option is selected, you will notice that the label above the last field will change to Account Field.
For example, if you want to Filter out Opportunities owned by the same person that owns the Account record, you can select the field Owner.User ID on the Matched Opportunity field. You then set the Operator to Equals. Lastly, you set the Account Field to Owner.User Id.
For each condition you add, you will see:
- Field: The Field selector will give you a list of all the fields on the Opportunity record that you are filtering.
- Operator: The Operator gives you a condition to apply to the field for the decision. (Example: Contains, does not contain, starts with, is null, etc). The values in the Operator selection change depending on the field selected.
- Value/Field: The Value is the value you are evaluating against in your selected field. This is typically a pull-down menu of possible values. If you select Field for Value/Field, you will see Account Field as the label and the field will be a pull-down of fields on the routed Account record.
You can add as many conditions as needed to create the desired Filters.
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).
Prioritize Matched Opportunities
In the Prioritize Matched Opportunities section you will see a list of rules called Tiebreakers. These rules are applied after filters if there are multiple Opportunities under that Account that remain after your filtering rules. Tiebreaker rules are processed from the top down and are used to narrow the pool of remaining Opportunities down to the one that best fits your criteria. The node will check each rule, one at a time, from top to bottom, until only one Opportunity remains. This is the Opportunity that will be referenced in any routing decisions.
The Account-to-Opportunity node includes a set of default Tiebreaker rules. You can:
- Edit the existing rules
- Add/remove rules
- Change the order of the rules
Editing a Rule
To edit a rule, simply click in the rule to open it for editing. You will see the same options as in the Filters.
Adding a Rule
If you choose to add a custom Tie-Breaker Prioritization Rule, click New Rule. There are three rule types; LOGIC, SOQL, MIN MAX.
LOGIC - When configuring a new logic rule, you can use a Field or Field Value from the matched Opportunity level. This works the same as adding FiltersSOQL - You can use a SOQL (Salesforce Object Query Language) string here. More on SOQL.
MIN MAX - The field you are choosing is the Opportunity level field. Set the Operator to either Min or Max. Min meaning the lowest possible value and max being the highest. For Date and Time fields, Min equals the oldest date and Max equals the newest date. When applied to time MIN is the oldest time and MAX is the most recent or further into the future.
Example: Mel the LeanData Admin wants to build a tiebreaker rule that will look for the Opportunity with the Min (oldest) created Date. She sets the Opportunity Created Date to MIN to ensure the tiebreaker looks for the oldest Opportunity that matches.
Advanced Settings
Under Advanced Settings there are options for setting the targets for the node edges.
Node Edges
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.
Summary
The Account-to-Opportunity node is used to identify one Opportunity under the routed Account for routing decisions. Using configurable filters and Tiebreakers, the node will select the best Opportunity under the routed Account. Accounts will exit the node with either 1 Opportunity identified or none.
For more information on working with Account Router flows please see our Account Routing Guide:
https://leandatahelp.zendesk.com/hc/en-us/articles/360018933094-Routing-Account-Router-Guide