pub struct EvaluateRequest {
pub decision_id: Option<String>,
pub inputs: HashMap<String, Value>,
pub xml: Option<String>,
pub decision_ref: Option<String>,
}Fields§
§decision_id: Option<String>A saved dmn_decision path to load and evaluate
inputs: HashMap<String, Value>Input values keyed by FEEL variable name (an input column’s inputExpression text). A nested object is flattened into dotted keys – {\"applicant\": {\"age\": 35}} supplies applicant.age – the same mapping a running BPMN businessRuleTask applies to its process variables, so a decision evaluates identically here and in production.
xml: Option<String>Inline DMN 1.3 XML to evaluate instead of a saved decision_id
decision_ref: Option<String>In-document <decision id> selector, separate from decision_id (which is the storage path when loading a saved decision). When set, selects which decision inside the document to evaluate – e.g. a decision other than the first in a saved multi-decision document. When omitted, inline xml falls back to decision_id as its selector and a stored decision evaluates its first decision element. Optional and backwards-compatible.