@frontlinesystems/rason-mcp-server 2026.5.1 → 2026.5.2

package/examples/calculation/DMNExamples/FEEL Some or Every example.json

@@ -1,66 +1,66 @@
-{
-  "modelName": "FEEL_Some_or_Every_example",
-  "comment": "Example of 'Some/Every' iteration in FEEL",
-  "modelType": "calculation",
-  "typeDefs": {
-    "tLoan": {
-      "components": {
-        "principal": {
-          "type": "number",
-          "allowedValues": [ ">0" ]
-        },
-        "rate": {
-          "type": "number",
-          "allowedValues": [ "[0..1]" ]
-        },
-        "termMonths": {
-          "type": "number",
-          "allowedValues": [ ">0" ]
-        }
-      },
-      "language": "Feel"
-    },
-    "tLoanList": {
-      "language": "Feel",
-      "typeRef": "tLoan",
-      "isCollection": true
-    }
-  },
-  "boxFunctions": {
-    "funPMT": {
-      "inputs": [ "loan" ],
-      "inputTypes": [ "tLoan" ],
-      "language": "Feel",
-      "resultType": "number",
-      "body": {
-        "payment": {
-          "formula": "(loan.principal*loan.rate/12) / (1 - (1 + loan.rate/12)**-loan.termMonths)"
-        },
-        "fee": {
-          "formula": "0.01 * payment"
-        }
-      },
-      "result": "payment + fee"
-    }
-  },
-  "data": {
-    "loans": {
-      "type": "tLoanList",
-      "value": [
-        [ 600000, 0.0375, 360 ],
-        [ 100000, 0.0375, 360 ]
-      ],
-      "binding": "get"
-    }
-  },
-  "formulas": {
-    "MonthlyPayment": {
-      "feelFormula": "for i in loans return funPMT(i)",
-      "finalValue": []
-    },
-    "LoanAcceptable": {
-      "feelFormula": "if (every i in MonthlyPayment satisfies i < 2000) then 'accept' else 'reject'",
-      "finalValue": []
-    }
-  }
+{
+  "modelName": "FEEL_Some_or_Every_example",
+  "comment": "Example of 'Some/Every' iteration in FEEL",
+  "modelType": "calculation",
+  "typeDefs": {
+    "tLoan": {
+      "components": {
+        "principal": {
+          "type": "number",
+          "allowedValues": [ ">0" ]
+        },
+        "rate": {
+          "type": "number",
+          "allowedValues": [ "[0..1]" ]
+        },
+        "termMonths": {
+          "type": "number",
+          "allowedValues": [ ">0" ]
+        }
+      },
+      "language": "Feel"
+    },
+    "tLoanList": {
+      "language": "Feel",
+      "typeRef": "tLoan",
+      "isCollection": true
+    }
+  },
+  "boxFunctions": {
+    "funPMT": {
+      "inputs": [ "loan" ],
+      "inputTypes": [ "tLoan" ],
+      "language": "Feel",
+      "resultType": "number",
+      "body": {
+        "payment": {
+          "formula": "(loan.principal*loan.rate/12) / (1 - (1 + loan.rate/12)**-loan.termMonths)"
+        },
+        "fee": {
+          "formula": "0.01 * payment"
+        }
+      },
+      "result": "payment + fee"
+    }
+  },
+  "data": {
+    "loans": {
+      "type": "tLoanList",
+      "value": [
+        [ 600000, 0.0375, 360 ],
+        [ 100000, 0.0375, 360 ]
+      ],
+      "binding": "get"
+    }
+  },
+  "formulas": {
+    "MonthlyPayment": {
+      "feelFormula": "for i in loans return funPMT(i)",
+      "finalValue": []
+    },
+    "LoanAcceptable": {
+      "feelFormula": "if (every i in MonthlyPayment satisfies i < 2000) then 'accept' else 'reject'",
+      "finalValue": []
+    }
+  }
 }

package/examples/calculation/DecisionTables/DT Datasource example.json

@@ -1,53 +1,53 @@
-{
-  "modelName": "DTDatasourceExample",
-  "comment": "Decision table inputs from a datasource: This RASON decision table example illustrates how to provide an outside data source. Decision Tables contain a set of rules which specify actions to perform based on specific conditions.  Decision tables are a good tool to use when there is a consistent number of rules, or conditions, to be evaluated followed by a specific set of actions to be performed once a rule, or condition, is met. In this example, the customer data is supplied in the DT Customers.txt CSV file. The decisiont table in this example generates a medical rating for a patient based on the age of the patient and his/her medical history.",
-  "modelType": "calculation",
-  "datasources": {
-    "comment": "Specify outside data sources within the 'datasources' section of a RASON model.",
-    "cust_data": {
-      "comment": "The CSV file, DT Customers.txt contains the input parameters for the decision table, PolicyUnique.",
-      "type": "csv",
-      "connection": "DT Customers.txt",
-      "selection": "",
-      "indexCols": [ "custID" ],
-      "valueCols": [ "custAge", "medHistory" ],
-      "direction": "import"
-    }
-  },
-  "data": {
-    "comment": "The input parameters, custAge and medHistory, are bound to the age and med variables within the data section.",
-    "age": {
-      "comment": "The input parameter custAge from the DT Customers.txt CSV file is bound to the age variable.",
-      "binding": "cust_data",
-      "valueCol": "custAge"
-    },
-    "med": {
-      "comment": "The input parameter medHistory from the DT Customers.txt CSV file is bound to the med variable.",
-      "binding": "cust_data",
-      "valueCol": "medHistory"
-    }
-  },
-  "decisionTables": {
-    "comment": "Decision tables are created within the decisionTable section in a RASON model. In this example, there is 1 decision table, the PolicyUnique decision table.",
-    "PolicyUnique": {
-      "comment": "In this decision table, the input and output parameters are passed using the 'inputs' and 'outputs' properties, respectively.  It's possible to provide types for the inputs and outputs, see the DTDateTimeExample. The decision table rules appear under 'rules'.  The hit policy must be specified using 'hitPolicy'.",
-      "inputs": [ "age", "medHistory" ],
-      "outputs": [ "riskRating", "rule" ],
-      "rules": [
-        [ ">60,<25", "good", "medium", "r1" ],
-        [ ">60", "bad", "high", "r2" ],
-        [ "[25..60]", "-", "medium", "r3" ],
-        [ "<25", "good", "low", "r4" ],
-        [ "<25", "bad", "medium", "r5" ]
-      ],
-      "hitPolicy": "U"
-    }
-  },
-  "formulas": {
-    "comment": "The decision table is called and calculated within the formulas section. The res function calls the PolicyUnique decision table with two inputs, age, and med.  Both input parameters are supplied through the DT Customers.txt CSV file. The result of the decision table will be returned in the result. ",
-    "res": {
-      "formula": "PolicyUnique(,,age[1], med[1])",
-      "finalValue": []
-    }
-  }
+{
+  "modelName": "DTDatasourceExample",
+  "comment": "Decision table inputs from a datasource: This RASON decision table example illustrates how to provide an outside data source. Decision Tables contain a set of rules which specify actions to perform based on specific conditions.  Decision tables are a good tool to use when there is a consistent number of rules, or conditions, to be evaluated followed by a specific set of actions to be performed once a rule, or condition, is met. In this example, the customer data is supplied in the DT Customers.txt CSV file. The decisiont table in this example generates a medical rating for a patient based on the age of the patient and his/her medical history.",
+  "modelType": "calculation",
+  "datasources": {
+    "comment": "Specify outside data sources within the 'datasources' section of a RASON model.",
+    "cust_data": {
+      "comment": "The CSV file, DT Customers.txt contains the input parameters for the decision table, PolicyUnique.",
+      "type": "csv",
+      "connection": "DT Customers.txt",
+      "selection": "",
+      "indexCols": [ "custID" ],
+      "valueCols": [ "custAge", "medHistory" ],
+      "direction": "import"
+    }
+  },
+  "data": {
+    "comment": "The input parameters, custAge and medHistory, are bound to the age and med variables within the data section.",
+    "age": {
+      "comment": "The input parameter custAge from the DT Customers.txt CSV file is bound to the age variable.",
+      "binding": "cust_data",
+      "valueCol": "custAge"
+    },
+    "med": {
+      "comment": "The input parameter medHistory from the DT Customers.txt CSV file is bound to the med variable.",
+      "binding": "cust_data",
+      "valueCol": "medHistory"
+    }
+  },
+  "decisionTables": {
+    "comment": "Decision tables are created within the decisionTable section in a RASON model. In this example, there is 1 decision table, the PolicyUnique decision table.",
+    "PolicyUnique": {
+      "comment": "In this decision table, the input and output parameters are passed using the 'inputs' and 'outputs' properties, respectively.  It's possible to provide types for the inputs and outputs, see the DTDateTimeExample. The decision table rules appear under 'rules'.  The hit policy must be specified using 'hitPolicy'.",
+      "inputs": [ "age", "medHistory" ],
+      "outputs": [ "riskRating", "rule" ],
+      "rules": [
+        [ ">60,<25", "good", "medium", "r1" ],
+        [ ">60", "bad", "high", "r2" ],
+        [ "[25..60]", "-", "medium", "r3" ],
+        [ "<25", "good", "low", "r4" ],
+        [ "<25", "bad", "medium", "r5" ]
+      ],
+      "hitPolicy": "U"
+    }
+  },
+  "formulas": {
+    "comment": "The decision table is called and calculated within the formulas section. The res function calls the PolicyUnique decision table with two inputs, age, and med.  Both input parameters are supplied through the DT Customers.txt CSV file. The result of the decision table will be returned in the result. ",
+    "res": {
+      "formula": "PolicyUnique(,,age[1], med[1])",
+      "finalValue": []
+    }
+  }
 }

package/examples/calculation/DecisionTables/DT Date and Time examples.json

@@ -1,92 +1,92 @@
-{
-  "modelName": "DTDateTimeExample",
-  "modelType": "calculation",
-  "modelDescription": "RASON Date and Time Decision Table Examples: Decision Tables contain a set of rules which specify actions to perform based on specific conditions.  Decision tables are a good tool to use when there is a consistent number of rules, or conditions, to be evaluated followed by a specific set of actions to be perfrmed once a rule, or condition, is met. This example contains 3 decision tables, tblRiskRating, tblTollTax and tblParkingFee.",
-  "decisionTables": {
-    "comment": "Decision tables are created within the decisionTable section in a RASON model. In this example, there are 3 decision tables, tblRiskRating, tblTollTax and tblParkingFee",
-    "tblRiskRating": {
-      "comment": "This decision table generates a predicted medical rating based on the age of a patient and his/her's medical history.  This decision table accepts two inputs, birthDate of type date, and medHistory of type text, and returns a RiskRating of type text. The hit policy for this table is 'U' for unique.  Unique (U):  A unique rule must 'hit' evaluating to a unique result.  If multiple rules are valid, an error will be returned.",
-      "inputs": [ "birthDate", "medHistory" ],
-      "outputs": [ "riskRating" ],
-      "inputTypes": [ "date", "text" ],
-      "outputTypes": [ "text" ],
-      "rules": [
-        [ ">'1970-05-05'", "good", "medium" ],
-        [ ">'1970-05-05'", "bad", "high" ],
-        [ "['1935-05-05'..'1970-05-05']", "-", "medium" ],
-        [ "<'1935-05-05'", "good", "low" ],
-        [ "<'1935-05-05'", "bad", "medium" ]
-      ],
-      "hitPolicy": "U"
-    },
-    "tblTollTax": {
-      "comment": "This decision table generates a toll amount based the time a car enters the toll road.  This decision table accepts one input, operTime of type time, and returns two outputs: traffic of type text and toll of type number. The hit policy for this table is 'U' for unique.",
-      "inputs": [ "operTime" ],
-      "outputs": [ "traffic", "toll" ],
-      "refTypes": [ "time", "text", "number" ],
-      "rules": [
-        [ ">'19:00:00'", "low", 5 ],
-        [ "['15:00:00'..'19:00:00']", "high", 7 ],
-        [ "['09:00:00'..'15:00:00')", "medium", 6 ],
-        [ "['06:00:00'..'09:00:00')", "high", 7 ],
-        [ "<'06:00:00'", "low", 5 ]
-      ],
-      "hitPolicy": "U"
-    },
-    "tblParkingFee": {
-      "comment": "This decision table generates a parking fee based on the time a car spends in a parking garage. This decision table accepts one input, dtDuration of type duration, and returns one outputs, parkingFee of type number. The hit policy for this table is 'U' for unique.",
-      "inputs": [ "dtDuration" ],
-      "outputs": [ "parkingFee" ],
-      "refTypes": [ "duration", "number" ],
-      "rules": [
-        [ "<'PT20M'", 0 ],
-        [ "['PT20M'..'PT1H')", "2 *ceiling(duration(dtDuration)/duration('PT20M'))" ],
-        [ "['PT1H'..'PT4H')", "6 *ceiling(duration(dtDuration)/duration('PT1H'))" ],
-        [ ">='PT4H'", "30*ceiling(duration(dtDuration)/duration('P1D'))" ]
-      ],
-      "hitPolicy": "U"
-    }
-  },
-  "data": {
-    "comment": "The data section holds the input parameters for each decision table.",
-    "Date1": {
-      "comment": "This is a patient's date of birth.",
-      "value": "'1964-05-05'"
-    },
-    "Date2": {
-      "comment": "This is a patient's medical history rating.",
-      "value": "good"
-    },
-    "actualTimeEntered": {
-      "comment": "This is the time that a car enters the toll road.",
-      "value": "'18:50:05'"
-    },
-    "durationParked": {
-      "comment": "This is that a car spent in the parking garage.",
-      "value": "PT25M"
-    }
-  },
-  "formulas": {
-    "comment": "Call each decision table from the 'formulas section'.",
-    "dateResult": {
-      "comment": "This formula calls the tblRiskRating decision table passing two input parameters Date1 and Date 2",
-      "formula": "tblRiskRating(,,Date1, Date2)",
-      "finalValue": []
-    },
-    "tollResult": {
-      "comment": "This formula calls the tblTollTax decision table passing one input parameter, actualTimeEntered, and asks for the toll amount in the result.",
-      "formula": "tblTollTax('toll',,actualTimeEntered)",
-      "finalValue": []
-    },
-    "trafficResult": {
-      "comment": "This formula calls the tblTollTax decision table passing one input parameter, actualTimeEntered, and asks for the traffic category in the result.",
-      "formula": "tblTollTax('traffic',,actualTimeEntered)",
-      "finalValue": []
-    },
-    "durationResult": {
-      "comment": "This formula calls the tblParkingFee decision table passing one input parameter, durationParked.",
-      "formula": "tblParkingFee(,,durationParked)",
-      "finalValue": []
-    }
-  }
+{
+  "modelName": "DTDateTimeExample",
+  "modelType": "calculation",
+  "modelDescription": "RASON Date and Time Decision Table Examples: Decision Tables contain a set of rules which specify actions to perform based on specific conditions.  Decision tables are a good tool to use when there is a consistent number of rules, or conditions, to be evaluated followed by a specific set of actions to be perfrmed once a rule, or condition, is met. This example contains 3 decision tables, tblRiskRating, tblTollTax and tblParkingFee.",
+  "decisionTables": {
+    "comment": "Decision tables are created within the decisionTable section in a RASON model. In this example, there are 3 decision tables, tblRiskRating, tblTollTax and tblParkingFee",
+    "tblRiskRating": {
+      "comment": "This decision table generates a predicted medical rating based on the age of a patient and his/her's medical history.  This decision table accepts two inputs, birthDate of type date, and medHistory of type text, and returns a RiskRating of type text. The hit policy for this table is 'U' for unique.  Unique (U):  A unique rule must 'hit' evaluating to a unique result.  If multiple rules are valid, an error will be returned.",
+      "inputs": [ "birthDate", "medHistory" ],
+      "outputs": [ "riskRating" ],
+      "inputTypes": [ "date", "text" ],
+      "outputTypes": [ "text" ],
+      "rules": [
+        [ ">'1970-05-05'", "good", "medium" ],
+        [ ">'1970-05-05'", "bad", "high" ],
+        [ "['1935-05-05'..'1970-05-05']", "-", "medium" ],
+        [ "<'1935-05-05'", "good", "low" ],
+        [ "<'1935-05-05'", "bad", "medium" ]
+      ],
+      "hitPolicy": "U"
+    },
+    "tblTollTax": {
+      "comment": "This decision table generates a toll amount based the time a car enters the toll road.  This decision table accepts one input, operTime of type time, and returns two outputs: traffic of type text and toll of type number. The hit policy for this table is 'U' for unique.",
+      "inputs": [ "operTime" ],
+      "outputs": [ "traffic", "toll" ],
+      "refTypes": [ "time", "text", "number" ],
+      "rules": [
+        [ ">'19:00:00'", "low", 5 ],
+        [ "['15:00:00'..'19:00:00']", "high", 7 ],
+        [ "['09:00:00'..'15:00:00')", "medium", 6 ],
+        [ "['06:00:00'..'09:00:00')", "high", 7 ],
+        [ "<'06:00:00'", "low", 5 ]
+      ],
+      "hitPolicy": "U"
+    },
+    "tblParkingFee": {
+      "comment": "This decision table generates a parking fee based on the time a car spends in a parking garage. This decision table accepts one input, dtDuration of type duration, and returns one outputs, parkingFee of type number. The hit policy for this table is 'U' for unique.",
+      "inputs": [ "dtDuration" ],
+      "outputs": [ "parkingFee" ],
+      "refTypes": [ "duration", "number" ],
+      "rules": [
+        [ "<'PT20M'", 0 ],
+        [ "['PT20M'..'PT1H')", "2 *ceiling(duration(dtDuration)/duration('PT20M'))" ],
+        [ "['PT1H'..'PT4H')", "6 *ceiling(duration(dtDuration)/duration('PT1H'))" ],
+        [ ">='PT4H'", "30*ceiling(duration(dtDuration)/duration('P1D'))" ]
+      ],
+      "hitPolicy": "U"
+    }
+  },
+  "data": {
+    "comment": "The data section holds the input parameters for each decision table.",
+    "Date1": {
+      "comment": "This is a patient's date of birth.",
+      "value": "'1964-05-05'"
+    },
+    "Date2": {
+      "comment": "This is a patient's medical history rating.",
+      "value": "good"
+    },
+    "actualTimeEntered": {
+      "comment": "This is the time that a car enters the toll road.",
+      "value": "'18:50:05'"
+    },
+    "durationParked": {
+      "comment": "This is that a car spent in the parking garage.",
+      "value": "PT25M"
+    }
+  },
+  "formulas": {
+    "comment": "Call each decision table from the 'formulas section'.",
+    "dateResult": {
+      "comment": "This formula calls the tblRiskRating decision table passing two input parameters Date1 and Date 2",
+      "formula": "tblRiskRating(,,Date1, Date2)",
+      "finalValue": []
+    },
+    "tollResult": {
+      "comment": "This formula calls the tblTollTax decision table passing one input parameter, actualTimeEntered, and asks for the toll amount in the result.",
+      "formula": "tblTollTax('toll',,actualTimeEntered)",
+      "finalValue": []
+    },
+    "trafficResult": {
+      "comment": "This formula calls the tblTollTax decision table passing one input parameter, actualTimeEntered, and asks for the traffic category in the result.",
+      "formula": "tblTollTax('traffic',,actualTimeEntered)",
+      "finalValue": []
+    },
+    "durationResult": {
+      "comment": "This formula calls the tblParkingFee decision table passing one input parameter, durationParked.",
+      "formula": "tblParkingFee(,,durationParked)",
+      "finalValue": []
+    }
+  }
 }

package/examples/calculation/DecisionTables/DT Expression example.json

@@ -1,32 +1,32 @@
-{
-  "modelName": "DTExpressionExample",
-  "modelDescription": "RASON Decision Table Example using an Expression: This example illustrates how to utilize duration in an expression in the body of a decision table. The tblParkingFee decision table calculates a fee based on the time spent in a parking garage.",
-  "modelType": "calculation",
-  "data": {
-    "comment": "The input parameter period, use binding to feed dif. values",
-    "period": {
-      "value": "PT25M"
-    }
-  },
-  "decisionTables": {
-    "tblParkingFee": {
-      "comment": "This decision table calculates a parking fee based on the amount of time spent in a parking garage.  The input parameter is the time spent, or the duration.  There are two formats for duration, one measuring periods in months and another measuring periods in seconds. For example, P1DT1H2M3S denotes: P for 'period', 1D for 1 day, T for 'time', 1H for 1 hour, 2M for 2 minutes and 3S for 3 seconds. The output is the parking fee. The fee is generated in the rules portion of the table. For example, if your car is parked in the garage for 90 minutes (PT1H30M), then the parking fee will be 6 * ceiling(duration(PT1H30M)/duration(PT1H)) or 12.  The Hit policy is Unique which means that if more than one rule is successful, an error will be returned.",
-      "inputs": [ "dtDuration" ],
-      "outputs": [ "parkingFee" ],
-      "rules": [
-        [ "<'PT20M'", 0 ],
-        [ "['PT20M'..'PT1H')", "2 *ceiling(duration(dtDuration)/duration('PT20M'))" ],
-        [ "['PT1H'..'PT4H')", "6 *ceiling(duration(dtDuration)/duration('PT1H'))" ],
-        [ ">='PT4H'", "30*ceiling(duration(dtDuration)/duration('P1D'))" ]
-      ],
-      "hitPolicy": "Unique"
-    }
-  },
-  "formulas": {
-    "comment": "The res formula computes a parking fee by calling the tblParkingFee decision table while passing the input parameter, period or PT25M (25 minutes).",
-    "res": {
-      "formula": "tblParkingFee(,,period)",
-      "finalValue": []
-    }
-  }
-}
+{
+  "modelName": "DTExpressionExample",
+  "modelDescription": "RASON Decision Table Example using an Expression: This example illustrates how to utilize duration in an expression in the body of a decision table. The tblParkingFee decision table calculates a fee based on the time spent in a parking garage.",
+  "modelType": "calculation",
+  "data": {
+    "comment": "The input parameter period, use binding to feed dif. values",
+    "period": {
+      "value": "PT25M"
+    }
+  },
+  "decisionTables": {
+    "tblParkingFee": {
+      "comment": "This decision table calculates a parking fee based on the amount of time spent in a parking garage.  The input parameter is the time spent, or the duration.  There are two formats for duration, one measuring periods in months and another measuring periods in seconds. For example, P1DT1H2M3S denotes: P for 'period', 1D for 1 day, T for 'time', 1H for 1 hour, 2M for 2 minutes and 3S for 3 seconds. The output is the parking fee. The fee is generated in the rules portion of the table. For example, if your car is parked in the garage for 90 minutes (PT1H30M), then the parking fee will be 6 * ceiling(duration(PT1H30M)/duration(PT1H)) or 12.  The Hit policy is Unique which means that if more than one rule is successful, an error will be returned.",
+      "inputs": [ "dtDuration" ],
+      "outputs": [ "parkingFee" ],
+      "rules": [
+        [ "<'PT20M'", 0 ],
+        [ "['PT20M'..'PT1H')", "2 *ceiling(duration(dtDuration)/duration('PT20M'))" ],
+        [ "['PT1H'..'PT4H')", "6 *ceiling(duration(dtDuration)/duration('PT1H'))" ],
+        [ ">='PT4H'", "30*ceiling(duration(dtDuration)/duration('P1D'))" ]
+      ],
+      "hitPolicy": "Unique"
+    }
+  },
+  "formulas": {
+    "comment": "The res formula computes a parking fee by calling the tblParkingFee decision table while passing the input parameter, period or PT25M (25 minutes).",
+    "res": {
+      "formula": "tblParkingFee(,,period)",
+      "finalValue": []
+    }
+  }
+}