Overview

The slider element allows you to make selections or adjust settings within a continuous range of values. It is typically represented by a bar that you can move left or right to choose a specific value within the range.

Use Cases of the Slider Element in a Guided Workflow:

1. Setting a Budget or Price Range: Define your desired spending limit for a product or service.

2. Selecting a Date or Time: Choose a specific date or time within a given range.

3. Setting Preferences: Adjust levels for things like workout intensity or coffee strength.

In the slider element, you can specify the minimum and maximum values to define the range and set the step size for more precise adjustments.

Additionally, you can configure disability conditions for the slider, which will disable it from being adjusted when certain conditions are met.

​

Key Characteristics

1. Track and Handle: The slider consists of a horizontal and a movable handle (or knob) that users drag to change the value. 

2. Defined Range: Sliders typically have a minimum and maximum value, with the current value being determined by the handle's position. 

3. Real-time Feedback: The selected value is often displayed in real-time as the user moves the handle. 

​

Various Fields in Slider 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: Enable this checkbox to make the field required, preventing users from proceeding without providing a value.

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

• The default value is the preset value used when the end user fills in nothing. 

• Minimum Value: This defines the minimum value you want to set in the range. 

• Maximum Value: This defines the maximum value you want to set in the range. 

• Step Size: This determines the amount by which the slider value will increase or decrease. By default, it will change by one, but this can also be customized from the options.

• Enable Reporting: This toggle allows 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.

• Visibility Conditions: is 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: is 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.

• Configure Error Message: An error message will be displayed in the following conditions:

  • If the value is required and is not entered.