Linking inputs in decision tree nodes
Summarize
Summary of Linking inputs in decision tree nodes
Linking inputs in decision tree nodes allows authors to reuse input values from previous nodes, enhancing efficiency by eliminating unnecessary questions for agents. When an input is linked, the corresponding question does not appear, as the answer is automatically filled during runtime based on prior inputs.
Show less
Key Features
- Linking Inputs in Question Nodes: Enables reuse of answers to avoid reprompting agents. For example, a credit card number asked previously can be reused without showing the question again.
- Linking Inputs in Guidance Nodes: Facilitates the transfer of customer-provided information into guidance inputs. For instance, linking the task input in the start node allows the agent to access necessary case information seamlessly.
- Special Cases for Linking Inputs: Allows linking inputs of different types under certain conditions, broadening the scope of usability.
Key Outcomes
- Improved agent efficiency by minimizing repetitive questions and streamlining the decision-making process.
- Enhanced data accuracy by automatically populating inputs based on previous answers.
- Flexibility in input linking through various supported field types, enabling more complex decision trees.
Linking of inputs enables decision tree authors to reuse input values (answers) from prior nodes.
Linking inputs in question and linking nodes
Most questions are presented to an agent to provide answers. When you link an input to another input, the question is not displayed to the agent. Because the input reuses values from the input it is linked to, the agent does not need to provide any answer.
Similar to other inputs, you can use linked inputs to create path conditions.
For example, if you have already asked the credit card number in the start node, you can reuse that input in the following question node. This question is not presented to the agent again and the value is automatically filled out during run time.
Linking inputs in guidance nodes
With linking inputs, you can reuse the answers that customer provided to supply input values to the guidance inputs. You can link the task input in the start node to the guidance inputs to pass the information about the record that the agent is working on.
For example, you can connect the start node’s task input to the following guidance. The task input holds a reference of the record the agent is working on in a workspace. You need a case number, which is provided by the task input, for reassigning the case to someone else.
Special cases for linking inputs
In most cases, you can only link inputs to other prior node’s inputs of the same type. For example, you can link a string input field type to another string input field type.
| Input type | Description |
|---|---|
| String input field type | Accepts any type of field to be linked. For example, string accepts integer, decimal, choice, and others. String is a text field which accepts any characters. |
| Reference input field type | Accepts only reference type of field. You can link reference input types only if the current question node’s input table matches the prior node’s input table at the same level or at the child level. For example, the Task table can be linked to the Task table or the Task table can be linked to the Case table, which is a child of the Task table. |
| Choice input field type | Accepts choice type and string type because a choice in a choice list is a string. |
| Date and Date/Time input field types | Accepts the following types:
|
glide_var type fields to map to any inputs.