Overview

The Number Input component is designed to capture and store numerical data. It provides several constraints to ensure data accuracy and validity:

• Minimum Value: If a number less than the defined minimum value is entered, an error message will prompt the user to correct it.

• Maximum Value: If a number exceeds the specified maximum value, an error message will alert the user.

• Maximum Decimal Places: If the input has more decimal places than allowed, an error message will notify the user.

Customization options include defining the field's width, alignment, and disability conditions, which can disable the field to prevent user input when required.

​

​

​

​

Various Fields in Number Input

• 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"). 

• Add Help Text: You can enable this toggle to add the help text for the user.

• Placeholder: It specifies the name of the field displayed in the system.  

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

• Default Value: Set a default value for the field that will be used if no selection is made by the users. This feature also allows customization with the addition of custom variables. 

• Minimum Value: You can define the lowest value a user can enter.

• Maximum Value: You can define the highest value a user can input.

• Max Decimal Places: You can set how many digits can appear after the decimal point.

• Enable Reporting: Once this feature is enabled, you can utilise this field for reporting purposes. 

• Restricted Keyword Lists: It is a multi-select configuration field. It enables you to assign one or more predefined keyword lists. If your input contains any terms from the selected restricted keyword lists, an error message will be triggered. This message is configurable once you enable the Configure Error Messages toggle. This feature helps you maintain better input quality control and enforce compliance with or content guidelines dynamically within your workflow.

• Configure Error Message: This field allows you to create a warning message for users in the following scenarios:

  • If the value is required.

  • If number entered exceeds set min and max limits.

  • If decimal places in the number entered exceeds set max limit.

  • If text entered has restricted keywords.

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