Branched nodes in a workflow

• US 10,708,388 B2
• Filed: 12/21/2018
• Issued: 07/07/2020
• Est. Priority Date: 09/21/2018
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Hsu, Stephen, Kashyap, Ashwin, Funk, Cassandra, Knell, Laurel, Berg, Eric, Long, Martin Edward, Arora, Avital, Lemon, Stanley, Gray, William Victor, Waligora, Philip Alexander, Parekh, Reena, Skibble, Kyle Coleman
• Primary Examiner(s): Nguyen, Quang N
• Application Number:
  US16/229,920
• Publication Number:
  US 20200099771A1
• Time in Patent Office: 564 Days
• Field of Search: 709203, 709205, 709206, 709217, 709219, 709223, 709224, 709226, 709228, 709230, 709232, 709238, 703 7, 717174, 719313
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 67/288 Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
• CPC Class Codes: H04L 67/561 Adding application-functional data or data for application control, e.g. adding metadata
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context

Abstract

Methods, systems, and devices for defining an action node series at a database system are described. In some examples, the workflow may include one or more nodes are associated with an action. When executed, the workflow may produce an outcome based on the occurrence of an event or parameter associated with the one or more nodes. In some examples, the workflow may include one or more branch nodes. A branch node may include logic such that, when the workflow is executed, the logic selects a particular workflow path that includes its own specific nodes. The path may be selected based on the occurrence of an event or a value of one or more parameters. Thus, when a workflow including one or more branch nodes is executed, the outcome of the workflow may be based on the occurrence of the event or the value of the parameter.

Claims

1. A method for defining an action node series at a database system, comprising:

assigning a plurality of nodes to the action node series, wherein each node of the action node series corresponds to an action and a set of metadata associated with the action;

defining at least one node of the action node series as a branch node, wherein the branch node defines a plurality of branches that each includes a subset of nodes, and wherein each node of the subset comprises at least one different action, at least one different set of metadata associated with a same action, or both, and wherein the branch node includes programmed logic for selecting a branch of the action node series based at least in part on an occurrence of an event, a value of a parameter, or both;

receiving information indicative of the occurrence of the event or the value of the parameter from a system that is separate from the database system;

executing the action node series on the database system, wherein an outcome of the action node series is based at least in part on the occurrence of the event or the value of the parameter; and

executing the action node series for a plurality of occurrences, wherein the action node series proceeds along a branch of the plurality of branches for a first subset of the plurality of occurrences, and wherein the action node series proceeds along a second branch of the plurality of branches for a second subset of the plurality of occurrences.

2. The method of claim 1, further comprising:

determining a relationship between an outcome set of the first and second subsets of the plurality of occurrences and the first and second branches of the plurality of branches.

3. The method of claim 2, further comprising:

recommending either the first branch or the second branch to a user of the action node series based at least part on the determining.

4. The method of claim 1, wherein the programmed logic is configured for declarative programming.

5. The method of claim 1, wherein the action comprises making a phone call, sending an electronic message, waiting a predetermined amount of time, exiting the action node series, or a combination thereof.

6. The method of claim 1, wherein the set of metadata associated with the action comprises an identity of a person associated with the action, contact information associated with the person associated with the action, a template of text associated with the action, a duration associated with the action, or a combination thereof.

7. The method of claim 1, wherein the occurrence of the event comprises whether a phone call was returned, whether an electronic message was returned, whether a user engaged with electronic customer material, or a combination thereof.

8. The method of claim 1, wherein the at least one different action associated with the nodes corresponding to each of the plurality of branches is configurable.

9. The method of claim 8, wherein the at least one different action is configurable based at least in part on a portion of the action node series on the database system being executed.

10. An apparatus for defining an action node series at a database system, comprising:

a processor, memory in electronic communication with the processor; and

instructions stored in the memory and executable by the processor to cause the apparatus to;

assign a plurality of nodes to the action node series, wherein each node of the action node series corresponds to an action and a set of metadata associated with the action;

define at least one node of the action node series as a branch node, wherein the branch node defines a plurality of branches that each includes a subset of nodes, and wherein each node of the subset comprises at least one different action, at least one different set of metadata associated with a same action, or both, and wherein the branch node includes programmed logic for selecting a branch of the action node series based at least in part on an occurrence of an event, a value of a parameter, or both;

receive information indicative of the occurrence of the event or the value of the parameter from a system that is separate from the database system;

execute the action node series on the database system, wherein an outcome at the action node series is based at least in part on the occurrence of the event or the value of the parameter; and

execute the action node series for a plurality of occurrences, wherein the subset of the plurality of occurrences, and wherein the action node series proceeds plurality of occurrences.

11. The apparatus of claim 10, wherein the instructions are further executable by the processor to cause the apparatus to:

determine a relationship between an outcome set of the first and second subsets at the plurality of occurrences and the first and second branches of the plurality of branches.

12. The apparatus of claim 11, wherein the instructions are further executable by the processor to cause the apparatus to:

recommend either the first branch or the second branch to a user of the action node series based at least part on the determining.

13. The apparatus of claim 10, wherein the programmed logic is configured for declarative programming.

14. The apparatus of claim 10, wherein the action comprises making a phone call, sending an electronic message, waiting a predetermined amount of time, exiting the action node series, or a combination thereof.

15. The apparatus of claim 10, wherein the set of metadata associated with the action comprises an identity of a person associated with the action, contact information associated with the person associated with the action, a template of text associated with the action, a duration associated with the action, or a combination thereof.

16. A non-transitory computer-readable medium storing code for defining an action node series at a database system, the code comprising instructions executable by a processor to:

assign a plurality of nodes to the action node series, wherein each node of the action node series corresponds to an action and a set of metadata associated with the action;

define at least one node of the action node series as a branch node, wherein the branch node defines a plurality of branches that each includes a subset of nodes, and wherein each node of the subset comprises at least one different action, at least one different set of metadata associated with a same action, or both, and wherein the branch node includes programmed logic for selecting a branch of the action node series based at least in part on an occurrence of an event, a value of a parameter, or both;

receive information indicative of the occurrence of the event or the value of the parameter from a system that is separate from the database system;

execute the action node series on the database system, wherein an outcome of the action node series is based at least in part on the occurrence of the event or the value of the parameter; and

execute the action node series for a plurality of occurrences, wherein the action node series proceeds along a branch of the plurality of branches for a first subset of the plurality of occurrences, and wherein the action node series proceeds along a second branch of the plurality of branches for a second subset of the plurality of occurrences.