List Page Layout

I. List Page Layout—PC Version

• The PC version list page layout configuration interface is divided into three sections: left, center, and right.
• When clicking the object icon to display the list, create/modify other objects, and need to select this object, the data of this object needs to be displayed on the list page. This provides list page layout and data selection list page, which can be set separately, with the latter defaulting to follow the former.

1.1 Navigation Area

1.2 Content Display Area

• The center of the page is the page preview interface.

1.3 Settings Area

• The right side under component settings allows you to set some common settings for the list page.
  • List Page Layout: Supports setting scene visibility, view settings, quick filters, general buttons, batch operation buttons, quick operation buttons, and the display of summary fields.
  Note: The list page experience is crucial, ensure to configure best practices from a business perspective.

1.3.1 Component Introduction

1. General Components Dashboard/Chart

• The Dashboard can display multiple BI Reports on the list page, including preset and custom dashboards.
• Charts can display BI Reports on the list page.

1. General Components Embedded Page

• Embedded page URLs support variable insertion.
• Embedded pages support height configuration.
  Note: The target website may have security settings for secondary pages, so not all URLs can be displayed in embedded pages. Please confirm that the webpage can be opened normally during the front-end demonstration.

1. Grid Container

• The Grid Container can incorporate other components to organize and compare information.
• The Grid Container can adjust the number of grids and the size ratio between grids.

1.3.2 Button Settings

1. General Buttons

• Can be shown or hidden.
• Set the button position in the button configuration as [List Page General Operations].
• After configuration, the button appears at the top right of the front-end list page. If the button is not exposed, click the top right [···] to see it.

1. Batch Operation Buttons

• Can be shown or hidden.
• Set the button position in the button configuration as [List Page Batch Operations].
• After configuration, when selecting data on the list page, the button appears at the top of the front-end list page.
• Note: Batch buttons remain present as long as data is selected in the list, regardless of whether the preset execution conditions are met. Clicking execute will not perform button operations on data that does not meet the conditions.

1. Quick Button Operations

• Can be shown or hidden.
• Set the button position in the button configuration as [List Page Single Item Operations].
• After configuration, the button appears in the [Operations] column on the right side of the list page data. You can decide the number of exposed and dropdown buttons by adjusting the [Display Exposure] count.

II. List Page Layout—Mobile Version

2.1 Independent Configuration

• Click on the data in the middle preview list to configure the list page settings.
  • Layout settings include: display style, scene settings, field settings, quick filter settings, button settings, summary field settings.
  • Display Style: Data can be set to display as cards or tables on the list page.
  • Scene Settings: Set which default or enterprise-level scenes can be hidden/shown for front-end users on this page, and whether to display scenes as tiles or dropdowns.
  • Quick Filter Settings: Set which fields users can filter on the list page, and whether these fields are exposed to simplify search efficiency.
  • Field Settings: Set which fields are specifically displayed on the list page, directly following the field settings in the scene.
  • Button Settings: Set the visibility of general and batch buttons.
  • Summary Field Settings: Enable settings for fields like numbers, amounts, and exchange rates to perform sum statistics.
• The mobile version provides separate settings for list page layout and data selection list page layout, with the latter defaulting to follow the former settings. The latter can also enable independent configuration for separate settings.

III. Multi-View Display on List Page

3.1 Split-Screen View

• Switching to split-screen view changes the original table to a left-right structure, with the left showing the list and the right showing the data detail page.
• The left list displays as cards, showing only the first three fields in the column settings. Quick filters are not supported in split-screen view.

3.2 Map View

• Fields with location types can switch to map view on the list page (web version only).
• When there are multiple location fields, you can customize the selection.
• Supports front-end customization of field display in map bubble points.

3.3 Calendar View

• Scene/Value: Enterprises can select objects and display them in calendar mode according to date-time fields in the objects. The summary field for each object on the calendar can be customized. The list page layout adds a calendar view, allowing users to arrange and manage business data from a time dimension, making schedule planning simpler and more efficient.
• Function: Display modes include calendar only, calendar + list.
• Select Time Dimension: The selected field must be a date-time type field and a required field (not required in layout settings).
• Configure summary fields when displaying the calendar.
• The front-end calendar supports viewing by day, week, month, and supports common functions like scene, filter, search.

IV. Advanced Settings - Display Specific Record Type in Menu

• Example: The Account object has two record types, Store and Distributor. Some enterprises need to display data of different record types in two separate menus, such as only seeing Distributor type data when entering the Distributor menu, and different Roles see different layout styles when entering different record type menus.
  Note: Menu refers to the long bar of objects displayed after clicking the CRM system on the left.

4.1 Setup Steps

1. Create a custom menu.

1. Associate an object and its record type.

1. In menu template management, the CRM application supports checking the newly created custom menu.

1. Add a new list page layout, the newly added layout in the image is [Store].

1. Set the allocation layout (only effective after the record type is separately configured with a custom menu).

1. At this point, assign the Store layout to various Roles under the Store record type, and assign this record type to the previously created menu. Therefore, you can directly view the Store in the menu, and its layout is displayed according to the previous allocation.

V. List Page Search

5.1 Full Field Search Configuration

