1. Enterprise-level Scenario Use Cases

1.1 Overview

The system provides Scenario functionality to quickly narrow and locate a subset of records. Scenarios help reduce the scope of query results and focus users on relevant data.

1.2 Enterprise-level Scenarios vs. Personal Scenarios

1. Difference and relationship between Enterprise-level Scenarios and Personal Scenarios - Enterprise-level Scenarios are configured by administrators in the backend; Personal Scenarios are configured by users in the frontend. - Enterprise-level Scenarios include preset and tenant-level custom scenarios. Personal Scenarios are configured based on enterprise-level scenarios.

2. Priority between Enterprise-level and Personal Scenario settings - Priority: Personal Scenario settings > Enterprise-level Scenario settings - Personal Scenario settings override tenant-level settings. If a user customizes a scenario at the personal level (for example, adjusts displayed fields on the frontend list page), the frontend will not follow subsequent backend changes for that user.

2. Operation Guide

2.1 Built-in Scenario Capabilities

2.1.1 Preset scenario scope

• The system provides Scenario functionality to quickly narrow and locate a subset of records. The system includes several ready-to-use preset scenarios for user convenience.
• Preset scenarios include: All, My Responsibilities, Participated by Me, My Responsible Departments, Responsible by My Subordinates, My Subordinates Participated, Shared With Me, Followed by Me

2.1.2 Preset scenario definitions

Each preset scenario corresponds to specific data access rules:

Note: A subordinate is a person whose Reporting Manager is me (including hierarchical descendants)

Note: A subordinate is a person whose Reporting Manager is me (including hierarchical descendants)

Note: To mark a specific record as Followed, open the record in the frontend and click the “Follow” button in the upper right corner.

2.1.3 Preset scenario configuration

1. Basic information: You can modify the list sorting for the frontend list page when this scenario is selected.

2. Web display settings: - Configure whether to show tag fields on the list page. - Fields configured to display will appear on the list page when this scenario is selected. - For preset scenarios, the most recently modified scenario settings may override user-level settings: if checked, the frontend list columns configuration will be replaced by the preset configuration. - Sync this configuration to other scenarios: replicate the current field display settings to other scenarios.

3. Mobile display settings: - If you do not choose separate configuration, when the scenario is selected in the frontend the list page will use the mobile summary layout display fields. - If you choose separate configuration, when the scenario is selected the list page will display the fields configured specifically for this scenario.

2.1.3.1 Basic layout

Under Basic layout, scenario records display in a fixed format. You can configure: - Whether to show a preview image on the left - Image size - Whether to show tags - Field display style: Tile or Compact - Whether to show field labels

Note: Translate “平铺” as “Tile” per terminology mapping.

2.1.3.2 Enable Advanced layout

When Advanced layout is enabled, layout flexibility increases and more options become available: - You can place multiple text elements in one row. Each text element can be one of: - Field - Custom text - Tag - Separator - For each text element you can configure: - Size - Color - Background color - Border color - For each row you can set alignment and arrangement. - For images you can set dimensions.

Using Card Templates - Advanced layout includes prebuilt card templates. Choose a template via preview, then adjust text and detail parameters to meet your business needs.

2.1.4 PC frontend scenario usage

• When a scenario is selected on the frontend list page, the list shows the records within that scenario’s data scope.
• In the frontend Scenario Filter → Manage you can toggle scenario visibility, change display order, and set defaults.
• The frontend list page’s Settings button (upper-right) allows users to configure personal settings for preset scenarios. If a backend change alters scenario display fields, it will not affect users who made personal adjustments. To remove personal overrides, users can click Restore System Default in the frontend Scenario Filter → Manage.

2.2 Create a New Enterprise-level Scenario

2.2.1 Basic information settings

If preset scenarios no longer meet business needs, admins can create a new scenario and configure its basic information. - Creation methods: Create from scratch, or Copy from an existing scenario

• Basic info: Object, Scenario Name, API Name, Description, Applicable Scope

• Data scope: Define record filtering rules using existing or custom logic. Includes:
  • Record Type: filter by a previously defined Record Type; selecting the scenario will automatically apply this filter in the frontend.
  • Base data scope: use a preset scenario’s filter as a prerequisite filter.
  • Configurable conditions: logical filters on specific fields; selecting the scenario will automatically apply these conditions in the frontend.

2.2.2 Display settings

For the filtered records, configure which fields appear on the list page. Configure Web display and Mobile display separately.

2.2.2.1 Web display settings

• Display field options: All fields or follow Record Type display
  • All: freely choose whether to display any field for the object
  • Follow Record Type: inherit layout fields from the specific object’s Record Type detail page
  • Fields you configure here will appear on the list page when this scenario is selected
• Auto-wrap configuration for display fields
  • Use this setting to avoid truncated field names when column widths are narrow

• Sync this configuration to other scenarios: replicate the current field display settings to other scenarios

2.2.2.2 Mobile display settings

• If you do not choose a separate configuration, selecting the scenario in the frontend will use the mobile summary layout fields.
• If you choose separate configuration, selecting the scenario will show the fields configured for this scenario on mobile. Separate configuration can enable Advanced layout.

Note: Advanced layout offers more flexible composition compared to Basic layout, supports more field types, and provides richer display controls.

1. Basic layout Under Basic layout, scenario records display in a fixed format. Configurable items: - Whether to place a preview image on the left - Image size - Whether to display tags - Field display style: Tile or Compact - Whether to show field labels

1. Enable Advanced layout When Advanced layout is enabled, layout flexibility increases: - You can place multiple text elements per row. Each element may be: - Field - Custom text - Tag - Separator - Available text properties: - Size - Color - Background color - Border color - For each row you can set alignment and arrangement. For images you can set size.

