Button

the button element is the primary action trigger in procesio forms it can be used to submit the form, trigger a process, execute javascript, navigate between steps, or initiate any other interaction that requires deliberate user intent when submit is set to true, clicking the button submits the form and its collected data when used without submission, it acts as a pure action trigger — useful for intermediate saves, data refreshes, or launching sub processes mid flow its label, visibility, and interactive state are all controllable from the data model at runtime, making it easy to implement conditional ui patterns like 'show submit button only after all required fields are filled' key use cases • primary form submission (submit true) at the end of a form flow • triggering a mid form process (e g , fetch data, validate externally) without submitting • dynamically disabling the button until all required conditions are met • hiding the submit button until the user has completed a specific step • presenting multiple action options (approve / reject) as separate buttons 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, onclick, or custom triggers api name description type default notes label the button's display text string — — tooltip tooltip text shown on hover string — — infotext supplementary info displayed near the button string — — readonly if true, the button is non clickable boolean false — visible controls button visibility boolean true — name unique element name string — — id unique element id string — — submit if true, clicking this button submits the form boolean false — for support, please join our https //discord com/invite/cebukgjefv for further assistance and support