Approval

the approval element is a purpose built control for formalizing review decisions within procesio forms it presents the reviewer with a clear approve / reject action pair and optionally requires them to leave a comment before their decision is recorded — enforcing accountability and audit readiness in approval workflows unlike a generic button or radio button, the approval element captures rich metadata alongside the decision the reviewer's user object (responseuser), the timestamp of the decision (responsedate), their written comment (comment), and the outcome itself (response) all of this data is part of the element's data model and flows directly into your process for downstream actions such as notifications, escalations, or document generation comment requirements can be made conditional per outcome — you can require a justification on rejection but make it optional on approval, or vice versa, giving you fine grained control over the governance policy your workflow enforces key use cases • document, purchase order, or leave request approval workflows • multi level approval chains where each reviewer's response is captured and stored • requiring a written reason for rejection (iscommentrequiredonreject true) for compliance • reading responseuser and responsedate at runtime to stamp a document or send a notification • pre filling the description with context sensitive instructions based on the record being reviewed runtime api — attributes in procesio forms all attributes below are accessible and modifiable at runtime via the element's data model in procesio forms — on any available event such as onload, onchange, or custom triggers api name description type default notes label display label above the approval control string — — tooltip help text shown alongside the label string — — description instructional text for the reviewer string — — infotext supplementary info displayed below the element string — — visible controls element visibility boolean true — comment the reviewer's written comment — readable at runtime string — — responsedate timestamp of when the decision was made string|date|null — — responseuser the user who made the decision (id, name, email) object|null — — response the decision outcome — approve or reject string|null — approve, reject name unique element name string — — id unique element id string — — iscommentrequiredonapprove forces a comment when approving boolean false — iscommentrequiredonreject forces a comment when rejecting boolean false — for support, please join our https //discord com/invite/cebukgjefv for further assistance and support