Appearance
Rules overview
Learn how object rules control pages and validate data before save.
Business value
Object rules reduce manual entry errors and adapt pages to business conditions. You can control field visibility, required and read-only states, and save validation. This aligns object pages with the Business Process.
Core concepts
| Rule Type | Problem solved | Effective area |
|---|---|---|
| Layout rule | Shows, requires, locks, or hides fields by condition | Create, edit, and details pages |
| Validation Rules | Checks whether data meets requirements before save | Web page save action |
Rule types
Layout rules
Layout rules control field states on a page. Use a controlling field, page context, or business condition to show, hide, require, or lock fields.
Typical examples:
- Show Unified Social Credit Identifier when Account Type is Enterprise Account.
- Require the sign-off time when the delivery Business Status is Signed.
- Set fields to read-only by Business Status on a details page.
Validation Rules
Validation Rules check field values before users save data. When the formula returns true, the system blocks the save or displays a warning.
Typical examples:
- End Date cannot precede Start Date.
- A mobile number is required.
- A discount rate cannot exceed the allowed range.
- Completion notes are required for completed records.
How rules work
- Layout rules affect the page experience first. They determine what users see and can edit.
- Validation Rules affect the save result. They determine whether submitted data can be saved.
- Field permissions always apply. A page rule cannot expose a field that the user cannot access.
Choose a rule
| Requirement | Recommended rule |
|---|---|
| Show a field by condition | Layout rule |
| Require a field by condition | Layout rule, plus a validation rule for critical data |
| Validate dates, amounts, or status before save | Validation Rules |
| Protect a sensitive field | Field permissions, not only a layout rule |
| Control bulk-import quality | Required fields, uniqueness, import rules, and Validation Rules |
Recommendations
- Confirm the business goal before selecting a Rule Type.
- Use layout rules for page-experience requirements.
- Use Validation Rules for minimum data-quality requirements.
- Do not rely only on client-side display controls for critical validation.
- Test rules with different roles and Record Type values before release.