5.2 Search Scope

5.3 Filterable Fields

1. Reference Fields
   • a. If the field configuration supports filtering, reference fields can be filtered on the list page.
   • b. Reference fields that reference “lookup fields, Dept. fields, personnel fields, Images fields” do not support filtering (when these fields are selected, “whether to support filtering on the list page” is grayed out as no).
   • c. Reference fields that do not support filtering cannot be used as filter conditions in functions.
   • d. Reference fields have a [whether to support filtering configuration] item, enabling this configuration allows filtering.

1. Calculated Fields
   • a. Calculated fields cannot be stored due to special circumstances, so they do not support filtering; calculated fields support filtering on the data list page, and the comparison operator for filtering calculated fields matches the return value type of the calculated field.
   • b. If the formula references fields on personnel, using the [reference personnel attribute calculated field supports filtering] gray item allows filtering.

VI. Common Issues

1. Can the mobile list page search field set default fields?

2. After selecting a specific record type, why does the mobile list page search retrieve data from other record types, but the PC version displays the corresponding record type data normally?

3. Can list page search fields filter out extra fields based on header fields?

4. Why can’t the “tag” field be selected in the list page filter fields?

5. Does the mobile filter field support unified configuration by the administrator?

The above configuration allows users to adjust themselves on the front end, and after adjustment, there is a personal configuration.

6. Logic for the display fields and order of each list header

I. Example images of each list:

1. List Page, List Page Header Display Fields, Column Settings as shown:

2. Sub-object/Related Object Table (Display Style: Record Type Tile) as shown:

2.1 Admin Console Configuration Location: Primary Object Detail Page -> Sub-object, Related Object Component Settings -> Display Style

2.2 Front-end Display:

3. Sub-object/Related Object Table (Display Style: Record Type Dropdown) as shown:

II. Logic for the display fields and order of each list header:

1. Default Value Logic:

1.1 List Page:

• Takes the scene display fields and order.

1.2 Sub-object/Related Object Table (Display Style: Record Type Tile):

• Fields take the intersection of scene display fields and layout display fields.
• If scene settings header fields = all, order takes the default detail page layout field order.
• If scene settings header fields = specified record type, order takes the default detail page layout field order.
  Note: 1. If grayed out [Sub-object display style is tile mode, header display fields follow the corresponding layout order], fields take the intersection of scene display fields and layout display fields, order takes the corresponding layout order. 2. If grayed out [Detail page sub-object column field order optimization, sub-object fields take scene configuration], fields take the intersection of scene display fields and layout display fields. - If scene settings header fields = all, order takes scene display fields. - If scene settings header fields = specified record type, order takes the record type corresponding detail page layout field order. - ps: If gray function 1 is grayed out again, the display logic follows gray 1. - Gray 1: Sub-object display style is tile mode, header display fields follow the corresponding layout order. - Gray 2: Detail page sub-object column field order optimization, sub-object fields take scene configuration.

1.3 Sub-object/Related Object Table (Display Style: Record Type Dropdown):

• Takes the scene display fields and order.

2. Logic after “Column Settings” is modified:

• Equivalent to personal-level configuration, the default value logic no longer takes effect, taking the column settings after personal-level configuration.

3. Rules for Column Settings:

• “Column Settings” default situation: follows Admin Console -> Scene Management -> Display Field Settings.
• “Column Settings” can configure whether all fields of the object are displayed.
• If personal-level modification of “Column Settings” is done, it no longer follows scene settings.
• If you want to restore following scene management, click [Restore System Default] in column settings to clear personal-level column settings.

6. Where does the default column width set in the scene take effect?

7. What buttons can be configured on the list page? What logic do different buttons follow in different lists?

General Buttons

• The web version supports setting exposed buttons, the mobile version does not support and does not follow web version configuration.

Large List

• Supported buttons: New, Import, Export, Export Images/Attachments, Duplicate Check Tool, Smart Form, Pull Order, Custom Button (Business/UI).

Related List

• Supported buttons: New, Associate, Disassociate, Smart Form, Custom Button (Business/UI).

Data Selection List

• Supported buttons: New.

Batch Buttons

• Web version and mobile version do not support setting button exposure.

Large List

• Supported buttons: Export, Export Images/Attachments, Lock, Unlock, Tag, Change Owner/External Owner, Change/Remove Partner, Add/Remove Related Teams Member, Print, Send Email, Follow, Unfollow, Custom Button (Business, UI).

Related List

• Supported buttons: Export, Export Images/Attachments, Tag, Change/Remove Partner, Print, Send Email, Follow, Unfollow, Custom Button (Business, UI).

Quick Buttons (also known as “Single Item Buttons”)

1. Web version supports setting button exposure, mobile version does not support and does not follow web version configuration.
2. Mobile version only displays single item buttons in card style, not in table style.

Large List

• Supported buttons: Convert, Custom Button (Business, UI).
• ps: Large list mobile independent layout does not support configuring quick buttons.

Related List

• Supported buttons: Custom Button (Business, UI).
• ps: Detail page mobile independent layout - related list independent configuration does not support configuring quick buttons.

Lookup Related

Sub Related