Contract obligation extraction use case mapping form

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Contract obligation extraction use case mapping form

    The Contract Obligation Extraction use case mapping form allows ServiceNow customers to configure how contract obligation extraction use cases apply to specific contract records. This form maps use cases to contract repository tables, contract types, request tables, and conditions, enabling precise and automated extraction of obligations from signed contracts within the Now Assist in Contract Management system.

    Show full answer Show less

    Key Features

    • Name: Assign a unique identifier to each use case mapping for easy reference.
    • Use case selection: Choose from active contract obligation extraction use cases, including the CM Pro - Contract Obligation Extraction use case available in the Now Assist in Contract Management base system.
    • Contract repository table: Specify the contract repository table where the contracts reside, ensuring the use case applies only to contracts in that table.
    • Order: Define the priority order in which use cases should apply when multiple use cases meet the same conditions; lower order numbers take precedence.
    • Contracts created from contract request: Optionally restrict the use case to contracts initiated via contract requests (selected by default). This checkbox is visible only when the Now Assist in Contract Management and Contracts core plugins are installed.
    • Contract type: Specify which active contract types the use case targets; this is available when the contract request option is selected.
    • Request table: Select the source table for contract requests, defaulting to the Contract Request table ([sncmcorecontractrequest]) for centralized configuration and reusability. This field appears when contracts created from contract request are enabled.
    • Request conditions: Define conditions on the request table that must be met for the use case to apply, using the ServiceNow condition builder.
    • Repository conditions: Set conditions on the contract repository table that limit when the use case applies, also configured via the condition builder.

    Practical Application

    By accurately mapping extraction use cases to specific contract records and conditions, customers can automate obligation extraction tailored to their contract management processes. This ensures obligations are extracted only when relevant, improving efficiency and accuracy in contract lifecycle management workflows.

    Use the Create use case mapping form in the contract obligation extraction skill to map the use case to specific tables and conditions.

    Table 1. Create use case mapping form
    Field Description
    Name Unique name of the use case mapping.
    Use case The use case used to extract obligations from a signed contract.
    Note:
    Only active use cases for the contract obligation extraction skill are displayed in the list.

    The CM Pro - Contract Obligation Extraction use case is available with the Now Assist in Contract Management base system.
    Contract repository table The repository table where the contract records are created. The use case applies to contracts stored in the selected table.
    Order Order in which the use case will apply.

    If multiple use cases meet the same conditions, the use case with the lowest order number is applied first.
    Contracts created from contract request Option to apply the use case to contracts initiated from a contract request.

    When the check box is cleared, the use case applies to contracts that are directly uploaded on a contract record, without a contract request. The check box is selected by default.

    Note:
    The check box appears only when the Now Assist in Contract Management (sn_cm_gen_ai) and Contracts core (sn_cm_core) plugins are installed.
    Contract type The contract type for which the use case applies.
    Note:
    Only active contract types are displayed in the list.

    This field appears only when the Contracts created from contract request check box is selected.
    Request table The table from which contract requests are created. The use case applies to contracts created from the selected table.

    The Contract Request table [sn_cm_core_contract_request] is selected by default to centralize the configuration on a single table and improve reusability across product lines. You can choose to configure the use case mapping on a different table.

    This field appears only when the Contracts created from contract request check box is selected.
    Request conditions Conditions under which the use case applies on the request table.

    The field appears only when the request table is selected.

    For more information on using the condition builder, see Create a condition statement using the condition builder.

    The field appears only when the Contracts created from contract request check box and the request table are selected.
    Repository conditions Conditions under which the use case applies on the repository table.

    The field appears only when a table is selected in the Contract repository table field.

    For more information on using the condition builder, see Create a condition statement using the condition builder.