CarlosJuncher03 opened a new issue, #6578: URL: https://github.com/apache/hop/issues/6578
### What would you like to happen? Currently, parameters in Apache Hop are treated as free-text fields. While this offers flexibility, it often leads to execution errors when a user types an incorrect value (e.g., typing "TRUE" instead of "1"). To prevent these errors and remove the need for manual validation steps inside every pipeline, I propose adding a way to define Allowed Values for parameters. Proposed Change Metadata Definition: In the Pipeline/Workflow settings (Parameters tab), add a new column called "Allowed Values" (optional). If left empty: The parameter behaves as a standard text field. If populated (e.g., 0,1 or Incremental,Full): The UI should recognize this as a list of valid options. Run Configuration Dialog (UI): When clicking "Run", the "Value" column in the Run Options dialog should check if there are "Allowed Values" defined. If defined, instead of a text input, a Dropdown (Combo Box) should be rendered, forcing the user to select one of the predefined options. Benefits Data Governance: Ensures that only valid values are passed to the pipeline. Reduced Complexity: Eliminates the need for "Filter Rows" or "Switch/Case" steps just to validate if a parameter is correct. Improved UX: Users don't have to guess or remember the exact strings required; they can simply choose from a list. Fail-Fast: Prevents the pipeline from starting with invalid configurations. Example Use Case A parameter hash_update could be restricted to 0 or 1. Instead of a blank field where a user might type "yes", they would be presented with a dropdown containing only 0 and 1. ### Issue Priority Priority: 3 ### Issue Component Component: Hop Gui -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
