I. Enterprise-Level Scenarios Overview

1.1 Scenario Overview

The system provides scenario functionality to quickly locate and narrow down query ranges for target objects.

1.2 Enterprise-Level vs. Personal-Level Scenarios

1. Differences and Relationships
- Enterprise-Level Scenarios: Configured by administrators in the backend.
- Personal-Level Scenarios: Configured by users in the frontend, based on enterprise-level scenarios.

2. Priority Settings
- Priority: Personal-Level Settings > Enterprise-Level Settings
- If a user modifies a scenario at the personal level (e.g., adjusts fields in the frontend list), the frontend will not sync with backend configurations.

II. Operational Guide

2.1 Preset Scenarios

2.1.1 Preset Scenario Range

The system offers predefined scenarios for quick data filtering:
- All: All data with access permissions.
- My Responsibilities: Data where I am the responsible party in Related Teams.
- Participated by Me: Data where I am a regular member in Related Teams.
- My Responsible Departments: Data owned by departments I manage (including cascading) or my assistants manage.
- Responsible by My Subordinates: Data where my subordinates are responsible parties in Related Teams.
- Note: “Subordinates” refer to personnel reporting to me (including cascading).
- Shared With Me: Data shared via owner-based, department-based, or conditional sharing (to me, my user groups, my departments, or my roles).
- Followed: Data marked as “Followed” (set via the frontend “Follow” button).

2.1.2 Preset Scenario Configuration

1. Basic Info: Adjust sorting for frontend list data.
2. Web Display Settings:
   • Toggle label field visibility in lists.
   • Configure displayed fields for the selected scenario.
   • Override user-level settings with the latest preset scenario configuration.
   • Sync configurations to other scenarios.
3. Mobile Display Settings:
   • Use default mobile summary layout fields or customize independently.

2.1.2.1 Basic Layout

Configure:
- Preview Images (left-side placement, size).
- Label visibility.
- Field display style (Tile/Collapsed).
- Field title visibility.

2.1.2.2 Advanced Layout

Enable flexible data formatting:
- Multi-text per row (fields, custom text, labels, separators).
- Text Attributes (size, color, background, border).
- Row alignment and image sizing.
- Card Templates: Prebuilt templates for quick customization.

2.1.3 Frontend Usage (PC)

• Select a scenario to filter list data.
• Manage visibility, order, and defaults via the Filter dropdown.
• Personal adjustments override backend configurations; reset via Restore System Default.

2.2 Create Enterprise-Level Scenarios

2.2.1 Basic Setup

When presets are insufficient, create new scenarios:
- Creation Methods: New from scratch or copy existing.
- Basic Info: Object, name, API Name, description, scope.
- Data Range:
- Record Type: Pre-filter by business type.
- Base Range: Use preset conditions.
- Custom Conditions: Apply field-specific logic.

picture coming soon:

2.2.2 Display Settings

Configure fields shown in lists for Web and Mobile:

Web Settings

• Field Display: Choose all fields or inherit from Record Type layouts.
• Auto-Wrap: Prevent truncation in narrow columns.
• Sync to Other Scenarios: Propagate configurations.

picture coming soon:

Mobile Settings

• Independent Config: Override default summary layouts.
• Advanced Layout: Enhanced formatting options (see 2.1.2.2).

picture coming soon:

2.2.3 Backend Operations

• Disable: Hide scenarios from frontend.
  • At least one company-wide scenario must remain active.
• Delete: Remove disabled scenarios.

2.2.4 Frontend Behavior

• Custom scenarios cannot be modified at the personal level.
• Filter/Search interactions:
  1. Modified filters ignore original scenario conditions.
  2. Searches combine scenario filters with user input.

2.3 Scenario Priority

2.3.1 Definition

Set default scenarios for specific roles/departments:
- Sorting: All non-deleted scenarios (including disabled).
- First applicable scenario becomes the default.

2.3.2 Examples

Example 1: Department-Specific Defaults

• Sales Dept: Sees names, contacts (Scenario A).
• Ops Dept: Sees revenue (Scenario B).
• All Departments: Sees company size/location (Scenario C).
• Priority Order: A > B > C.
  • Sales defaults to A; Ops to B; others to C.

Example 2: Company-Wide Default

• Priority Order: C > A > B.
  • All departments default to C.

Example 3: Overlapping Departments

• Sales & Ops: Scenario A.
• Ops Only: Scenario B.
• Priority Order: B > A.
  • Ops defaults to B; Sales to A.

2.3.3 Personal vs. Tenant Priority

• Personal-Level > Tenant-Level.
• Reset personal overrides via Restore System Default.

picture coming soon:

III. FAQs

3.1 Why is the “Apply” button missing in list headers?

Tenant scenarios cannot be modified; column adjustments are disabled.

3.2 Why can’t I save modified filters?

Tenant scenarios are read-only.

3.3 Why is “Full-Field Search” unavailable?

Cause: Global search is unconfigured.
Fix: Enable in Admin > Object Management > Basic Info > Global Search.

3.4 Why don’t backend field changes reflect for users?

Cause: Personal-level settings override them.
Solutions:
1. Clear user configurations via List > Column Settings.
2. Admin Override: Check “Clear Personal Configs” in scenario settings (use cautiously).

picture coming soon: