List Page Layout

## 1. List Page Layout — Web - The List Page layout configuration on Web is divided into three areas: left, center, and right. - When clicking an object icon to display a list, or when creating/modifying another object that needs to reference this object, the system shows this object's data in a list. The product provides both a List Page Layout and a Select-Data List Page; each can be configured separately. By default, the Select-Data List follows the List Page Layout. ### 1.1 Navigation Area The left side contains component settings. Supported component types include: - Common components: List Page, Embedded Page, Charts, Navigation Component, Dashboard - Containers: Tab Container, Grid Container - Custom components: user-defined components ### 1.2 Content Preview Area - The center area shows a live page preview. ### 1.3 Settings Area - The right side contains component settings where common List Page configuration options are available: - List Page Layout: configure scene visibility, view settings, quick filters, global buttons, bulk action buttons, quick action buttons, and display of summary fields. Note: List page experience is critical — configure it from a business perspective and follow best practices.

#### 1.3.1 Component Overview 1. Common components — Dashboard / Chart - Dashboard can display multiple BI reports on the List Page, including preset dashboards and custom dashboards. - Chart displays BI reports on the List Page.

2. Common component — Embedded Page - Embedded Page URL supports insertion of variables. - Embedded Page supports configurable height. Note: Target sites may implement cross-page security settings, so not all URLs will display within an embedded frame. Verify the target page opens correctly in a live preview.

3. Grid Container - A Grid Container can host other components to organize and compare information. - You can adjust the number of grid columns and their relative sizes.

#### 1.3.2 Button Settings 1. Global Buttons - You can show or hide these buttons. - In the button configuration, set the button position to "List Page Global Actions". - After configuration, the button appears in the top-right of the front-end List Page. If it is not visible, click the top-right "···" menu to find it. 2. Bulk Action Buttons - You can show or hide these buttons. - In the button configuration, set the button position to "List Page Bulk Actions". - After configuration, when items are selected in the list, the buttons appear above the list on the front end. - Note: Bulk buttons remain available whenever any records are selected, regardless of whether all selected records meet execution conditions. Records that do not satisfy the preconditions will not be affected when the action runs. 3. Quick Action Buttons (per-row) - You can show or hide these buttons. - In the button configuration, set the button position to "List Page Row Actions". - After configuration, these buttons appear in the Actions column on the right of each row. Use the "Expose count" setting to control how many buttons show as tiles and how many go into a dropdown.

## 2. List Page Layout — Mobile - By default, the Mobile List Page inherits the Web layout. You can enable independent Mobile layout configuration. ### 2.1 Independent Mobile Configuration - Click a record in the preview area to configure List Page settings. - Layout settings include: Display Style, Scene Settings, Field Settings, Quick Filter Settings, Button Settings, Summary Field Settings. - Display Style: choose Card or Table presentation on the list. - Scene Settings: control which default or tenant-level scenes are visible to front-end users and whether scenes display as tiles or in a dropdown. - Quick Filter Settings: decide which fields users can filter by on the list and whether those filters are exposed, improving search efficiency. - Field Settings: select which fields display in the list; this follows the scene's field configuration. - Button Settings: configure visibility for Global and Bulk buttons. - Summary Field Settings: enable summation for numeric, currency, and rate fields. - Mobile supports separate configuration for List Page Layout and Select-Data List Page; the latter follows the former by default but can be configured independently.

## 3. Multiple List Views A simple list may not meet every user need. Users might need to compare different datasets, view geographic locations on a map, or manage records by time on a calendar. The system offers multiple list views. ### 3.1 Split-Screen View - In Split-Screen View, the table becomes a two-column layout: the left shows the list, the right shows the record detail. - The left list displays as cards and only shows the first three fields from the column settings. Quick filters are not supported in Split-Screen View.

### 3.2 Map View - If the object contains geolocation fields, you can switch to Map View on the List Page (Web only). - When multiple location fields exist, you can choose which field to map. - Configure which fields appear in the marker pop-up bubbles on the map.

