List Page Layout

1. List Page Layout — Web

• The list page layout configuration on the Web is divided into three sections: left, center, and right.
• When a record list displays after clicking an object icon, or when another object references this object during create/edit and needs to show this object’s list for selection, the system uses the list page layout and the “select-data list” layout. These two layouts can be configured separately; by default the select-data list follows the primary list layout.

1.1 Navigation Area

The left column contains available components. Supported component types: - Generic components: List, Embedded Page, Chart, Navigation Component, Dashboard - Containers: Tab Container, Grid Container - Custom components: user-defined components

1.2 Content Preview Area

• The center area shows a live preview of the page.

1.3 Settings Area

• The right column shows component settings and common list page options.

• List page layout: configure scene visibility, view settings, quick filters, global buttons, bulk action buttons, quick action buttons, and summary field display.

Note: List page usability is critical. Configure layouts from a business perspective and follow best practices.

1.3.1 Component descriptions

1. Generic components: Dashboard / Chart - Dashboard can display multiple BI reports on a list page, including preset dashboards and custom dashboards. - Chart displays a BI report on the list page.

1. Generic component: Embedded Page - The embedded page URL supports variable injection. - You can configure the embedded page height.

Note: Some target websites have secondary security restrictions and cannot be embedded. Verify the URL renders correctly during a front-end demo.

1. Grid Container - A Grid Container can host other components to organize and compare information. - You can adjust the number of grid columns and the proportion between columns.

1.3.2 Button settings

1. Global buttons - Can show or hide. - Set button position to “List Page Global Actions”. - After configuration, the button appears at the top-right of the front-end list page. If it’s not shown directly, click the top-right “···” menu to find it.

2. Bulk action buttons - Can show or hide. - Set button position to “List Page Bulk Actions”. - After configuration, when users select records in the list, bulk action buttons appear above the list. - Note: Bulk buttons are always present when records are selected regardless of whether selected records meet preconditions; clicking execute will skip records that don’t meet the conditions.

3. Quick (single-record) action buttons - Can show or hide. - Set button position to “List Page Row Actions”. - After configuration, the buttons appear in the Actions column on the right side of each row. Use the “exposed count” to control how many show as tiles and how many are in the dropdown.

2. List Page Layout — Mobile

• By default the Mobile list layout inherits the Web layout. You can enable an independent Mobile layout.

2.1 Independent Mobile Configuration

• Click a row in the preview to configure the Mobile list settings.
• Layout options include: Display Style, Scene Settings, Field Settings, Quick Filter Settings, Button Settings, Summary Field Settings.

Definitions: - Display Style: choose Card or Table display for records on Mobile. - Scene Settings: control which default or tenant-level scenes are visible to front-end users and whether scenes display as tiles or dropdowns. - Quick Filter Settings: select which fields users can filter by and whether those filters are exposed, improving findability. - Field Settings: determine which fields appear in the list; by default follows the scene field configuration. - Button Settings: set visibility for global and bulk buttons. - Summary Field Settings: enable aggregation (sum) for numeric, currency, or rate fields.

• Mobile supports separate configurations for the primary list and the select-data list. By default the select-data list follows the primary list but can be configured independently.

3. Multi-view List Presentation

• A plain list sometimes doesn’t meet user needs. Users may want to compare different datasets, display record locations on a map, or visualize records by time in a calendar. The system offers multiple list views.

3.1 Split-Screen View

• Switching to Split-Screen View changes the layout to left/right: the left shows the list, the right shows record details.
• The left list displays as Cards and only shows the first three fields configured in the column settings. Quick filters are not supported in Split-Screen mode.

3.2 Map View

• If the object contains geolocation fields, the list can switch to Map View (Web only).
• If multiple geolocation fields exist, you can choose which to use.
• You can customize which fields appear in the marker info-bubble on the map.

3.3 Calendar View

• Use case: display chosen object records on a calendar by a Date-Time field. The calendar entry’s summary fields are configurable. Calendar View helps users manage records by time.
• Modes: Calendar only, or Calendar + List.
• Time dimension selection: the selected field must be a required Date-Time field at the field level (not layout-level required).
• When configuring the calendar, set the summary field(s) to display.
• Front-end calendar supports Day, Week, Month views, scenes, filters, search, and other standard functions.

4. Advanced: Expose Specific Record Types Under a Menu

• In Custom Menus you can now add a specific Record Type as a menu entry. The menu can display not only an object, but also a particular Record Type (for example, Store or Distributor) as its own icon.

Example: - The Account object has two Record Types: Store and Distributor. Some organizations want separate menus for each Record Type so that entering the Distributor menu only shows Distributor records. Different Roles can see different layouts when accessing different Record Type menus.

