Struct EvaluateServiceRequest 

pub struct EvaluateServiceRequest {
    pub decision_id: Option<String>,
    pub xml: Option<String>,
    pub decision_service_ref: Option<String>,
    pub inputs: HashMap<String, Value>,
}

EvaluateServiceRequest : Evaluate one <decisionService> – the whole DRD closure below it – as a unit (Flowable part2). Deliberately a separate shape from EvaluateRequest: a decision service has no single hit_policy and no single matched_rules, so folding it into EvaluateResponse would leave two of that schema’s three required fields meaningless.

Fields

decision_id: Option<String>

A saved dmn_decision path whose document holds the decision service

xml: Option<String>

Inline DMN 1.3 XML to evaluate instead of a saved decision_id

decision_service_ref: Option<String>

The in-document <decisionService id> to run. Optional only when the document declares exactly one decision service, which is then resolved automatically (the same rule a BPMN decision task already applies to a decisionServiceReference that carries no in-document selector). Two or more, and the request is rejected with every declared service id named: picking the first would make which one ran depend on element order.

inputs: HashMap<String, Value>

Input values keyed by FEEL variable name, flattened into dotted keys exactly as for EvaluateRequest. Each decision’s result is then bound into the same context twice: under each output column’s bare name (Flowable parity – Flowable merges results flat into one shared variable map and never reads <variable>), and under the decision’s own <variable name> (single output) or <variable name>.<column> (several outputs), which cannot collide.

Implementations

impl EvaluateServiceRequest

pub fn new(inputs: HashMap<String, Value>) -> EvaluateServiceRequest

Evaluate one <decisionService> – the whole DRD closure below it – as a unit (Flowable part2). Deliberately a separate shape from EvaluateRequest: a decision service has no single hit_policy and no single matched_rules, so folding it into EvaluateResponse would leave two of that schema’s three required fields meaningless.

Trait Implementations

impl Clone for EvaluateServiceRequest

fn clone(&self) -> EvaluateServiceRequest

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for EvaluateServiceRequest

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for EvaluateServiceRequest

fn default() -> EvaluateServiceRequest

Returns the “default value” for a type.

impl<'de> Deserialize<'de> for EvaluateServiceRequest

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq for EvaluateServiceRequest

fn eq(&self, other: &EvaluateServiceRequest) -> bool

Equality operator ==.

fn ne(&self, other: &Rhs) -> bool

Inequality operator !=.

impl Serialize for EvaluateServiceRequest

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.

impl StructuralPartialEq for EvaluateServiceRequest