### 3.3 Calendar View - Use case/value: Administrators can select an object and display records on a calendar based on a date/time field. The calendar event summary fields are configurable. Calendar view helps users arrange and manage business records by time, simplifying scheduling. - Modes: Calendar-only or Calendar + List. - Time dimension: The chosen field must be a DateTime-type field and must be required at the field level (not just required in a layout). - Configure the calendar event summary field. - Front-end calendar supports Day / Week / Month views, and supports scenes, filters, and search. - List Page Layout: add Calendar View to the List Page layouts.

## 4. Advanced — Expose Specific Record Types in Menu Custom menus can now include specific Record Types. That means a menu item can show an object filtered to a particular Record Type and present that Record Type with its own icon. - Example: The Account object has two Record Types: Store and Distributor. Some organizations want separate menu entries for each Record Type so that selecting the Distributor menu only shows Distributor records. Different Roles may also see different layout styles for the same Record Type. Note: "Menu" refers to the long left navigation column listing CRM objects.

### 4.1 Steps 1. Create a custom menu.

2. Associate an object and select a Record Type.

3. In Menu Template Management, check the newly created custom menu for the CRM app.

4. Add a new List Page Layout — the example shows a new layout named "Store".

5. Assign layouts (this only applies if you configured a Record Type as a separate custom menu).

6. Assign the Store layout to the roles for the Store Record Type and link the Record Type to the previously created menu. The menu will now show Store and use the assigned layout when opened.

## 5. List Page Search ### 5.1 Global (All-Field) Search Configuration - In Admin Console → Object Management → Preset/Custom Object → Basic Information, enable "Global Search". The front-end filter will include the "All Fields" option.

### 5.2 Search Scope - The field types currently available in the List Page field search dropdown include: Auto-number, Single-line/Multi-line Text, Rich Text, Mobile, Email, URL, Lookup (reference), and Geolocation.

### 5.3 Filterable Fields - Most fields support filtering. Two special cases are Reference (Lookup) fields and Formula (Calculated) fields:

1. Reference (Lookup) fields a. A Reference field can be filtered on the List Page only if its field configuration enables "Support filtering". b. If the Reference field points to a Lookup field type of "Lookup-to-Lookup", Departments, Users, or Images, it does not support filtering (the "Support filtering on List Page" option will be disabled). c. Reference fields that do not support filtering cannot be used as filter conditions in functions. d. The Reference field has a configurable "Support filtering" switch — turning it on enables filtering.

2. Formula (Calculated) fields a. Some calculated fields are not persisted to storage in certain scenarios, so they cannot support filtering. Calculated fields that are filterable on the data list will use comparison operators based on the field's return type. b. If a formula references fields on User records and the tenant has enabled the "Calculated fields referencing user attributes support filtering" beta, those formula fields can be filtered.

## 6. FAQs Q1. Can the default search field on Mobile be set? - The search default is the Primary Attribute field. If a user switches to a different field, the system remembers that choice and will default to the user's last-used field next time. Q2. After selecting a specific Record Type, Mobile List Page search returns other Record Types, while Web shows the correct Record Type data. Why? - Mobile All-Field search currently performs a global search without applying other conditions such as scene or filters. For Custom Objects, this can be mitigated by requesting the beta feature: "Mini Program: Object Data List Search V2 — Custom Objects". Preset objects are not supported currently. Q3. Can List Page search fields be filtered by the table header fields? - Search fields are the object's filterable fields, not controlled by table header visibility. Q4. Why can't I find the "Tags" field in the List Page filters? - Confirm whether the "Hide Tag Filtering" beta is enabled (tags made invisible). If needed, request a beta rollback. Q5. Can an admin centrally configure Mobile quick filters? - Yes. Path: List Page Layout → Mobile Independent Layout → Quick Filter Settings. Definitions: - "Enable Quick Filters": whether filter fields are exposed. - "Fields in the Filter Page": which fields are set as filter fields. Note: Users can adjust these on the front end; changes become personal configuration. Attention points: 1. Web List Page Layout quick filters are independent from Mobile and do not synchronize. 2. If Mobile independent layout is not enabled, the Mobile view defaults to the Mobile summary layout fields. 3. If tenant-level configurations don't appear to take effect, advise users to click "Restore System Default" in their personal settings.

Q6. How are header fields and their order chosen for list tables? A. Example screenshots: 1) List Page — header display and column settings:

