Using existing validators
Last updated
Last updated
KASKO Frontend Framework utilizes most of with the addition of some KASKO validators. These validation rules are defined in .
Note: See "" for more information how to add product-specific custom validators.
Available data types (variables will be converted prior to sending to the API, but are not validated in frontend):
Alpha-numeric characters and dash is allowed.
Alpha-numeric characters, dash and forward slash is allowed.
Alpha-numeric characters and space is allowed.
Fails validation if the given input matches a value in the blacklist.
1hello
No
This is my hello text.
No
Fails validation if the given input exactly matches a value in the blacklist (full words).
1hello
Yes
This is my hello text.
No
Check if the input value is divisible by X without a remainder.
123
No
12300
Yes
Check if each word in the input is capitalized.
hello World
No
Hello World
Yes
Input must be false to pass the validation.
Input must be false if additional field match the given value.
Input under validation is required if all other (given) fields are false.
Input under validation is required if all other (given) fields match the given values.
Input must be true to pass the validation.
Input must be true if additional field match the given value.
Input must be true if all other (given) fields match the given values.
Check if input doesn't have more than (given) limit of sequential characters.
Check if input has a valid iban code, for this validation we are using 3rd party library.
First check is done by our framework:
can contain only A-Z and 0-9 (letters and numbers)
Next are 3rd party library checks:
if is, then check against selected country's IBAN length
check against selected country's IBAN structure
and then check and calculate MOD 97-10 of the passed IBAN as specified in ISO7064
Check if input has a valid bic code.
Code should consist from 8 to 11 chars. First 6 chars should be A-Z, next 2 should be A-Z or 0-9 and then last 3 are optional which should be A-Z or 0-9.
Check if input has a valid IMEI code - consists of 15 digits and is valid using Luhn formula.
Check if input has a valid phone number
Check if input value (date) is between the given time interval.
value must be between time period trip_start_date and +91 days
Check if input value (date) is between the given time interval or equal.
Check if input value (date) is between the given time interval.
value must be between time period -100 years and policy_start_date
Check if input value (date) is between the given time interval or equal.
Fails validation if the given input matches a value in the blacklist. Validation is case sensitive and blacklisted keyword can be a sentence.
1hello
Yes
This is my hello text.
No
sometext
Yes
Need to write some text.
No
. hello world
No
Check if each letter in the input is capitalized.
Input value (string) can't have all capital letters.
HeLLo WorLD
Yes
HELLO WORLD
No
Input is validated against the provided rule which contains two arguments - a comparison operator and year.
Check if the input is a valid date.
Check if the input is a valid datetime.
check if first 2 chars from IBAN is registered in 3rd party library's supported country codes list. You can find this list .