Rendered Form (Rules Output)
?
The decision service decides which controls render, where data is written, and validation behavior.
UI-Specific Schema Fields
pathToData: target object branch for stage values
fieldName: property key written by the control
type: renderer selected (Text, Radio, MultiExpenses, etc.)
option: choice list used by selectable controls
required/requiredBy...: mandatory behavior (static/conditional)
minLength/maxLength/minDT/maxDT: constraints
UI Control Legend
  • * Required
  • * Conditionally required
  • R Read-only / derived
  • ! Validation message
  • C UI control rendered from rules
Provenance
Rule-defined User-entered Derived System/default
Waiting for stage render...
Explainability Hooks
  • Start a sample to see stage-specific explainability hints.

Rules Driven Dynamic Forms

In these samples the forms are generated on the fly based on rules from Corticon.js decision services. It shows how the decision service acts as the model for a generic form component. Questions can be conditionally asked based on inputs from previous questions and external data. The component can render the form with either simple HTML controls or KendoUI components.