Published at: 2025-10-30

Contract


I. Business Use Case Examples

When companies establish Contracts, they typically set effective and expiration dates. To remind sales teams and clients to renew Contracts in a timely manner, the system will display smart reminder cards on the CRM homepage starting 30 days before the expiration date, providing daily notifications for upcoming expirations.

For agreement-type Contracts, fulfillment often involves executing multiple Sales Orders with clients. The system supports creating multiple Sales Orders under a single Contract to accommodate such business scenarios.

II. Detailed Overview of Contracts

2.1 Default Contract Scenarios

  • All:

    • Records where the owner is the current user or their subordinates.

    • Or records where the Related Teams include the current user or their subordinates.

    • Or records where the current user, as an Order Management or Order Finance Role, is responsible for approving data from a specific Dept. (e.g., User A has the “Order Finance” Role and approves records submitted by Dept. B—User A can then view all records owned by members of Dept. B).

    • Or records where “Data Permission Management” configures Contract “Data Sharing” rules to share records owned by the current user, their Dept., or their user group.

    • Or records under “My Responsible Departments.”

  • My Responsibilities: Records where the owner is the current user.

  • Participated by Me: Records where Related Teams include the current user.

  • Responsible by My Subordinates: Records where the owner is a subordinate of the current user.

  • Participated by My Subordinates: Records where Related Teams include subordinates of the current user.

  • Shared With Me: Records shared via “Data Permission Management” where Contract “Data Sharing” rules apply to the current user, their Dept., or their user group.

  • My Responsible Departments:

    • Records where the current user is the head of their primary Dept.

    • And the Related Teams’ primary Dept. matches the current user’s Dept.

    • Note: Whether the responsible Dept. includes all subordinate data depends on “CRM Management > Rule Settings > Basic Settings > Data Visibility for Superiors.”

Notes:
- “CRM Administrators” can view all data.
- Records marked as “Voided” are visible only to “CRM Administrators” and hidden from all other users.

III. Contract Business Operations

3.1 Creating a Contract

  • Methods to create a Contract:

    • Manual creation:

      • Entry points:

        • [Contract] list page

        • [Contract] tab under the associated [Account] details page

        • [Contract] tab under the associated [Sales Order] details page

    • Import: Refer to Import for details.

3.2 Common Contract Operations

  • List page operations: See Common List Page Operations (link pending).

  • Adding sales records: See Sales Records (link pending).

  • Common business operations: Including reassigning ownership, adding Related Teams, printing, importing, exporting, editing, voiding, deleting, etc. See Common Business Operations (link pending).

  • Collaboration-integrated operations: Including forwarding, Calendar events, reminders, phone calls, emails, etc. See Common Business Operations (link pending).

Submit Feedback