<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">

 
 
  <channel>
    <title>Decision Tree on ServiceNow Developer Blog</title>
    <link>https://developer.servicenow.com/blog.do?p=/tags/decision-tree/</link>
    <description>Recent content in Decision Tree on ServiceNow Developer Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 04 Feb 2019 09:00:00 -0400</lastBuildDate>
    
        
        
         
        <atom:link href="https://developer.servicenow.com/blog.do?p=/tags/decision-tree/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>New For Developers in Madrid: Decision Tables</title>
      <link>https://developer.servicenow.com/blog.do?p=/post/decisiontrees/</link>
      <pubDate>Mon, 04 Feb 2019 09:00:00 -0400</pubDate>
      
      <guid>https://developer.servicenow.com/blog.do?p=/post/decisiontrees/</guid>
      <description>Decision Tables The first feature in Madrid I am going to highlight is Decision Tables. These decision tables are a place to store the decision logic for variable situations. Each decision table record (sys_decision) handles a single decision. Related lists are the decision inputs (sys_decision_input) and decision (sys_decision_question) records. Each decision record contains an answer.

Our example will be for routing after hours service calls. We take multiple inputs in the form of location, time of submission, and the service.</description>
    </item>
    
  </channel>
</rss>