RuleEngine
Rule Engine – Start
Summary (SEO Meta Description):
The Rule Engine processor in WeHub evaluates rules against workflow data.
Configure rules, inputs, and outputs with schemas to automate decision-making.
Overview
The Start action in the Rule Engine allows workflows to apply rule-based logic on incoming data.
It evaluates conditions, transforms inputs, and produces outputs based on defined rules.
This is essential for business logic automation, data validation, and dynamic decision-making within workflows.
⚙️ Configuration Options
| Field | Type | Description |
|---|---|---|
| Label | String | Custom name for the node (e.g., "Check Patient Consent Rule"). |
| Rule | String | Define one or more rules for evaluation (business logic). |
| Input | Object | Input object or schema-driven fields to feed into the rule engine. |
| Input Schema | Schema | (Optional) Schema for validating input data. |
| Truncate Input | Boolean | Toggle truncation of large input fields. |
| Truncate Level | Integer | Depth/length for truncation when enabled. |
| Output | Object | Result object defined by rules. |
| Output Schema | Schema | (Optional) Schema for validating output data. |
| Truncate Output | Boolean | Toggle truncation of large output fields. |
| Truncate Level | Integer | Depth/length for truncation when enabled. |
💡 Example Use Cases
- Healthcare → Validate patient consent or filter FHIR resources by rules.
- Finance → Flag transactions over a threshold for fraud detection.
- Ops → Route workflow events dynamically based on business conditions.
FAQ
Q: Can I define multiple rules?
A: Yes, you can add multiple rules, and each will be evaluated against the input data.
Q: What happens if input data doesn’t match schema?
A: The node fails with a schema validation error unless error handling is applied.
Q: Is truncation required?
A: Not required, but useful for handling large payloads (e.g., logs, documents).
Keywords: WeHub Rule Engine, Start Rule Engine, business rules, decision automation, data validation