--- sourceDocument: Yokohama Customer Service Management sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/customer-service-management Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama Customer Service Management ft:clusterId : - csm bundleId : - csm workflow : - Customer and Industry --- # Editing decision trees in Core UI # Editing decision trees in Core UI {#ariaid-title1} Release version: Yokohama Updated January 30, 2025 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 This content guides ServiceNow customers on how to edit existing decision trees within the Core UI to enhance or extend troubleshooting workflows. It highlights that while creation of new decision trees is no longer supported in Core UI (users should use Decision Tree Builder for new creations), editing and extending current decision trees remains possible. Show full answer Show less ## Editing Decision Trees Workflow The editing process involves configuring various nodes and paths within the decision tree to guide users through questions, decisions, guidance, and linking to other decision trees. Key steps include: * **Start Node and Task Input:** Each tree has a start node (decision type) and a task input that references the record the agent is working on. * **Adding Questions:** Inputs are created to pose initial questions to customers, with configurable answer types. * **Decision Paths:** Paths with conditions determine which decision node is next based on user answers; decision nodes generate automatically. * **Guidance Paths:** Conditions lead to guidance nodes providing resolutions; these nodes are created automatically and configured with appropriate guidance and inputs. * **Linking Paths:** Paths that connect to other decision trees, enabling complex workflows; linking nodes are created and configured to connect trees. * **Next Node Configuration:** You can add decision nodes after guidance nodes but not another guidance node directly. Linking nodes can follow decision nodes. * **Input Mapping:** Inputs can be mapped from one node to another to reuse answers, improving efficiency and consistency across the tree. The Pill-picker icon facilitates passing inputs to guidance nodes. ## Practical Tips * Use the Preview icon next to the Decision Tree field to quickly return to the full decision tree view from any node. * All created nodes appear in the related list for easy management. * Remember to use Decision Tree Builder for creating new decision trees, as Core UI supports only editing existing ones. This approach enables ServiceNow customers to maintain and improve their troubleshooting decision trees effectively within the Core UI, ensuring clear guidance and streamlined user interactions. 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](https://servicenow-prod.fluidtopics.net/rfe2qqSLpM~2peX5_w8avw "Configure decision trees using the no-code visual Decision Tree Builder, which provides a canvas for a diagrammatic representation of nodes and their paths in a troubleshooting process."). Figure 1. Decision tree configuration flow in Core UI The following table provides high-level information for editing a decision tree in the Core UI. {#decision-trees__table_hxd_yc1_3xb__entry__2} | 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](https://servicenow-prod.fluidtopics.net/OfAyI0hDQXn~uht1aEmRLw "Edit a decision tree that you created using Core UI to improve or extend a troubleshooting process."). 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](https://servicenow-prod.fluidtopics.net/Ae5XDr~GH_iBxXkn0dTbKA "Create decision inputs for each decision node. Decision inputs appear in the form of questions in a workspace for service agents to answer."). | | 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](https://servicenow-prod.fluidtopics.net/N5uIOt73v8LeSu16ZE_3IQ "Create a path to set conditions and priority order for 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](https://servicenow-prod.fluidtopics.net/Ae5XDr~GH_iBxXkn0dTbKA "Create decision inputs for each decision node. Decision inputs appear in the form of questions in a workspace for service agents to answer."). | | 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](https://servicenow-prod.fluidtopics.net/N5uIOt73v8LeSu16ZE_3IQ "Create a path to set conditions and priority order for 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](https://servicenow-prod.fluidtopics.net/Mo1aOB6MUuSGdA64QaG_GQ "Associate a guidance to a guidance node so that service agents can act to resolve or escalate a customer issue."). | | 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](https://servicenow-prod.fluidtopics.net/N5uIOt73v8LeSu16ZE_3IQ "Create a path to set conditions and priority order for 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](https://servicenow-prod.fluidtopics.net/m~Vuz42uxJBhrem5y9Z9gA "Nest and invoke decision trees from linking nodes when specific conditions are met. Use guidance output and nested trees to execute complex troubleshooting."). | | 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. {#decision-trees__ul_y2y_nkl_vwb} For more information, see [Add a next node after a guidance node](https://servicenow-prod.fluidtopics.net/xHKU6A7aV4HYOZpuHlveMQ "Add a next node that is a decision node after a guidance node. If a next node is configured, the execution of the decision tree continues after the agent performs the guidance and the guidance history is marked as complete."). | | 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](https://servicenow-prod.fluidtopics.net/06Gbx9MBm0Pm6gRqJxjg5w "Create input mapping to reuse answers from prior nodes. For example, in a decision tree that deals with loan application, you can reuse the input related to the customer’s salary at multiple decision points to determine the loan eligibility."). | [Table 1. Decision tree configuration steps] {#decision-trees__table_hxd_yc1_3xb} 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.