Validations
Validations enforce data quality rules on your CRM records. Configure required fields, format checks, and custom validation logic.
Overview
Section titled “Overview”Validations ensure that data entered into the CRM meets your business requirements. Rules are configured by administrators and enforced on both frontend and backend.
Related Modules:
- Settings - Validation configuration
- Contacts - Contact field validations
- Deals - Deal field validations
Validation Types
Section titled “Validation Types”Required Field
Section titled “Required Field”Make a field mandatory:
- Field cannot be empty
- Form cannot submit without value
- Error message displayed
Format Validation
Section titled “Format Validation”Check field format:
| Format | Example |
|---|---|
| [email protected] | |
| Phone | +1-555-123-4567 |
| URL | https://example.com |
| Number | 12345 |
Length Validation
Section titled “Length Validation”Control text length:
- Minimum characters
- Maximum characters
- Exact length
Custom Validation
Section titled “Custom Validation”Advanced rules:
- Regex patterns
- Conditional requirements
- Cross-field validation
Configuring Validations
Section titled “Configuring Validations”Accessing Validation Settings
Section titled “Accessing Validation Settings”- Go to Settings → Validations
- Select the entity type (Contact, Deal, etc.)
- View current validation rules
- Add or edit rules
Creating a Validation Rule
Section titled “Creating a Validation Rule”- Click Add Rule
- Select the field
- Choose validation type
- Configure parameters
- Set error message
- Save
Validation Rule Fields
Section titled “Validation Rule Fields”| Field | Description |
|---|---|
| Entity | What type of record |
| Field | Which field to validate |
| Type | Validation type |
| Condition | When rule applies |
| Message | Error text shown |
| Active | Enable/disable rule |
Entity Validations
Section titled “Entity Validations”Contact Lifecycle Validations
Section titled “Contact Lifecycle Validations”Common contact lifecycle rules:
| Field | Rule | Example |
|---|---|---|
| Format | Must be valid email | |
| Phone | Format | Must be valid phone |
| Company | Required | Cannot be empty |
| Source | Required | Must select source |
Deal Validations
Section titled “Deal Validations”Common deal rules:
| Field | Rule | Example |
|---|---|---|
| Amount | Required | Must have value |
| Close Date | Required | Must set date |
| Account | Required | Must link account |
| Contact | Required | Must link contact |
Contact Validations
Section titled “Contact Validations”Common contact rules:
| Field | Rule | Example |
|---|---|---|
| First Name | Required | Cannot be empty |
| Last Name | Required | Cannot be empty |
| Format | Must be valid if provided | |
| Account | Required | Must belong to account |
Account Validations
Section titled “Account Validations”Common account rules:
| Field | Rule | Example |
|---|---|---|
| Name | Required | Cannot be empty |
| Website | Format | Must be valid URL |
| Phone | Format | Must be valid phone |
Conditional Validations
Section titled “Conditional Validations”Rules that apply in specific situations:
Stage-Based Rules
Section titled “Stage-Based Rules”If deal stage = "Proposal"Then require: Amount, Close DateStatus-Based Rules
Section titled “Status-Based Rules”If contact status = "Qualified"Then require: Budget, TimelineType-Based Rules
Section titled “Type-Based Rules”If activity type = "Meeting"Then require: Start TimeValidation Enforcement
Section titled “Validation Enforcement”Frontend Validation
Section titled “Frontend Validation”Real-time validation in forms:
- Fields validated as you type
- Errors shown immediately
- Form submit blocked if invalid
Backend Validation
Section titled “Backend Validation”Server-side verification:
- All data validated before save
- Prevents bypass of frontend checks
- Returns detailed error messages
Error Messages
Section titled “Error Messages”Customize validation messages:
- Default: “This field is required”
- Custom: “Please enter a valid email address”
- Helpful: “Phone must include country code”
Validation Examples
Section titled “Validation Examples”Email Required for Contacts
Section titled “Email Required for Contacts”Entity: ContactField: EmailType: RequiredCondition: AlwaysMessage: "Email address is required for qualified contacts"Valid Phone Format
Section titled “Valid Phone Format”Entity: ContactField: PhoneType: Format (Phone)Condition: When not emptyMessage: "Please enter a valid phone number"Amount Required for Won Deals
Section titled “Amount Required for Won Deals”Entity: DealField: AmountType: RequiredCondition: When stage = "Won"Message: "Deal amount is required for won deals"URL Format for Website
Section titled “URL Format for Website”Entity: AccountField: WebsiteType: Format (URL)Condition: When not emptyMessage: "Please enter a valid website URL"Managing Validations
Section titled “Managing Validations”Viewing All Rules
Section titled “Viewing All Rules”The validation settings show:
- All active rules
- Entity grouping
- Field and type
- Enable/disable toggle
Editing Rules
Section titled “Editing Rules”- Click on a rule
- Modify settings
- Update error message
- Save changes
Deleting Rules
Section titled “Deleting Rules”- Select the rule
- Click Delete
- Confirm removal
Disabling Rules
Section titled “Disabling Rules”Toggle rules off without deleting:
- Find the rule
- Toggle Active off
- Rule no longer enforced
Best Practices
Section titled “Best Practices”- Start minimal - Add rules as needed
- Clear messages - Help users fix errors
- Test thoroughly - Verify rules work correctly
- Consider workflow - Don’t block common operations
- Document rules - Train team on requirements
- Review regularly - Remove outdated rules
Troubleshooting
Section titled “Troubleshooting”Common Issues
Section titled “Common Issues”| Problem | Solution |
|---|---|
| Can’t save record | Check required fields |
| Format error | Verify data matches pattern |
| Rule not working | Check if rule is active |
| Conflicting rules | Review rule conditions |
See Also: