Validations
This page describes what Property validations are and how they can be set when creating properties.
Last updated
This page describes what Property validations are and how they can be set when creating properties.
Last updated
In the Modeling view under the Technical view, when adding properties, you can also specify validations for these properties.
Property validations are crucial for various native object types to ensure data integrity and compliance with business rules. The types of validations include:
Integer & Float:
Ensure numeric values fall within accepted thresholds (e.g., non-negative quantities).
Confirm inputs expected to be numeric truly are.
String:
Enforce length constraints (minimum or maximum characters).
Validate content against specific formats or regex patterns (e.g., email addresses).
Limit content to permissible characters.
Date & Datetime:
Check values are within an acceptable logical range.
Ensure chronological order for a series of dates (start date comes before end date).
Verify correct formatting according to application standards.
To begin adding a validation, click the property of interest to access the sidebar, then navigate to the settings tab. It's important to note that only properties labeled with a Property Type Native type can have validations set. Once this is confirmed, select the data type that matches one of the previously listed validation types. The process is detailed below.
With the validation tab visible, under the field restrictions, we do see a couple of extra options listed below as:
No validation
Forced validation
Validation options
The first option is as self-explanatory as we would expect. No validation would be applied to the property.
The second option Forced validation displays a restriction option with the ability to add a restriction based on the type of validation selected.
Once the changes have been saved, our validation is applied to the property going forward.
The above example applies to the string validation but the other validation types may defer on how they are presented when the Add+ restriction button is clicked as shown below.
With regards to the date time validations, we have extra options as seen below that are helpful if in need of more refined date time validation.
In the above screenshot, expanded options for date and time validation ensure inputs meet specific criteria. You can specify a date range, enforce a specific format, and apply conditional logic, such as checking if a date falls on a weekday. These features provide robust flexibility for precise data validation in forms or applications, ensuring data integrity and consistency.
The screenshot above offers an in-depth look at the advanced date and time validation options available within the platform. These options extend beyond simple date restrictions to provide a higher degree of control and specificity. Users can define date ranges to ensure inputs fall within a particular timeframe, enforce specific date and time formats to maintain consistency, and apply sophisticated conditional logic—such as requiring that a date be a weekday or excluding holidays. The floating date window does not have a specific or fixed day, week, month, or year with time in regards to the range selection.
The screenshot above demonstrates the advanced date and time validation options available. Users can define specific date ranges, enforce particular date and time formats, and apply conditional logic such as ensuring a date falls on a weekday or excluding holidays. The floating date window feature allows for a flexible range selection without fixed days, weeks, months, or years.
The third and last option Validation options adds a few extra options besides the Restriction option as seen in the second option. The extra options when selected are also applied to the property as seen below.
Overall, property validations across these native object types are fundamental to ensuring that data stored and processed by applications meet defined constraints and business rules. Adding these validations can significantly reduce errors, enhance data quality, and provide a better user experience.