Using Card Templates - Choose from prebuilt card templates via preview, then adjust template texts and details to meet your business needs.

2.2.3 Backend operations for custom scenarios

• Disable: Disabled scenarios will not appear on the corresponding object pages.
  • The All scenario can also be disabled. The previous rule (only All could not be disabled) has changed: each object must retain at least one scenario whose Applicable Scope is the whole company (including preset and tenant-level scenarios).
  • Example 1: If only one company-wide scenario exists, the Disable button will not show on the right for that scenario.
• Delete: Disabled scenarios can be deleted.

2.2.4 PC frontend scenario usage

• When a scenario is selected on the frontend list page, the list displays data for that scenario’s data scope.
• In frontend Scenario Filter → Manage you can toggle scenario visibility, change display order, set default values, and also create custom scenarios.
• The frontend list page Settings button (upper-right) cannot apply personal-level configuration to tenant-level custom scenarios; there is no Apply button for those scenarios.

2.2.5 Relationship between frontend list filters/search and custom scenarios

1. If the frontend selects a custom scenario and modifies its filter component conditions, clicking Search makes the list ignore the original scenario filter and follow the modified conditions. - Example: A scenario sets filter: Primary Attribute contains 1. After clicking Filter, the list shows: Primary Attribute 1, Primary Attribute 11 If the user removes that filter condition in the frontend filter component and clicks Filter, the list shows: Primary Attribute 1, Primary Attribute 11, Primary Attribute 2

2. If the frontend selects a custom scenario, its filter conditions are loaded. Searching in the search box will combine the search condition with the scenario filter. - Example: Scenario filter: Primary Attribute contains 1. If the user enters Primary Attribute = 2 in the search box and clicks Search, the list shows records that include both 1 and 2 in the Primary Attribute: Primary Attribute 121, Primary Attribute 1234

2.3 Configure Scenario Priority

2.3.1 Definition of scenario priority

After defining scenarios that determine which records appear and which fields display, you may face conflicts for default scenario selection across different Roles. For example, you may want Role M to default to Scenario A and Role N to default to Scenario B. To resolve this, set Scenario Priority.

• Administrators can sort all scenarios’ default priority in the backend Scenario Management.
  • Sortable scenarios: any scenario except deleted ones (including disabled scenarios) can be ordered.
• Scenarios are evaluated by Applicable Scope; the first applicable scenario becomes the default.

2.3.2 Scenario priority configuration examples

Example 1 — Each department should default to the scenario for its own department - For the Account object, the company wants Sales to see name, contact info, activity (Scenario A); Operations to see deal amount (Scenario B); and both departments to see company size and location (Scenario C). - Scenario settings: - Scenario A applies to Sales - Scenario B applies to Operations - Scenario C applies to the whole company - Backend default scenario order: 1. Scenario A 2. Scenario B 3. Scenario C - Frontend results: - Sales staff: - Can view A and C - Default scenario: A - Operations staff: - Can view B and C - Default scenario: B - Other departments: - Can view C - Default scenario: C

Example 2 — Force the whole company to default to one scenario - For the Account object, same scenarios A (Sales), B (Operations), C (Company-wide). The company wants both departments to default to C. - Scenario settings: - Scenario A applies to Sales - Scenario B applies to Operations - Scenario C applies to the whole company - Backend default scenario order: 1. Scenario C 2. Scenario A 3. Scenario B - Frontend results: - Sales employees: - Can view A and C - Default scenario: C - Operations employees: - Can view B and C - Default scenario: C - Other departments: - Can view C - Default scenario: C

Example 3 — Overlapping applicable departments - For the Account object, the company configures: - Scenario A applies to departments Sales and Operations (show name, contact, activity) - Scenario B applies to department Operations only (show deal amount) - Backend default scenario order: 1. Scenario B 2. Scenario A - Frontend results: - Sales employees: - Can view A - Default scenario: A - Operations employees: - Can view A and B - Default scenario: B

2.3.3 Priority between Personal and Tenant-level scenario settings

• Priority: Personal Scenario settings > Tenant-level Scenario settings

The system provides preset scenarios: All, My Responsibilities, Participated by Me, My Responsible Departments, Responsible by My Subordinates, Shared With Me, Followed by Me.

• Use case: Admin changes fields for a preset scenario in the backend, but frontend users report no change.
• Cause: Users made personal-level adjustments to the scenario; personal settings override tenant-level settings. Personal-level adjustments refer to changes made in the frontend list page field settings.
• Solution: In the frontend Scenario Settings click Restore System Default to align with backend configuration.

3. FAQs

3.1 Why is the Apply button missing after adjusting the object list header?

Tenant-level scenario configurations are not editable by end users; therefore, after column adjustments the Apply button is disabled.

3.2 Why is there no Save button after changing filters when switching scenarios on the list page?

Tenant-level scenario configurations are not editable, so filter changes cannot be saved.

3.3 Why is there no All-fields search option for custom object list search?

Cause: Global search is not enabled for the object.
Solution: Backend Admin → Object Management → Basic Information → Check Enable Global Search

3.4 Backend hid a field in the “All” scenario but frontend users still see it

Cause: Frontend users have personal display field configurations which override backend settings.

Solutions: - Method 1: User clears system configuration in List Page → Column Settings. - Method 2: Force clear personal user configurations from backend: Edit Scenario → Web Display Settings → Check Clear Personal Configurations. (Note: this will clear all users’ personal column settings, column widths, etc. Use with caution.)