Published at: 2025-10-30

Detail Page Layout


Detail Page Layout - Web

I. Detail Page Layout - Web

  • The Web detail page layout configuration interface consists of three sections from left to right: Navigation Area, Preview Area, and Settings Area.

picture coming soon:

(1) The left side of the layout configuration interface primarily contains two sections: Components and Field Information.

  • Supported component types include:
    • General Components: Platform-preset universal components available for all custom objects
      • Title and Buttons: Configure visibility of labels and buttons, including the number of exposed buttons
      • Summary Information: Display key information on the detail page with configurable fields
      • Others: Related Teams, Follow-Up Activity, Details, Revision History, Process List, Approval List, Embedded Pages, Chart Components
    • Business Components: Includes related objects, Sub-objects, and SFA preset components
      • Sub-object Components: Use list page configuration when independent configuration is disabled
    • Containers: Tab Container, Grid Container
  • Supports adding and managing field visibility
    • Field Information includes 32 supported field types and 3 scenario-based field groups (refer to: Field and Field Dependency Relationships)

1.2 Preview Area

The middle section displays the page preview: 1. Drag and drop components directly onto the page for configuration 2. Configure field visibility

1.3 Settings Area

Note: The right side of the layout configuration interface includes Global Settings and Component Settings.

1.3.1 Global Settings

Global Settings consist of Basic Information and UI Events.

  • Basic Information Settings:
    • Layout Name: Customizable layout name
    • API Name: System-generated (non-editable)
    • Layout Description: Custom description
    • Layout Templates: Supports Top-Bottom and Left-Right layouts
      Note: Top-Bottom layout hides the classic right-side Related Teams card area
    • JS Plugins: Supports Web and mobile detail page plugins
    • Field Alignment: Left, Center, or Top-Bottom alignment

picture coming soon:

picture coming soon:

  • UI Event Settings: Execute functions to modify interface information through triggered events > Notes: > 1. UI Events only affect Create/Edit pages (actual changes require saving) > 2. Fully supported for custom objects; partially supported for preset objects (Leads, Account, Order/Order Products, Opportunity 2.0/Opportunity 2.0 Line Items) > 3. Available in Enterprise and Group Editions only

    • Data Update Events:
      • Field Events: Trigger custom functions to update Primary Object or Sub-object data when field values change (on blur)
        • Use Case: Auto-populate shipping address from selected Account when creating an Order
        • Configuration: UI Events → Add Data Update Event → Select Field Event
      • Sub-object Events: Update Primary/Sub-object data when adding/editing/deleting Sub-objects (requires Sub-object relationship)
        • Use Case: Apply discount rates to Order Products based on customer tier
        • Configuration: UI Events → Add Data Update Event → Select Sub-object Event (trigger conditions: Add/Edit/Delete)
      • Page Load Events: Update data when page loads
        • Use Case: Auto-create E-Signature signers based on business data
        • Configuration: UI Events → Add Data Update Event → Select Page Load Event

picture coming soon:

  • Validation Events:
    • Trigger custom validation when field values change (on blur)
      • Use Case: Real-time validation for phone/email format errors
      • Configuration: UI Events → Add Validation Event

picture coming soon:

1.3.2 Component Settings

  1. Title Card Settings
    • Template Selection:
      • Basic: Toggle visibility
      • Advanced: Configure field arrangement, colors (configure parameters in Field Settings)
    • Button Management: Show/hide buttons and set exposed count (hover to configure). Buttons set to [Detail Page] position appear here.
    • Configure basic field/component information and visibility conditions
  2. Summary Field Management
    • Control visibility of summary fields (hover to configure)
  3. Details Section
    • Configure field visibility and data scope when Create/Edit page layout is disabled
  4. Business Components (Related Objects/Sub-objects)
    • Show only populated lists
    • Display style for Record Types
    • Independent Sub-object layout configuration
    • Pre-set data filters

picture coming soon:

  1. Independent Configuration
    • Scenario visibility
    • Sub-object operation buttons:
      • 5.1 General Buttons: Not supported
      • 5.2 Batch Operations: 1) Toggle visibility 2) Set button position to [List Page Batch Operations] in Admin Console 3) Buttons appear above Sub-object lists when data is selected
        Note: Batch buttons remain visible regardless of execution conditions (non-compliant data won’t execute)
      • 5.3 Single-Record Operations: 1) Toggle visibility 2) Set button position to [List Page Single Operation] in Admin Console 3) Buttons appear in the [Actions] column

picture coming soon:

II. Detail Page Layout - Mobile

Note: Mobile layouts can inherit Web configurations or be configured independently.

  1. Inheriting Web layout synchronizes summary fields and detail settings
  2. Supports independent mobile layout configuration
  • Summary Fields: Manage visibility (hover to configure)
  • Navigation Container: Configure tabs (sorting, custom tabs) and component properties
    > Notes: > - Sub-objects can enable independent configuration (defaults to Web settings if disabled) > - Mismatched tabs occur when users manually configure tabs (user-specific). Reset via [Navigation Settings] → [Restore Defaults]
  • Button Management:
    • Toggle visibility
    • Set button position to [Detail Page] in Admin Console
    • Buttons appear at the bottom of mobile detail pages

III. FAQs

1. Why can’t I configure field styles on the detail page?

Field style configuration is disabled when Create/Edit page layout is enabled for the object.

2. Why don’t Web-configured buttons appear on mobile?

Mobile independent layout must be enabled.

3. How to disable in-line field editing (Quick Edit/Real-Time Edit)?

Request the “Disable Real-Time Editing for All Objects” feature (affects all objects).

4. Can table components in form layouts have locked rows?

No. Tables scroll with the page and don’t support row/column locking.

Admin Console → Related Object Detail Page Layout → Independent Related List Configuration
Note: Tile-style summaries aggregate all page data. If independent layout is disabled, summaries inherit list page configurations.

picture coming soon:

6. Why don’t renamed default layouts reflect in list pages?

Default name changes require updating translated values via the language globe icon.

picture coming soon:

7. Which components support quick navigation via floating components?

To-Do Items, My Orders, Charts (Sales Briefing, Lead Conversion, Rankings), Scenarios, Dashboard, Custom Components, Announcements, Tasks, Calendar, Menu Entries.

8. Why don’t renamed tab objects update on mobile?

Tab names default to object names. Mobile layouts don’t inherit Web tab name changes.

Web displays tab names; mobile displays component names. Translate component names under “Detail Page Layout → Object Name → Page Components”.

picture coming soon:

picture coming soon:

10. Why don’t field/option colors apply to label fields?

Label colors are fixed and don’t inherit field option colors.

Only works with “Record Type Dropdown” display style (not supported in Tile style).

picture coming soon:

Single-record button exposure isn’t supported for related lists.

Submit Feedback