Overview

Radio buttons are an effective input tool that enables customers to quickly and easily select a single option from a predefined set. They are particularly useful for simplifying decision-making and streamlining workflows.

Key features of radio buttons include:

• Option Input: You can add options manually or resolve them in real-time using variables.

• Disability Conditions: Specific conditions can be set to disable the radio button component, restricting users from making changes when required.

This flexibility ensures radio buttons can be tailored to suit various use cases, enhancing user interaction and overall workflow efficiency.

​

Various Fields in Radio Group Component

• API Name: The API Name is a unique identifier used to reference a particular object, field, or component in an application programmatically. It is typically used in backend code, integrations, or API calls. API Names are often system-generated and follow a specific naming convention, such as using underscores instead of spaces (e.g., Customer_Status__c). 

• Label: The Label is the user-friendly name for an object, field, or component that is displayed in the user interface (UI). It is designed to be easily understood by end-users and often includes spaces or capitalization for readability (e.g., "Customer Status"). 

• Mark Field as Mandatory: to mark the field mandatory, if the field is not a field, it will not allow the user to move to the next step. 

• Add Help Text is the text that will be displayed to the end user to understand the Label’s Meaning. 

• Option Source: You can either choose Manual or By Variable in this. This will help you name the option, and whatever you enter in this field will be reflected in the user interface (UI). You have two choices: "Manual," where you can enter information manually, and "Variable," which gives you the flexibility to select a resource or a custom source/code.

​

Manual

If you choose Manual in the option source, you need to configure the following fields:

• Define your option: You can manually define the picklist options.

​

By Variable

If you choose By Variable in the option source, you need to configure the following fields:

• Choose Variable: Define a data map to populate the pick list directly or select a pre-defined variable using the resource selector, e.g., [["label": "optionLabel1", "value": "optionValue1"], ["label": "optionLabel2", "value": "optionValue2"]]

• Value: You can define the backend value of the option.

• Label: You can add the text to be shown on the card.

• Description: You can add the additional information that you want to be shown below the label.

• Icon URL: You can add the URL for the image/icon to be displayed on the card.

​

Other Common Fields

• Default value: It is the preset value used when the end user fills in nothing. 

• Alignment: You can choose the alignment of the option, either in a horizontal or vertical layout. 

• Add On Select Action: This feature allows you to specify the option selected by the user. Sprinklr offers two options: Next Screen Action and Back Screen Action. 

  ​

  ​

  ​

• Enable Reporting Explanation: The Enable Reporting 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.

• Configure Error Message: This field allows you to create a warning message for users when they leave the field empty. 

• Visibility Conditions: A rule or set of rules that determine 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 user roles, permissions, 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. 

•  Disability Condition: 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.