Core
Input
Overview:
The Input Configuration block serves as a customizable input handler that allows users to define parameters for user inputs in a versatile manner. This block supports various types of input selections, making it adaptable for different application contexts.
Inputs & Outputs
| I/O | Feature | Type | Simple Explanation |
|---|---|---|---|
| input | input_name | string | A name or label for the input, which identifies this parameter in various views. |
| input | test_value | string | A preset value used as a default when running the flow manually. |
| input | input_type | selector | Determines the type of input field displayed to users; options include text, number, boolean, file, audio. |
| output | {input_value} | string | The actual value received from the user through this configuration; defaults to the test_value specified above. |
Use Cases
This block can be beneficial in numerous scenarios:
- Form Creation: Simplifies building dynamic forms where each field can be customized easily via names and types.
- User Input Handling: Ideal for applications requiring varied data entry formats (like uploading files or entering numbers) while maintaining consistent backend handling.
- Testing Flows: Facilitates manual testing by allowing testers to set default values before initiating flows without needing full data integration.
- Data Collection: Efficiently collects information from end-users on platforms like surveys or feedback forms with clearly labeled inputs.
In conclusion, whenever there’s a requirement to gather diverse forms of user inputs seamlessly and flexibly within an application context, the Input Configuration block provides a streamlined solution!
Was this page helpful?