<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Validations on Forio</title><link>/docs/freshforms/macros/validations/</link><description>Recent content in Validations on Forio</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright (c) 2025 Forio</copyright><lastBuildDate>Sat, 13 Dec 2025 10:52:25 -0600</lastBuildDate><atom:link href="/docs/freshforms/macros/validations/index.xml" rel="self" type="application/rss+xml"/><item><title>Overview</title><link>/docs/freshforms/macros/validations/overview/</link><pubDate>Sat, 13 Dec 2025 10:52:25 -0600</pubDate><guid>/docs/freshforms/macros/validations/overview/</guid><description>&lt;p&gt;Welcome to &lt;strong&gt;FreshForms Validation Documentation!&lt;/strong&gt;
This page provides an overview of the various validation rules applied when using FreshForms. Below you&amp;rsquo;ll find detailed information about the different validation types, the associated rules, and how to avoid common errors.&lt;/p&gt;</description></item><item><title>Form Name Validation</title><link>/docs/freshforms/macros/validations/form-name-validation/</link><pubDate>Sat, 13 Dec 2025 10:52:25 -0600</pubDate><guid>/docs/freshforms/macros/validations/form-name-validation/</guid><description>&lt;p&gt;This validation rule ensures that form names are &lt;strong&gt;written entirely in lowercase&lt;/strong&gt; and &lt;strong&gt;do not contain special characters&lt;/strong&gt;. This is crucial to maintain consistency and prevent technical issues related to improper naming conventions.&lt;/p&gt;</description></item><item><title>Field Name Validation</title><link>/docs/freshforms/macros/validations/field-name-validation/</link><pubDate>Sat, 13 Dec 2025 10:52:25 -0600</pubDate><guid>/docs/freshforms/macros/validations/field-name-validation/</guid><description>&lt;p&gt;This validation rule ensures that &lt;strong&gt;field names&lt;/strong&gt; within your form are &lt;strong&gt;written in lowercase&lt;/strong&gt; and &lt;strong&gt;contain no special characters&lt;/strong&gt;. Similar to form names, field names must adhere to this rule to maintain consistency.&lt;/p&gt;</description></item><item><title>Required Validation</title><link>/docs/freshforms/macros/validations/required-validation/</link><pubDate>Sat, 13 Dec 2025 10:52:25 -0600</pubDate><guid>/docs/freshforms/macros/validations/required-validation/</guid><description>&lt;p&gt;Certain fields in your form may be marked as &lt;strong&gt;required&lt;/strong&gt;. This validation rule ensures that users &lt;strong&gt;fill out&lt;/strong&gt; these fields before submitting the form.&lt;/p&gt;</description></item><item><title>Alphanumeric / Numeric / Email Validation</title><link>/docs/freshforms/macros/validations/alphanumeric-/-numeric-/-email-validation/</link><pubDate>Sat, 13 Dec 2025 10:52:25 -0600</pubDate><guid>/docs/freshforms/macros/validations/alphanumeric-/-numeric-/-email-validation/</guid><description>&lt;p&gt;These validation rules ensure that user input adheres to the correct &lt;strong&gt;data type&lt;/strong&gt;. You can enforce that fields accept only &lt;strong&gt;letters and numbers&lt;/strong&gt;, &lt;strong&gt;numeric values&lt;/strong&gt;, or &lt;strong&gt;email addresses&lt;/strong&gt;.&lt;/p&gt;</description></item></channel></rss>