The input constraint option on de domains are a nifty feature to check the user input for valid data. When wrong values are entered a warning is shown and finalizing actions like “Save” and “Execute” are blocked.
Sometimes defaults are being used to help the user to reduce manual input, so even fields with an input constraint could be filled by this.
Here comes the unfortunate part…. the input constraint is being ignored. (sad_face)
Please trigger the input constraints once more when using a finalizing action to still block this if a constraint will fail the validation.
Needs feedback
Trigger input constraint (Domain) before finalizing action
- Andre te Raa
- Arjan Sollie
- Harm Horstman
- Johan van Eijsden
- Edwin Saan
- Gert Groeneveld
- André Romijn
- Hugo Nienhuis
- Geurt
- eurban
- Erwin Ekkel
- Frank Junger
- Remco Kort
- Blommetje
- Arie V
- Rafal Zaluski
- J. de Lange
- mperrott
- Tjerk
- Marc Ferket
- Jefferson Delacruz
- Peter van Leenen
- Shawn Adrian Diño
- WarrenM
- Jason Philip A Mortera
- PeterKeeris
- Maarten
- ArnoW
- Kevin Rosink
- Remco Duijsens
- Marius Korff
- Guido Bijl
- Mark_Plaggenborg
- Johan
- JC Bulaong
- Max Ferket
- Mike C
- nelsontenbrink
- Steffen
- sven.neuteboom
- nick_de_ruiter
- Superhero
- 116 replies
+3
Do you have a practical example of what is currently going wrong? The idea is that only manual input is checked, so not input that is filled in by a default (procedure).
Kind regards,
Remco
+3New→Needs feedback
- Superhero
- 116 replies
The resulting field can still be manually changed as well or even fully entered by hand. The field has a nice RegEx to check for legitimate entry. As the data will only be entered via the GUI, this is a perfect method for valid data and we do not have to also put all these checks in our logic that way.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.