Map a use case for contract obligation extraction

  • Release version: Yokohama
  • Updated October 28, 2025
  • 2 minutes to read

    • Map a use case to specific tables, and define conditions to apply the use case for obligation extraction.

    Before you begin

    Ensure that the application scope is in Global or Now Assist in Contract Management scope. If you’re configuring the use case mapping in a different application scope, add the scoped ACL to the Use Case Mapping table (sn_cm_gen_ai_usecase_configuration).

    Role required: sn_cm_gen_ai.ai_contract_config, sn_cm_core.contract_config

    Procedure

    1. Navigate to All > Now Assist Admin > Skills to access the Now Assist Skills tab of the Now Assist Admin console.
    2. Navigate to Employee > CM Pro.
    3. On the tile for your skill, select Activate skill.
      Figure 1. Now Assist skills for Contract Management Pro
      Now Assist skills available for Contract Management Pro.
    4. In the General details page, view the skill details and select Save and continue.
    5. In the Use case page, select Save and continue.
      For more information on creating a use case, see Create use cases for contract obligation extraction.
    6. In the Use case mappings page, select New.
    7. On the form, fill in the fields.
      Figure 2. Create new use case mapping form
      Create new use case mapping form to map obligations with request tables and repository tables.
      Table 1. Create new 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 type The contract type for which the use case applies.
      Note:
      Only active contract types are displayed in the list.
      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.
      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.
      Contract repository table The repository table where the contract records are created. The use case applies to contracts stored in the selected table.
      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.
      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.
    8. Select Save.

    Result

    The use case is mapped to specific tables and conditions, and it’s applied for obligation extraction when the conditions are met.

    What to do next

    Activate business rules for the Manage contract repository agentic workflow