Published at: 2025-10-30

Configure Layout Rules

Layout Rule Definitions

  • Layout rules allow fields to dynamically change (show/hide, become required/read-only, etc.) based on specific conditions during manual record creation/editing.
  • Scope: Layout rules only apply during manual creation/editing and detail page display. They don’t affect imports, OpenAPI, workflow-triggered field changes, or bulk updates.
  • Access path: Preset Object Management/Custom Object Management → Layout Rules

Creating Layout Rules

picture coming soon:

  • Each layout rule applies to one specific layout.
  • Maximum 10 layout rules can be created per layout.
  • Two rule types: Field Control and Page Control.

1.1 Field Control

  • Each rule selects one [Primary Field]. Supported field types: Dropdown, Single-line Text, Multi-line Text, Multi-select, Number, Currency, Date, Time, DateTime, Phone, Email, URL, Boolean, Percentage, and Geolocation components.

picture coming soon:

  • Conditions between groups use OR logic; conditions within the same group use AND logic.
  • Maximum 20 action groups per rule.
  • Field controls can form chains but not circular references.
  • Triggered actions when conditions are met:

    • Show Fields: Multiple fields can be selected.
      Scope: Non-required fields in layout (excluding system fields, owner, owner’s Dept., lifecycle status, lock status, Record Type, master-detail relationships, payment components, check-in components, auto-number fields, formula fields, roll-up summary fields, and fields with parent relationships).
      Effect: Hidden by default, shown when conditions are met.

    • Set Required Fields:
      Scope: Non-required and non-read-only fields in layout (same exclusions as above).
      Effect: Fields become required when conditions are met.

    • Set Read-only Fields:
      Scope: Non-required fields in layout (same exclusions as above).
      Effect: Fields become read-only when conditions are met.

picture coming soon:

1.2 Page Control

  • Controls field visibility/read-only status based on page context (Create/Edit pages).
  • Business use cases:
    1. After-sales fields in Work Order objects only need to appear during service processes, not during initial creation.
    2. Basic information fields in Quotation objects should be editable during creation but locked during editing.
  • Configuration path: Add [Page Control] type rules in object layout rules.

picture coming soon:

  • Configuration guidelines:
    1. On Create pages: Only field hiding can be configured.
    2. On Edit pages: Both hiding and read-only settings are available. Field scope: Same as Field Control exclusions.

Layout Rule List

  • Searchable by rule name.
  • Filterable by associated layout (default: All).
  • Displayed columns: Rule Name, Primary Field (with disabled/deleted status indicators), Layout Rule Type, API Name, Trigger Method, Actions.
  • Available actions:
    • Create
    • Edit (disabled if primary field is disabled/deleted)
    • Enable (shown when rule status = Disabled)
    • Disable (shown when rule status = Enabled)
    • Delete (shown when rule status = Disabled; system prompts “Only disabled rules can be deleted” if attempted on enabled rules)
    • Copy

picture coming soon:

FAQs

1. Why do different Roles see different fields when using the same layout?

When Role A and Role B share a layout but Role A lacks permission for [Field1], any fields hidden by rules using [Field1] as the primary field will remain visible to Role B (who can’t see [Field1]) but hidden from Role A.

2. Why can’t I select certain fields when configuring layout rules?

Possible reasons:
(1) Fields already used as condition fields cannot be controlled fields.
(2) The field isn’t set to [Visible] in the layout.

3. Why can’t I make a field non-required?

If a layout rule sets [Field1] as required, this overrides the field-level optional setting in Field Management.

4. Why can I submit records without filling required fields during editing?

Quick-edit operations on single fields don’t trigger layout rule validations.

5. Why does [Page Control] sometimes appear grayed out?

This depends on layout type - only Create/Edit page layouts support page control rules.

6. Why is Page Control unavailable sometimes?

Gray-out conditions:
(1) For Sub-objects (never support page control)
(2) For main objects:
a. If Create/Edit layouts aren’t enabled: Page Control remains available
b. If enabled:
- Grayed out when selecting detail page layouts
- Available when selecting Create/Edit page layouts

Note: Contact the relevant business team if preset objects behave differently. Locate teams via the “Business Modules and Owners” object in the system.

picture coming soon:

7. Why do hidden fields retain values?

Example: If “Text Field” contains “1”, “Text Field 1” becomes visible and gets a value. Later changing “Text Field” to exclude “1” hides “Text Field 1” but preserves its value.

picture coming soon:

picture coming soon:

8. Sub-object fields appear uneditable or blank in Create/Edit pages

Check if fields are hidden by layout rules or UI events. Note: For Sub-object table components, only field values can be hidden (column headers remain visible as tables don’t support dynamic header rendering).

Submit Feedback