2) Sub-object / Related-object table (display style: Record Type Tile): - Admin path: Primary Object detail page → Sub-objects / Related Objects component settings → Display Style

2.2 Front-end presentation:

3) Sub-object / Related-object table (display style: Record Type Dropdown):

B. Rules for header fields and order: 1. Default logic: 1.1 List Page: - Use the scene's display fields and order. 1.2 Sub-object / Related-object table (display style: Record Type Tile): - Fields are the intersection of Scene display fields and Layout display fields. - If the scene header fields = All, the order follows the default detail page layout field order. - If the scene header fields = Specific Record Type, the order follows the default detail page layout field order for that Record Type. Notes: 1. If the tenant enabled the beta "Sub-object display style Tile — header fields follow the corresponding layout order", the fields are the intersection of scene and layout fields and the order follows the corresponding layout. 2. If the tenant enabled the beta "Detail page sub-object column order optimization — sub-object fields follow scene configuration", the fields are the intersection of scene and layout fields: - If scene header fields = All, order follows the scene fields. - If scene header fields = Specific Record Type, order follows the detail page layout field order for that Record Type. If both betas were toggled in sequence, the first-enabled beta determines behavior. 1.3 Sub-object / Related-object table (display style: Record Type Dropdown): - Use the scene's display fields and order. 2. After a user modifies "Column Settings": - This becomes a personal-level configuration. The default logic no longer applies; the list uses the user's personal column settings. 3. Rules for "Column Settings": - By default, Column Settings follow Admin Console → Scene Management → Display Fields. - Column Settings can control which fields of the object are visible. - If a user has modified Column Settings personally, it will not follow the scene settings. - To revert to scene-managed behavior, click "Restore System Default" in Column Settings to clear the personal configuration.

### 6. Where do the default column widths set in Scenes apply? - Scene-configured field widths apply only to object lists (main lists, related lists, select-data lists — any place with scenes). New/edit pages and sub-tables do not follow these widths. Notes: 1. New/Edit page table field widths cannot be uniformly set and use default widths. Users can resize columns personally; that setting is stored in browser cache. Clearing cache restores defaults. 2. If widths don't seem to apply, personal column-width settings likely exist. In the object's main list, restore default column widths and re-check.

### 7. Which buttons are configurable on List Pages? How do different button types display across lists? Global Buttons - Web supports exposed (visible) buttons; Mobile does not use Web-exposed configuration. Big List (Main List) - Supported buttons: New, Import, Export, Export Images/Attachments, Duplicate Detection, Smart Forms, Pull Order, Custom Buttons (Business/UI) Table: Big List button behavior | | Web | Mobile | |---|---|---| | Big List — Mobile independent layout NOT enabled | Exposed buttons / order / expose count follow Web config | Buttons/order follow Web config; Mobile does not support exposed buttons | | Big List — Mobile independent layout enabled | Exposed buttons / order / expose count follow Web config | Buttons/order follow Mobile independent config; Mobile does not support exposed buttons | Related Lists - Supported buttons: New, Link, Unlink, Smart Forms, Custom Buttons (Business/UI) Table: Related list button behavior | | Web | Mobile | |---|---|---| | Detail Page Web — Related list independent config NOT enabled | The New button is exposed by default; other buttons are under "More" | Same as Web | | Detail Page Web — Related list independent config enabled | Exposed buttons / order / expose count follow the related-list independent config | Buttons/order follow Web related-list independent config; Mobile does not support exposed buttons (the first button is exposed by default) | | Detail Page Mobile — Related list independent config NOT enabled | Buttons/order/expose count follow Web related-list independent config | Buttons/order follow Web related-list independent config; Mobile does not support exposed buttons (first button exposed) | | Detail Page Mobile — Related list independent config enabled | Buttons/order/expose count follow Web related-list independent config | Buttons/order follow Mobile related-list independent config; Mobile does not support exposed buttons (first button exposed) | Select-Data List - Supported buttons: New Table: Select-data list button behavior | | Web | Mobile | |---|---|---| | Select-data list Web — no independent config | Exposed buttons / order / expose count follow object main list Web config | Buttons/order follow object main list Web config; Mobile does not support exposed buttons (first button exposed) | | Select-data list Web — independent config enabled | Exposed buttons / order / expose count follow object main list Web config | Buttons/order follow object main list Web config; Mobile does not support exposed buttons (first button exposed) | | Select-data list Mobile — no independent config | Exposed buttons / order / expose count follow object main list Web config | Buttons/order follow object main list Mobile config; Mobile does not support exposed buttons (first button exposed) | | Select-data list Mobile — independent config enabled | Exposed buttons / order / expose count follow Select-data list independent config | Buttons/order follow Select-data list independent config; Mobile does not support exposed buttons (first button exposed) |

