Input validation

[FRosner]

Problem

We need a flexible way to perform input validation. It should cover cases where we want to

• restrict parameters to a certain set of values
• validate data types (URLs, dates, numbers, etc.)
• can we have special validations depending on the type (e.g. only dates that are mondays or only absolute paths in a path field)?
• can we have custom built validations (e.g. as code)?

It needs to be as flexible as possible to configure (so you don't have to request a new feature but can just add your own validation rules) and it should be possible to apply it based on (a combination) of the following:

• users
• roles
• templates
• instances
• parameter names
• ...?

Having the instanceRegex is actually just a special case of input validation based on the user.

Solution

Maybe we can cover most of these cases by

• allowing the user to define a validation regex for each parameter
• where he can use predefined parameter values (Autofilled parameter values #216)
• with the possibility to define parameter values based on users and groups (Autofilled parameter values #216)