📄️ 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
📄️ Debug Panel
Shesha actually has two different debug panels for inspecting live data while you build or run a form: a read-only one built into the Form Designer, and a separate, editable one available anywhere in a running application. They are opened differently and show different things - this page covers both.
📄️ 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.