Trigger Events for Form and Elements

overview our platform provides a variety of trigger events that allow you to define what happens when users interact with your forms or specific controls inside them triggers help you connect form actions with workflows, scripts, or data mappings, making your forms highly dynamic and customizable key features 1\ data mapping form events support data mapping between form fields and process variables this feature enables you to seamlessly transfer data from your forms to associated processes, enhancing data consistency and integrity dynamic mapping establish dynamic links between form fields and process variables automate the transfer of relevant data, reducing manual efforts 2\ event triggers form events can be triggered by various actions within the form, creating a responsive and interactive user experience trigger events 📝 form lifecycle events onload – fires when the form is initially loaded onbeforesubmit – fires just before the form is submitted (useful for validation or preprocessing) onaftersubmit – fires immediately after the form is submitted (useful for cleanup or navigation) 🔤 input & interaction events onclick – fires when a control or button is clicked onhover – fires when the user hovers over a control oninput – fires when the user types or changes a value in a field onfocus – fires when a field gains focus onblur – fires when a field loses focus 📊 table and dynamic row events onpaginationchanged – fires when table pagination changes (e g , switching pages) onrowadded – fires when a new row is added to a table (dynamic row) onrowdeleted – fires when a row is deleted from a table (dynamic row) 📑 tabs events ontabchange – fires when the user switches between tabs ✅ approval events onbeforeapprove – fires before an approval action is submitted onbeforereject – fires before a rejection action is submitted onbeforesubmit – fires before either approval or rejection is submitted onafterapprove – fires after an approval action is submitted onafterreject – fires after a rejection action is submitted onaftersubmit – fires after either approval or rejection is submitted ⏱️ debounce debounce delays the event until the user pauses their action for example, when typing, the event will only run once after the user stops , instead of running on every keystroke this helps avoid unnecessary runs and improves performance 🎛️ run events conditionally with set condition , you can decide when an event should (or shouldn’t) run by default, events run every time they are triggered with a condition, the event will only run if the rule you set is true getting started adding events to add events to your forms open the form or select an element expand the events section choose event and trigger set debounce if needed configure the event (check according documentation pages for more details) set condition(s) best practices clear naming conventions use descriptive names for your events and triggers to facilitate easy identification test extensively before deploying forms with events in a live environment, thoroughly test all configurations to catch and resolve any potential issues troubleshooting if you encounter issues with your form events check the event logs for error messages and details verify the event configurations (check troubleshooting section on according documentation page) trigger process docid\ ijhssgp0lshyikannrfzz trigger javascript docid\ i49dpqt0dgnnnei8hnfay trigger form docid\ n0atlkze0efrkirslstea map form variable docid\ qurmiao 3brq60czv fv7 email notifications in the form builder, once a task is displayed in the assinged to me section, an email will be sent to the user the email is sent for approvers and task assignees as well for support, please join our discord community for further assistance and support