Note: “Menu” refers to the long left-hand column that lists objects after entering the CRM.

4.1 Setup Steps

1. Create a custom menu.

1. Associate an object and its Record Type with the menu.

1. In Menu Template Management, enable the newly created custom menu for the CRM app.

1. Add a new list page layout — in the example, a layout named “Store”.

1. Assign layout allocation (this only takes effect if you configured a custom menu for the Record Type).

1. Finally, allocate the Store layout to Roles for the Store Record Type and assign that Record Type to the previously created menu. Now the menu shows Store and presents the assigned layout when opened.

5. List Page Search

5.1 Global (All-Field) Search Configuration

• In Admin Console → Object Management → Preset/Custom Object → Object Basic Info, enable “Global Search”. The front-end filter will include an “All Fields” option.

5.2 Search Scope

• The current field search dropdown supports these field types: Auto-increment ID, Single/Multi-line Text, Rich Text (collaborative), Mobile, Email, URL, Lookup (Find Association), and Geolocation.

5.3 Filterable Fields

• Most fields support filtering. Exceptions apply to Lookup fields and Formula (calculated) fields.

• Lookup fields: a. A lookup field is filterable only if the field’s configuration enables filtering. b. Lookups that reference Lookup fields, Dept. fields, User fields, or Images do not support filtering (when such targets are chosen, the “Filterable on List Page” option is grayed out to No). c. Lookup fields that do not support filtering cannot be used as filter criteria in functions. d. Lookup fields include a configuration toggle “Enable filter support”; enabling it allows filtering.

• Formula (calculated) fields: a. Some formulas cannot be persisted to storage, so they do not support filtering. Formula fields can appear in the data list filter if supported, and the comparison operators depend on the formula return type. b. If a formula references user fields and the feature “Formula referencing user attributes supports filtering” is available in grayscale, such formulas may be filterable.

6. FAQ

Q1. Can Mobile default the search field? - The default search uses the primary attribute field. If a user switches to another field, the system remembers that choice and uses it as the default next time.

Q2. After selecting a specific Record Type on Mobile, the list search sometimes returns records of other Record Types while Web correctly shows only the selected Record Type — why? - Mobile all-field search is currently a full-text search and ignores scene and filter context. For custom objects you can request the grayscale feature “Mini App: Object Data List Search V2 — Custom Objects” to address this; preset objects are not supported yet.

Q3. Can the search fields be controlled by the column header fields? - No. Search fields are the object’s fields that support filtering, not controlled by visible column headers.

Q4. Why can’t I select the “Tag” field in list filters? - Confirm whether the grayscale “Hide Tag Filtering” is enabled. If tags are hidden by grayscale, request a grayscale rollback to restore tag filtering.

Q5. Can admins centrally configure Mobile quick filter fields? - Yes. Configure at: List Page Layout → Mobile Independent Layout → Quick Filter Settings.

Glossary: - Enable Quick Filters: whether filter fields are exposed. - Fields in Filter Page: which fields are available as filters.

Note: Users can personalize front-end filter settings; personal changes persist.

Points to note: 1. Web list layout also has Quick Filter settings. Web and Mobile Quick Filter configurations are independent. 2. If Mobile independent layout is not enabled, Mobile uses fields from the Mobile summary layout by default. 3. If a tenant-level configuration doesn’t appear for the user, ask the user to click “Restore System Defaults”.

Q6. How does the system determine which fields and order show in list headers? - Examples shown below illustrate layouts.

(Example images)

Related / Sub-object table (when Record Type displays as Tile): - Admin setting location: Primary Object detail page → Sub-object/Related Object component settings → Display Style.

Front-end display:

Related / Sub-object table (when Record Type displays as Dropdown):

Field & order selection logic:

1. Default logic: 1.1 List page: - Use the scene’s display fields and order.

1.2 Sub-object / Related-object table (Record Type as Tile): - Fields = 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: - If grayscale “Sub-object tile mode: header follows corresponding layout order” is enabled, fields = intersection of scene and layout fields; order follows the corresponding layout order. - If grayscale “Detail-page sub-object column order optimization: sub-object fields follow scene configuration” is enabled, fields = intersection of scene and layout fields. - If scene header fields = All, order follows scene display fields. - If scene header fields = Specific Record Type, order follows that Record Type’s detail-page layout field order. - If both grayscales have been toggled (enable 1 then enable 2), the system follows grayscale 1’s logic.

Grayscale keys: - Grayscale 1: “Sub-object tile mode: header follows corresponding layout order” - Grayscale 2: “Detail-page sub-object column order optimization: sub-object fields follow scene configuration”

