Editing decision trees in Core UI

  • Release version: Xanadu
  • Updated August 1, 2024
  • 3 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Editing decision trees in Core UI

    ServiceNow customers can edit existing decision trees within the Core UI to enhance or expand troubleshooting workflows. While creation of new decision trees in Core UI is no longer supported, editing and extending existing ones remains possible. For new decision tree creation, customers should use the Decision Tree Builder.

    Show full answer Show less

    Key Features

    • Start Node and Task Input: Each decision tree starts with a decision node and associated task input that references the record being handled. This forms the entry point for the troubleshooting process.
    • Adding Questions (Inputs): Customers can add questions or instructions as inputs to nodes. Each input requires selecting an answer type and configuring possible answers, enabling interactive decision paths.
    • Decision Paths: Define conditions based on answers to direct users to subsequent decision nodes automatically created in the process. This structures the flow of troubleshooting decisions.
    • Guidance Paths: Establish paths leading to guidance nodes that provide resolutions to customers. Guidance nodes are configured by associating guidance content and input parameters.
    • Linking Paths: Create paths to link one decision tree to another, allowing complex troubleshooting flows across multiple decision trees with linking nodes.
    • Next Node Configuration: Add subsequent decision nodes after existing ones to extend the tree; however, guidance nodes cannot follow another guidance node directly without an intermediate decision node.
    • Input Mapping: Reuse answers across nodes by mapping inputs from a source node/input to a destination input, simplifying data flow and avoiding redundant questions.
    • Navigation: Easily return to the overall decision tree view from any node using the Preview icon, allowing quick access to all configured nodes.

    Practical Use and Benefits

    Editing decision trees in Core UI enables customers to refine existing troubleshooting guides without rebuilding them from scratch, ensuring knowledge and processes stay current. The structured approach to defining decision, guidance, and linking nodes supports complex logic and multi-tree workflows. Input mapping improves efficiency by reusing customer responses, enhancing agent experience. Customers can expect improved troubleshooting accuracy and streamlined resolution delivery by maintaining and expanding their decision trees effectively within the Core UI environment.

    You can edit decision trees created in Core UI to improve or extend a troubleshooting process.

    Note:
    You can edit or extend existing decision trees in the Core UI but you can no longer create them. Use Decision Tree Builder to create new decision trees. For more information, see Configuring decision trees in Decision Tree Builder.
    Figure 1. Decision tree configuration flow in Core UI
    Decision tree configuration flow.

    The following table provides high-level information for editing a decision tree in the Core UI.

    Table 1. Decision tree configuration steps
    Decision tree step Description
    Configure a start node and a task input Each decision tree includes a start node of type decision and a task input. The task input stores a reference of the record that the agent is working on. For more information, see Edit a decision tree.

    Select the start node from the Decision Tree Nodes related list. Create inputs to add initial questions you want to ask customers. Select the input type for the expected answer and configure the answers in the related list. For more information, see Add questions or instructions to a decision input.
    Create a decision path Create a decision path and configure conditions for the next decision node. For example, you can set up a condition to select an answer for the question in the start node. When a user selects this answer, this path that leads to a decision node is taken. For more information, see Determine the next node in a decision tree.

    A decision node is automatically created.
    Create inputs to add follow-up questions in the decision node Select the input type for the expected answer and configure the answers in the related list. For more information, see Add questions or instructions to a decision input.
    Create a guidance path Create a guidance path and configure conditions for the next guidance node. For example, you can set up a condition to select an answer for the question in the start node or decision node. When a user selects that answer, this path leads to a guidance node. For more information, see Determine the next node in a decision tree.

    A guidance node is automatically created.
    Configure the created guidance node Configure the guidance node to provide resolution to a customer. Associate a guidance to the guidance node and configure the guidance inputs. For more information, see Provide actions to agents in a decision tree.
    Create a linking path Create a linking path and configure conditions for the next decision tree. For example, you can set up a condition to select an answer for the question in the decision node. When a user selects that answer, this path leads to the next decision tree. For more information, see Determine the next node in a decision tree.

    A linking node is automatically created.
    Configure the created linking node Configure the linking node to link another decision tree to this decision tree. For more information, see Link another decision tree to this decision tree.
    Configure a next node

    Configure a next node that is a decision node.

    Note:
    You can't add another guidance node after a guidance node.
    • You can add an intermediate decision node to add another guidance node.
    • You can configure a linking node after this decision node to link another decision tree.

    For more information, see Add a next node after a guidance node.
    Map inputs from one node to another Map inputs from one node to another to reuse answers by selecting a source node and a source input and a destination input.

    In the guidance node, you can pass inputs from the prior nodes to the guidance inputs by using the Pill-picker icon (Pill-picker icon) to reuse answers.

    For more information, see Reuse answers at decision points.
    Note:
    To go back to your decision tree from any node, select the Preview this record icon (Preview this record icon) next to the Decision Tree field and then select Open Record. You can see all the nodes that you created in the related list.