Overview

A checkbox is an interactive element in a form that enables users to independently select or deselect options. Checkbox Group inputs allow for integrating multiple checkboxes.

​

Various Fields in Checkbox Group

• API Name: It is a unique identifier that can be used as a reference to the value of this component. Please ensure there are no hyphens or spaces, and that the name does not start with a number or underscore.

• Label: This field allows you to name the checkbox group. If you want to customize the name, you can use this component to define it. 

• Mark Field as Mandatory: You can click this if you want to make this field mandatory.

• Add Help Text: It is the text that will be displayed to the end user to help them understand the label’s meaning. 

• Option Source: The option source can be either manual or dynamically defined by a variable.

​

Manual

• In this, the option values are entered directly by the user.

• You can click +Add More Options to add more options in the checkbox group.

• Default Value: You can define the pre-populated value for the component. Based on the above added options, you can select the default value from the dropdown list. You can choose multiple values here.

​

By Variable

• The option values can be populated dynamically from a specified variable.

  ​

  

​

Other Common Fields

• Enable Reporting: This toggle allows you to specify whether the auto-drafted values in the screen component should be included in reporting. When enabled, this ensures that auto-saved data is captured and made available for analytics, addressing gaps in reporting accuracy caused by un-submitted workflows.

• Input Disability Conditions: A rule or set of criteria that determines whether a specific element, such as a field, button, or component, should be disabled (i.e., grayed out and non-interactive) in a user interface. It restricts user interaction based on certain conditions, ensuring that actions are contextually valid or preventing errors. 

  • Example: 

    • Based on Field Value: 

      • Condition: Disable the "Submit" button if the "Terms and Conditions" checkbox is unchecked. 

      • Result: The user cannot submit the form until they accept the terms. 

    • Based on User Role: 

      • Condition: Disable the "Delete Record" button for users without "Admin" permissions. 

      • Result: Only admins can delete records, while other users see the button but cannot interact with it. 

    • Based on Data Completeness: 

      • Condition: Disable the "Next" button until all required fields are filled. 

      • Result: Users are prevented from moving forward until they complete the required steps.

• Visibility Condition: A rule or set of rules that determines whether a specific element, field, or component is visible to users in an application or interface. These conditions are typically based on factors such as field values or contextual data. Visibility conditions ensure that users only see relevant information, improving usability and security. 

  • Example  

    • Condition: Display a "Priority Escalation" section if the "Ticket Priority" is set to "High." 

    • Implementation: Visibility Condition: Ticket_Priority == 'High' 

    • Result: The "Priority Escalation" section appears only for high-priority tickets. 

• Configure Error Message: This field allows you to create a warning message for users if the value is left empty.