Overview

This is an extension of the text input. It also has a pattern for validation of the URL and a placeholder to show the end user the expected format of the URL.

Various Fields in URL Input

Various Fields in URL 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: It is the text that will be displayed to the end user to help them understand the label’s meaning. 

• Placeholder: The placeholder attribute in the URL input field offers users a visual cue of the expected format for the URL, such as "http://www.example.com." This placeholder disappears once the user starts typing, helping users understand the format they need to follow.

• Regex Pattern: The URL input field includes pattern validation to ensure that the URL entered is in the correct format. This prevents users from submitting incomplete or invalid URLs, improving data accuracy.

• Default Value: You can add a pre-populated value for the component.

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

• 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 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: An error message will be displayed in the following conditions:

  • If the value is required and is not added.

  • If the value entered does not match the regex supported.