The Hierarchical Picklist component enables brands to capture multi-level categorical information through a single, interactive dropdown. It is designed for use cases where the user must drill down through multiple layers of a hierarchy—such as Issue Category → Sub-Issue → Reason—within one consolidated component, without needing separate fields for each level.

This component fetches hierarchical values from a selected Entity Studio entity, and dynamically renders an expandable tree structure. Users can navigate through categories using arrow expanders, search across all levels, and select a final leaf value. The full hierarchical path is then returned as the component’s output.

The Hierarchical Picklist component is a powerful capability when deep category structures need to be captured efficiently. It consolidates multi-level selections into a single, searchable, interactive UI—saving space and significantly improving user experience.

Various Fields in Picklist Input ​

​

​

• API Name: A unique identifier used to reference the component programmatically in integrations, scripts, and API requests. API names typically follow a predefined naming convention.
• Label: Specifies the name displayed to users at runtime. Use a clear and descriptive label to indicate the expected input. You can also configure the label dynamically by using the Resource Selector.
• Help Text: Displays additional guidance to help users understand the purpose of the field.
• Placeholder: Displays instructional or sample text before a user makes a selection.
• Mark Field as Mandatory: Makes the field required. Users cannot proceed to the next step until a value is selected.
• Entity Type: Select the Entity Studio entity that provides the hierarchical data used in the pick list.

• Levels of Hierarchy: Available after you select an entity in the Entity Type field. Use this setting to define the entity fields that represent each level of the hierarchy. You can add as many hierarchy levels as needed.

  Example
  If the selected entity contains the following fields:

  • Issue Category 1
  • Issue Category 2
  • Issue Category 3
• Map these fields sequentially in the hierarchy builder. The component automatically creates hierarchical relationships based on matching entity record values.
• Filter Records: Available after you select an entity in the Entity Type field. Use this option to filter entity records based on available fields. To add multiple filter criteria, select + Add Condition.
• Delimiter: Defines how the hierarchical path is displayed when passed to the next screen. Common delimiters include /, >, and →.

• Default Value: Sets a predefined value for the component. You can enter a static value or use a variable.
• Parent Pick List for Auto-Expansion: Select the parent pick list that triggers automatic expansion of the next dependent pick list.
  Example: If Pick List 10 depends on Pick List 9, selecting a value in Pick List 9 automatically expands Pick List 10. The same behaviour applies to subsequent dependent pick lists.
• Refresh Value on Screen Revisit: Resets the field to its default value when users revisit the screen through forward navigation, helping ensure accurate data collection.
  

Note: This setting applies only when the screen is revisited through forward workflow navigation. It does not apply to backward navigation

• Add On Select Action: Specifies an action that occurs automatically when a user selects a value.
  Available options:

  • Next Screen Action
    Automatically moves the workflow to the next screen after a selection is made.
  • Back Screen Action
    Returns the user to the previous screen after a selection is made.
• Enable Reporting: Includes the component's values in reports.

• Input Disability Conditions: Determines when the component is disabled and unavailable for user interaction.

  Examples

  • Based on Field Value
    Disable the Submit button until the Terms and Conditions checkbox is selected.
  • Based on User Role
    Disable the Delete Record button for users who do not have administrator permissions.
  • Based on Data Completeness
    Disable the Next button until all required fields are completed.

• Visibility Conditions: Controls whether the component is displayed based on conditions such as user roles, permissions, field values, or contextual data.

  Example

  • Condition: Show the Priority Escalation section when Ticket Priority is set to High.
  • Visibility Rule: Ticket_Priority == 'High'
  • Result: The Priority Escalation section is displayed only for high-priority tickets.

• Configure Error Message: Defines the message displayed when a required field is left empty or validation fails.​