📄️ Action Configurations
Actions define what happens when a user interacts with a component - clicking a button, submitting a form, or selecting a row. Rather than writing code for every interaction, you configure actions through the designer by selecting an action type, filling in its settings, and optionally chaining a second action to run on success or failure.
🗃️ Client-side Scripting
4 items
📄️ Debugging in the Designer
When a form does not behave the way you expect, the first thing you usually need is the identity of the component you are looking at, and then the values a script is actually seeing. The Form Designer gives you the first directly, and your browser's console gives you the second.
📄️ Form Builder Canvas
The form builder canvas is the central area of the form designer where you lay out a form by dragging components onto it. The canvas is a true WYSIWYG surface, which means what you arrange on it closely matches how the form will render for a user. You can zoom and scroll the canvas, so it stays an accurate picture of the final form even as it grows larger than the screen.
📄️ Form Templates
Every form in Shesha starts from a template. A template sets the layout container your form uses as its foundation. Choosing the right template means Shesha pre-wires the correct display and interaction behaviour for your use case, saving you from building common layouts from scratch.
📄️ Form Naming Conventions
Form names need to be unique within the module. The form name should be in lowercase and use hyphens to separate words and should not have any other special characters or spaces.
🗃️ Form Events
4 items
📄️ Toggling Edit Mode
Every Shesha application runs in one of two modes. Live Mode is how your end users experience the app day to day. Edit Mode unlocks the parts of the app an administrator can reconfigure right there on the page, without switching over to the Configuration Studio.