Published at: 2025-10-30

Sales Record Admin Console Configuration


I. Sales Record Object Configuration

Access Path: Admin Console > Object Management > Preset Object Management > Sales Record

1.1 Basic Information

Administrators can customize the name, description, and other details of the Sales Record.

1.2 Field List

Administrators can add or edit fields for Sales Records and configure them in corresponding layouts.

1.3 Field Dependency

Establishes dependencies between fields.

Example: If a dependency is set between Record Type (Sales Record) and Follow-Up Activity (Onsite Training), front-end users creating a Sales Record of this type will only see “Onsite Training” as an option for Follow-Up Activity.

1.4 Role Permissions

Administrators can configure functional permissions for Sales Records based on employee Roles.

1.5 Layouts

Includes:
- Detail Page Layout
- List Page Layout
- Mobile Summary Layout (also applies to web summary views)

Administrators can edit preset layouts or create new ones. After configuration, layouts can be assigned based on Roles and Record Types.

Note: In Feeds, Sales Records displayed before clicking [Show More] follow the Mobile Summary Layout. After clicking, they switch to the Detail Page Layout. To maintain consistency, ensure both layouts share the same field scope.

1.6 Layout Rules

Enables dynamic layout displays based on field conditions or actions (e.g., creating/editing Reports).

Example: If a Report’s Daily Plan Record Type has “Li Si” as the reviewer, the condition “Next Work Plan is a required field” is triggered.

1.7 Record Types

Administrators can create Record Types for different business scenarios and assign them to specific Roles.
- After creating Record Types, administrators can assign visible types per Role.
- Note: The [All Employees] Role is a special designation affecting all users. Selecting [Select All] assigns the Record Type to all Roles.

picture coming soon:
[PC/Web] Sales Record Record Types

picture coming soon:
[Mobile] Sales Record Record Types

1.8 Validation Rules

Administrators can set validation rules for creating/editing Sales Records to block non-compliant data.

Example: If an employee submits a Sales Record, the system validates whether the owner’s Dept. is Sales. If not, an error message appears, and the save fails.

1.9 Scenario Management

Preset scenarios help users narrow Sales Record ranges. Administrators can also create custom scenarios and set priorities.

picture coming soon:
[PC/Web] Sales Record Scenario Switch (List Page)

picture coming soon:
[Mobile] Sales Record Scenario Switch (List Page)


II. Sales Record Settings

Configures related objects and Cc rules for Sales Records.

### 2.1.1 Flexibility Settings
Determines whether associated business objects can be modified or deleted after Sales Record creation.

picture coming soon:
Sales Record Association Settings

picture coming soon:
[PC/Web] Flexibility Settings (Demo)

picture coming soon:
[Mobile] Flexibility Settings (Demo)

2.2.2 Association Rules

Configures one-way association rules for Sales Records (A → B, but not B → A).

Example: If Leads and Accounts are associated, Sales Records created in a Lead’s Follow-Up Activity will auto-sync to the linked Account’s Follow-Up Activity, but not vice versa.

picture coming soon:
Association Settings – Related Objects

Key Points:

  • Related Object Selection: Based on the Lookup Relationship fields of the initiating object.
  • Format: [Target Object (Source Object.Lookup Field)] (e.g., Account (Lead.Lookup Account)).

picture coming soon:
Lead – Lookup Account Field

Prerequisite: The Lookup field must have a value when creating a Sales Record in Follow-Up Activity to enable auto-association.

picture coming soon:
Publishing a Sales Record in Follow-Up Activity (Ensure Lookup field is populated)

2.2 Cc Default Settings

Administrators can set default Cc rules for Sales Records based on sender/receiver criteria.
- Applicable Scope: Defines which senders the rule applies to.
- Preset Cc Range: Defines default recipients for the sender.

Note: Multiple rules can apply to the same sender; the final Cc list merges all applicable ranges.

Submit Feedback