Map a use case for contract metadata extraction

  • Rversion finale: Australia
  • Mis à jour 12 mars 2026
  • 2 minutes de lecture

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

    Pourquoi et quand exécuter cette tâche

    The following video walks you through the process of mapping use cases for the contract metadata extraction skill.

    Avant de commencer

    Ensure that the application is in Global or Now Assist in Contract Management scope. If you are configuring the use case mapping in 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

    Procédure

    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. Select Activate skill on the skill you want to activate.
      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 metadata extraction.
    6. In the Use case mappings page, select New.
    7. In the Create new use case mapping form, fill in the fields.
      Tableau 1. Use Case mapping form
      Field Description
      Name Unique name of the use case mapping.
      Use case The use case used to extract metadata from a signed contract.
      Remarque :
      Only active use cases for Contract metadata extraction are displayed in the list.

      The CM Pro - Contract Metadata Extraction use case is available with the Now Assist in Contract Management base system.
      Contract type The contract type for which the use case will apply.
      Remarque :
      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 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 contract repository table where the extracted metadata will be added.
      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.

    Résultats

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