1.3 Sub-object / Related-object table (Record Type as Dropdown): - Use the scene’s display fields and order.

1. After a user customizes “Column Settings”: - Personal-level configuration applies; default logic no longer applies. The system uses the personal column settings.

2. Column settings rules: - By default, Column Settings follow Admin Console → Scene Management → Display Field Settings. - Column Settings let you toggle visibility for all object fields. - If a user modifies Column Settings, they no longer follow the scene. To revert to scene-managed fields, use “Restore System Default” in Column Settings to clear personal column settings.

Q7. Where do default column widths set in scenes apply? - Scene field widths apply only to object lists (main lists, related lists, select-data lists — basically anywhere scenes are used). Field widths in new/edit pages do not follow this rule.

Notes: 1. New/edit page table column width cannot be set globally; they use default widths. Users can manually adjust widths, which are stored locally in the browser cache. Clearing cache restores default widths. 2. If configured widths don’t take effect, it’s likely the user has personal column settings. Ask the user to restore default column widths in the object main list and check again.

Q8. Which buttons can be configured on list pages, and how do different buttons behave across contexts?

Global buttons - Web supports exposing global buttons; Mobile does not and ignores Web’s exposed-button configuration.

Main List - Supported buttons: New, Import, Export, Export Images/Attachments, Duplicate Detection, Smart Form, Pull Records, Custom Buttons (Business/UI)

Table: Main List button behavior

Related List - Supported buttons: New, Link, Unlink, Smart Form, Custom Buttons (Business/UI)

Table: Related list button behavior (summary) - If Related List independent config is OFF on Web detail page: New is exposed by default; other buttons are in the More menu (Web and Mobile). - If Related List independent config is ON, Web uses related-list independent config for visibility/order/exposed count; Mobile uses Web related-list config for visibility/order but does not support exposed buttons (first button is exposed by default). - Mobile detail page settings follow similar mapping; when Mobile related-list independent config is ON, Mobile visibility/order uses the Mobile config but still does not support exposed buttons (first button exposed by default).

Select-Data List - Supported buttons: New

Table: Select-data list button behavior (summary) - Web select-data list without independent config: uses main list Web config for visibility/order/exposed count; Mobile follows Web main list config for visibility/order but cannot expose buttons (first button exposed by default). - Web select-data list with independent config: Web still uses main list Web config; Mobile uses main list Web config and does not support exposed buttons (first button exposed). - Mobile select-data list without independent config: Web uses main list Web config; Mobile uses main list Mobile config (no exposed buttons). - Mobile select-data list with independent config: Web uses select-data list independent config; Mobile uses select-data independent config (no exposed buttons).

Bulk buttons - Both Web and Mobile do not support exposed bulk buttons.

Main list bulk buttons supported: Export, Export Images/Attachments, Lock, Unlock, Tag, Change Owner / External Owner, Change / Remove Partner, Add / Remove Related Teams Members, Print, Email, Follow, Unfollow, Custom Buttons (Business/UI)

Table: Bulk button behavior - Main list — Mobile independent layout OFF: Web and Mobile display/order follow Web config. - Main list — Mobile independent layout ON: Web display/order follow Web config; Mobile display/order follow Mobile independent config.

Related list bulk buttons supported: Export, Export Images/Attachments, Tag, Change / Remove Partner, Print, Email, Follow, Unfollow, Custom Buttons (Business/UI)

Table: Related list bulk button behavior follows same mapping as single-record related-list bulk behavior described earlier.

Quick action buttons (Row-level actions) 1. Web supports exposing quick action buttons; Mobile does not and ignores Web’s exposed configuration. 2. Mobile shows single-record quick actions only in Card style; Table style does not show single-record quick actions.

Main list quick actions - Supported buttons: Convert, Custom Buttons (Business/UI) Note: Mobile independent layout for main list does not support quick action configuration.

Table: Quick action behavior - Both Web and Mobile follow Web config for visibility/order/exposed count in most main-list scenarios as described above. Mobile does not support exposed quick-actions.

Related list quick actions - Supported: Custom Buttons (Business/UI) Note: Mobile independent detail-page related-list config does not support quick action configuration.

Lookup-related behavior (lookup fields in related lists) - If Web detail page related-list independent config is OFF: visibility and exposed count follow main list config (both Web and Mobile). - If Web detail page related-list independent config is ON: Web uses related-list independent config; Mobile does not show row-level quick actions.

From Related (sub-related lists) - Web detail page without related-list independent config: visibility follows main list config; exposed buttons are not supported (exposed not inherited). - Other combinations follow the same patterns described above: when Mobile does not support single-row buttons, they are hidden on Mobile.

(End of document)