Introduction to RASON
About RASON Models and the RASON Server
Rason Subscriptions
Rason Web IDE
Creating and Running a Decision Flow
Defining Your Optimization Model
Defining Your Simulation Model
Performing Sensitivity Analysis
Defining Your Stochastic Optimization Model
Defining Your Data Science Model
Defining Custom Types
Defining Custom Functions
Defining Your Decision Table
Defining Contexts
Using the REST API
REST API Quick Call Endpoints
REST API Endpoints
Decision Flow REST API Endpoints
OData Endpoints
OData Service for Decision Flows
Creating Your Own Application
Using Arrays, For, Loops and Tables
Organization Accounts

"Hit Policy: Unique" using tblPolicyUnique

According to the Unique Hit Policy, only one rule may be returned. If multiple rules are successful and multiple results are collected, an error will be returned.

This table takes two inputs, age and medHistory and returns two outputs, riskRating and rule.


{decisionTables: {
   "tblPolicyUnique": {
   	 inputs: ["age", "medHistory"], 
   	 outputs: ["riskRating", "rule"],
   	 hitPolicy: "U", 
   	 rules: [
		  [">60,<25", "good", "medium", "r1"], 
		  [">60", "bad", "high", "r2"], 
		  ["[25..60]", "-", "medium", "r3"], 
		  ["<25", "bad", "medium", "r4"]
	   ]
   }
 },
 formulas: {
    "Unique": { formula: "tblPolicyUnique(,,54, 'good')",    finalValue: [] }
 }
}

In this example, given an age of 54 and a "good" medical history, a "medium" risk rating is returned by rule 3.

"Unique": { "value": [ ["medium", "r3"] ] }

Back to Decision Table Hit Policy: Rule Order