Data Validation
Workstation validates CRM data through the Properties and Pipelines settings. The old standalone Validations screen is no longer the main configuration path.
Use the narrowest rule that matches the business requirement.
Validation options
Section titled “Validation options”| Requirement | Configure it in | Example |
|---|---|---|
| Always validate one field | Settings → Properties → property → Rules | Deal amount must be at least 0 |
| Require or set fields when another value matches | Settings → Properties → Conditional logic | If Deal type is Renewal, require Contract term |
| Require fields only when entering a process stage | Settings → Pipelines → Pipeline Rules | Require Close date before entering Proposal |
These rules can work together. A value must satisfy every applicable rule before it is saved or a stage move completes.
Property rules
Section titled “Property rules”Property rules belong to a native or custom property and are always evaluated where that property is supported.
Available checks depend on the field type:
- Required values
- Text length, whitespace, regular expressions, and uniqueness
- Numeric minimums, maximums, decimals, and uniqueness
- Phone default country code
- Future, past, weekday, or ranged dates
- Minimum or maximum choices for multi-select fields
- Semantic checks for email, URL, number, currency, date, boolean, and multi-select payloads
Open Settings → Properties, choose an object, select a property, and open Rules.
Conditional logic
Section titled “Conditional logic”Conditional logic uses one controlling property and one or more actions. Depending on field type, conditions can test selected values, text matching, or whether a value is known.
A matching rule can:
- Show a dependent field
- Show and require a dependent field
- Set or overwrite a dependent value
- Set a value only when the dependent field is empty
Rules run top to bottom. If multiple matching rules set the same property, the lower rule wins.
Conditional visibility improves forms, but backend validation remains the source of truth. API calls and supported bulk updates cannot bypass required and typed-value checks.
See Properties for the full workflow.
Pipeline-stage requirements
Section titled “Pipeline-stage requirements”Contact and Deal pipelines can require standard and custom fields before entering a stage.
- Open Settings → Pipelines.
- Select a Contact or Deal pipeline.
- Open Pipeline Rules.
- Select the destination stage under Conditional Stage Properties.
- Choose the fields required to enter that stage.
This is the right choice when a field is optional early in the process but necessary later. See Pipelines and Stages.
Imports and bulk changes
Section titled “Imports and bulk changes”The import wizard validates mapped rows before the import begins and shows valid rows, errors, and a data preview. Invalid rows are skipped when valid rows can continue.
Supported bulk updates validate records individually. A bulk operation may therefore update valid records while reporting failures for records that do not satisfy the applicable rules.
Planning rules
Section titled “Planning rules”- Use Required sparingly. A permanently required field affects creation, editing, imports, integrations, and bulk actions.
- Prefer stage requirements for information that becomes necessary only later.
- Use conditional logic when the requirement depends on another value rather than process stage.
- Write labels and descriptions that make the expected format clear before an error occurs.
- Check a property’s Usage panel before changing its type, options, or rules.
- Test create, edit, bulk update, import, and stage movement after changing important requirements.