Overview

The Password Input component is primarily used in customer-facing Guided Workflows (GWs) to securely collect passwords for verifying a user's identity. When entering the password, the characters are masked (usually represented by dots) to maintain confidentiality. Users can reveal the password by clicking on the eye icon.

You can customize the format of the password input to be either numeric or alphanumeric, and you can set both the maximum and minimum character lengths for the password. Additional customization options include defining the width, alignment, and disability conditions of the component, which can disable the field if required, preventing users from entering any data when needed.

​

Various Fields in Password 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"). 

• Mark Field as Mandatory: It is used to mark the field mandate, which means that if the particular field is not filled it will not allow the user to move to next step. 

• Placeholder: A Placeholder is a short, descriptive text displayed inside an input field to guide users on what to enter. It disappears when users start typing.

• Format:You can choose between two password formats: alphanumeric or numeric. Once a format is selected, users will only be able to create their password in that specified format. 

• Width: Define the width of the text area, ensuring it is entered as a percentage (%), with a maximum limit of 100%. Customize it according to the use case.

• Minimum and Maximum Length: You can set both the minimum and maximum length for the password. This will ensure that users enter a password within the defined limits.  

​

​

Configure Error Message: This field allows you to create a warning message for users in the below conditions:

• • If the value is required.

  • Password only numeric but something else filled.

  • If the length of the password entered is less than the minimum character limit

• Alignment 

  1. Start Alignment: 

     1. The content is aligned to the left side  

     2. Use Case: Creates a structured look, often used when the design emphasizes a logical flow or pairs text with an image on the right. 

     3. Example: Title and subtitle are placed on the left, while the rest of the space remains open or used for visuals. 

  2. Center Alignment: 

     1. The content is aligned to the center.

     2. Use Case: Best for symmetrical designs or when the content needs to grab attention equally from all sides. 

     3. Example: A sale announcement with the title and subtitle in the middle of the for maximum focus. 

  3. End Alignment: 

     1. The content is aligned to the right side. 

     2. Use Case: Creates a systematic look or design.

     3. Example: The title and subtitle are on the right side, and the left is used for decorative imagery or emphasis. 

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

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

  1. Based on Field Value: 

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

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

  2. Based on User Role: 

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

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

  3. Based on Data Completeness: 

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

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

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