This article explains the features of the Toggle block and how it can be used to design your app.
Click on the Toggle block and start editing on the panel that appears on the right side.
The label is the name of the block that the end user sees in the app, displayed beside the toggle switch.
Example: Enable Notifications, Approve Request.
The description provides additional information displayed next to the toggle switch to guide the user. This is a required option to configure.
Example: Turn on to receive updates, Toggle to approve.
Enter the text you want to display in the submission when the toggle is turned on (enabled). This text will appear in the Submissions Tab for any submission where the toggle was activated.
Example: "Enabled" for toggling features on, or "Approved" for confirming requests.
Enter the text you want to display in the submission when the toggle is turned off (disabled). This text will appear in the Submissions Tab for any submission where the toggle was deactivated.
Example: "Disabled" for toggling features off, or "Not Approved" for rejecting requests.
Select the default state for the toggle when the app loads. Set to either enabled (True) or disabled (False) by default, depending on the primary use.
Use this option to show or hide the field under specific conditions. It accepts the standard Clappia formulae, similar to conditional sections or in the ‘Calculations & Logic’ block.
For example: The display condition as seen in the image is given as {enable_not]=”Enable”. This means the field “Email Notifications” will appear in the app only if “Enable Notifications” field is toggled on whose true value is configured as “Enabled”.
Here, the rest of the fields appear in the app once “Email Notifications” is toggled on (display conditions have been given to all the remaining 3 fields).
This option appears once a condition is set in the Display this field if option. Enable this setting if you want the field's value to be retained even when the field is hidden. This is useful for preserving user input in cases where the field may temporarily disappear based on conditions.
Example: If the field is hidden based on user selection but you still need to keep the entered value for future reference or calculations, enable this option to ensure the data is retained.
This option is enabled by default. When active, end users can change the toggle state even after creating a submission. Disable this option if you want the toggle state to remain fixed once submitted.
Desktop View: Set the width of the PDF Viewer block in the desktop view. Options are 100%, 75%, 50%, or 25%.
Mobile View: Set the width of the PDF Viewer block in the mobile view. Options are 100% or 50%.
This is the unique identifier for the Email Input field, which can be used in formulas or references within the app. This appears automatically after saving your configuration of the Email Input block.
In App Home, users can toggle this field on or off based on their needs. When the toggle is enabled, the submission entry in the Submissions Tab will display the True Value text (e.g., "Enabled" or "Approved"). If the toggle is disabled, the False Value text (e.g., "Disabled" or "Not Approved") will appear in the submission. This provides clear visibility into the selected state for each submission.
L374, 1st Floor, 5th Main Rd, Sector 6, HSR Layout, Bengaluru, Karnataka 560102, India
+91 96418 61031
3500 S DuPont Hwy, Dover,
Kent 19901, Delaware, USA
+1 (341) 209-1116
3500 S DuPont Hwy, Dover,
Kent 19901, Delaware, USA
+1 (341) 209-1116
L374, 1st Floor, 5th Main Rd, Sector 6, HSR Layout, Bengaluru, Karnataka 560102, India
+91 96418 61031