Hidden component
The content on this page is outdated and will not receive updates. For the most up-to-date functionality, refer to Setting up and managing flows.
Use a hidden component to ensure a value exists on a page, so that it can be used with validation or page conditions/operations.
Overview
Hidden components do not present or display anything to a flow user when they are added into a page, but are used in situations where you require a "hidden" value to exist on a page. This value can then be used for validation or page conditions/operations.
For example, you could use this in combination with a page condition to show/hide other components on a page, depending on a hidden component value:
-
If "value x" is empty, display "component B".
-
If "value x" is not used in any component on the page, the page condition will not work.
General settings
The following options and settings can be configured.
| Setting | Description |
|---|---|
| Name | Enter a name for the component. |
| Help information about this component | Display help text directly below the component, for example to provide further information on how to use the component. |
State
Select the value that you wish to save the user selection state data into.
- Save the component state into: Click Select or create a new value to select an existing value or create a new value.
Styles
Apply additional CSS styling to the component.
- Enter space-delimited CSS classes/selectors into the CSS Classes field.
When you run the flow, these classes are appended to the main component class. See CSS reference.
Validation
Add client-side page validation to the component. You cannot add validation if you are saving state data into a boolean or object value.
- Click Add Validation.
- Select the validation Type.
- Enter a valid Value for the validation type.
- Enter a feedback Message to show to the user if the validation criteria is not met.
- Click Update to add the validation item.
| Setting | Description |
|---|---|
| Required | Specify if the component requires user selection before the next step in the flow can be navigated to. For example, a user must use the component before they are allowed to progress in the flow. 1. Switch on the toggle to set the component as requiring selection from a user before they can progress in the flow, for example to the next page. 2. Switch off the toggle to allow a user to progress in the flow, even if they have not used the component, for example if the field is optional. |
| Type | Select the type of validation to apply to the component. 1. Minimum number: A user must enter more than this value into the field. 2. Maximum number: A user is unable to enter more than this value into the field. 3. Regular expression pattern: Apply Regular Expression (Regex) validation to the component. |
| Value | Enter the validation critera. 1. Minimum number: Enter a minimum number or character limit for the component. 2. Maximum number: Enter a maximum number or character limit for the component. 3. Regular expression pattern: Enter a valid Regular Expression (Regex) to validate the component. |
| Message | Enter a message to show to the user if the validation criteria is not met. |
Attributes
Add attributes to the component.
- Click Add Attribute.
- Enter a supported attribute Key and Value. See Attributes reference.