- Object Eligibility
- How to Setup Any Object Routing
- Supported Flowbuilder Nodes
- Match Nodes
- Entry or Trigger Nodes
- Decision Nodes
- Action Nodes
- Track & Report Nodes
- Partner Nodes
- Routing Support
- Troubleshooting Tools
- Reporting Tools
Any Object Routing gives you the ability to use the FlowBuilder interface to create and manage routing logic for any standard or custom Salesforce objects. This will ensure that the objects that are relevant to your organization's specific processes get assigned to the appropriate owner automatically and actioned accordingly.
In addition to assigning these records to the correct owners, Any Object Routing offers you access to other powerful Flowbuilder actions such as notifications and field updates.
You can configure up to 5 objects for Any Object Routing. These objects must fall under one of the following categories:
- Any triggerable custom object in Salesforce
- Any triggerable, sObject type, standard object in Salesforce from API Version 47.0 or prior.
Note: Standard objects released on API Versions 48.0 onwards are not currently supported.
Please ensure you have the proper permissions for each object you wish to configure with Any Object Routing
- Setup > Profiles > Your profile (ex: System Administrator)
- Object Settings
- Select “Object Settings”
- Create/Read/Edit for appropriate object permissions (should have All Access)
- Author APEX
How to Set Up Any Object Routing
Please see the Any Object Routing Setup Guide for detailed, step-by-step instructions on how to enable and set up your instance for Any Object Routing.
Supported FlowBuilder Nodes
Any Object Routing supports object-agnostic LeanData Routing capabilities that are not dependent on specific object characteristics. Below, you will find the FlowBuilder features that can be used in Any Object Routing. Each of these features maintain the same functionality & experience that you are familiar with from the LeanData other supported Router objects.
- Object to Account (Obj2A) Match Node
The Object to Account match node is available for Any Object Routing graphs. The Obj2A node lets you match the routed object to an Account in your Salesforce Organization. It is a little different from other Match Nodes in Flowbuilder. With Any Object Routing you need to specify the Variable Field Mappings between the routed object and the Account. Specify the fields to use to match the routed record to Accounts. While Company is the only required field, mapping additional fields will help improve match results.
The rest of the node works just like an Account Match Node in other routers.
For more information on Account matching please see the Lead to Account Match Node Guide.
Entry or Trigger Nodes
- New Object Entry Node
- Updated Object Entry Node
Your New and Updated Entry nodes will be available for the object you have selected. These will operate in the same manner as the corresponding Trigger Nodes in the other Router objects.
Additional Entry Nodes (such as the Campaign Member Entry Nodes) are not available.
- True-False Decision Node
- True-False Object to Account Decision Node
- Branch Decision Node
- Branch Object to Account Decision Node
- General Branch Node
Both True-False and Branch Decision nodes are available for the selected object. These will operate in the same manner as the corresponding Decision Nodes in the other Router objects. The Object 2 Account (Obj2A) Branch and T/F Decision Nodes are designed to work with the Account Match Node. The General Branch Node is designed to make routing decisions on any Variable in the graph.
- Route Nodes
- Assign Owner
- Route to Matched Account
- Round Robin
- Territory Segment
- Update Field
- Send Notification
- Send Slack Notification
Several Action Nodes are available for the selected object. These will operate in the same manner as the corresponding Action Nodes in the other Router objects. The Route to Matched Account node is available to send your routed object to a matched Account.
For more information, see the following guides:
- Assign Record Node Guide
- Round Robin Node Guide
- Route to Territory Node Guide
- Route to Matched Account
- Update Record Node Guide
- Send Notification Node Guide
Track & Report Nodes
The Hold Until Node is available for Any Object Routing graphs. This node will operate in the same manner as the Hold Until Node in other routers.
For more information see the Hold Until Node & Time to Action Tracker Guide.
Please Note: You will need to create or identify a text field for the Hold Until Node, for it to work with AOR. This field will be used to track and execute the Hold Until Node.There is no restriction on naming of the field but we recommend including LeanData in the naming convention. Then reach out to your Implementation person or CSM to begin using this node.
The Send Slack Notification Node is available for Any Object Routing graphs. This node will operate in the same manner as the Send Slack Notification Node
For more information see the Slack FlowBuilder Integration Guide.
Additional Supported Routing Functionality
In addition to the supported nodes listed above, Any Object Routing also supports the following supplementary functionality.
Round Robin Pools
Round Robin Pools are available for all objects you enable for Any Object Routing. Your routing object will be dynamically added to the Round Robin Pool Menu and the Capping Rules Menu as a selectable Object option.
For more information please refer to the Round Robin Overview Guide.
Territory Management is available for Any Object Routing. You can use the Territory Segments that you have developed for other object Routers, but map them to the corresponding territory fields on your object within the Territory Node:
For more information, please refer to the Territory Management Overview.
People (Schedules & Capping)
Any Object Routing will also support the functions found under the People section of the Dashboard, including Schedules and Capping.
Schedules are object agnostic and the availability of Users will be the same across all objects, according to how nodes or pools are configured to respect these hours.
Capping will give you the option to select which object you are configuring cappings for.
Audit Logs are available for records routed via Any Object Routing. These will be found on their own Audit Logs page by navigating to Routing > Any Object > [Your Object Name] > Audit Logs.
For more information please refer to the Audit Logs Guide.
Routing Insights & Deployment History
Your deployments for your Any Object Configurations will also be captured in the Routing Insights & Deployment History Page. These will be found on their own Audit Logs page by navigating to Routing > Any Object > [Your Object Name] > Routing Insights & Deployment History.
This page will show all your deployments for this particular object and show you metrics related to how these records have been processed.
For more information, please refer to the Routing Insights & Deployment History Guide.
Any Object Routing also supports some reporting tools such as Routing Metrics Mapping and Routing Usage
Routing Metrics Mapping
By navigating to Routing > Any Object > [Your Object Name] > Advanced Settings > Routing Metrics Mapping you can map fields from your routed object to LeanData's Log Object for later reporting.
For more information please see our Routing Metrics Mapping Guide.
The LeanData Dashboard Home Page as well as the more detailed Routing Usage page under Admin > Routing Usage will capture metrics on how records are routed via Any Object Routing. These will be categorized under the "Other" tab in Routing Usage.
For any additional information please contact LeanData Support.