Bulk Buttons - Neither Web nor Mobile support exposed bulk buttons. Big List — Bulk supported actions: Export, Export Images/Attachments, Lock, Unlock, Tag, Change Owner / External Owner, Change/Remove Partner, Add/Remove Related Team Members, Print, Send Email, Follow, Unfollow, Custom Buttons (Business/UI) Table: Bulk buttons behavior | | Web | Mobile | |---|---|---| | Big List — Mobile independent layout NOT enabled | Buttons/order follow Web config | Buttons/order follow Web config | | Big List — Mobile independent layout enabled | Buttons/order follow Web config | Buttons/order follow Mobile independent config | Related List — Bulk supported actions: Export, Export Images/Attachments, Tag, Change/Remove Partner, Print, Send Email, Follow, Unfollow, Custom Buttons (Business/UI) Table: Related-list bulk behavior | | Web | Mobile | |---|---|---| | Detail Page Web — related list independent config NOT enabled | Buttons/order follow object main list config | Buttons/order follow object main list config | | Detail Page Web — related list independent config enabled | Buttons/order follow Web related-list independent config | Buttons/order follow Web related-list independent config | | Detail Page Mobile — related list independent config NOT enabled | Buttons/order follow Web related-list independent config | Buttons/order follow Web related-list independent config | | Detail Page Mobile — related list independent config enabled | Buttons/order follow Web related-list independent config | Buttons/order follow Mobile related-list independent config |

Quick Action Buttons (aka Row Actions) 1. Web supports exposed row-action buttons; Mobile does not and does not use Web-exposed configuration. 2. On Mobile, row actions appear only in Card style; Table style does not show row actions. Big List — Quick Action supported: Convert, Custom Buttons (Business/UI) Note: Big List Mobile independent layout does not support quick action configuration. Table: Quick action behavior | | Web | Mobile | |---|---|---| | Big List — Mobile independent layout NOT enabled | Exposed buttons / order / expose count follow Web config | Exposed buttons / order / expose count follow Web config | | Big List — Mobile independent layout enabled | Exposed buttons / order / expose count follow Web config | Exposed buttons / order / expose count follow Web config |

Related Lists — Quick Action supported: Custom Buttons (Business/UI) Note: Detail Page Mobile independent layout — related-list independent config does not support quick actions. Lookup-related Table: Lookup single-row button behavior | | Web | Mobile | |---|---|---| | Detail Page Web — related list independent config NOT enabled | Buttons and expose count follow object main list config | Buttons and expose count follow object main list config | | Detail Page Web — related list independent config enabled | Buttons/order/expose count follow Web related-list independent config | Single-row buttons are not shown | | Detail Page Mobile — related list independent config NOT enabled | Buttons/order/expose count follow Web related-list independent config | Single-row buttons are not shown | | Detail Page Mobile — related list independent config enabled | Buttons/order/expose count follow Web related-list independent config | Single-row buttons are not shown | Sub-Related (From Related) Table: From-related button behavior | | Web | Mobile | |---|---|---| | Detail Page Web — related list independent config NOT enabled | Buttons follow object main list config; exposed buttons are not supported (exposes do not inherit from object main list) | Buttons and expose count follow object main list config | | Detail Page Web — related list independent config enabled | Buttons/order/expose count follow Web related-list independent config | Single-row buttons are not shown | | Detail Page Mobile — related list independent config NOT enabled | Buttons/order/expose count follow Web related-list independent config | Single-row buttons are not shown | | Detail Page Mobile — related list independent config enabled | Buttons/order/expose count follow Web related-list independent config | Single-row buttons are not shown |