---
sourceDocument: Australia Employee Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/employee-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Employee Service Management

ft:clusterId :

    - emplsm

bundleId :

    - emplsm

workflow :

    - Employee


---

# Create use case mapping form

# Contract obligation extraction use case mapping form {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 in ServiceNow enables customers to map specific contract obligation extraction use cases to designated tables and conditions within their contract management system.
This functionality helps tailor how obligations are extracted from signed contracts based on contract types, storage locations, and creation methods, improving automation and accuracy in contract management.
Show full answer Show less  

## Key Features

* **Name:** Assign a unique identifier to each use case mapping to easily manage multiple mappings.
* **Use case selection:** Choose from active contract obligation extraction use cases, including the CM Pro - Contract Obligation Extraction use case available with the ServiceNow Otto for Contract Management Pro base system.
* **Contract repository table:** Specify the repository table where contracts are stored, allowing the use case to apply only to contracts within that table.
* **Order:** Define the priority order for applying multiple use cases when conditions overlap; the lowest order number is applied first.
* **Contracts created from contract request:** Optionally restrict the use case to contracts initiated via contract requests versus direct uploads. This checkbox is enabled by default and requires specific plugins (ServiceNow Otto for Contract Management Pro and Contracts core).
* **Contract type:** Limit the use case application to specific active contract types when contracts are created from requests.
* **Request table and request conditions:** Specify the source table for contract requests and define conditions that determine when the use case applies to requests. By default, the Contract Request table is selected to promote centralized configuration and reusability.
* **Repository conditions:** Define conditions on the contract repository table to further refine when the use case applies, using the ServiceNow condition builder for precise filtering.

## Practical Benefits for ServiceNow Customers

* Enables precise and flexible mapping of obligation extraction logic to relevant contract records, improving accuracy in contract analysis.
* Supports multiple use cases with prioritized application, ensuring the most relevant extraction logic is applied first.
* Allows differentiation between contracts created directly and those initiated from requests, enhancing workflow alignment.
* Facilitates centralized and reusable configurations by leveraging default tables and condition builders.
* Integrates smoothly with ServiceNow Contract Management Pro plugins to extend functionality.  
Use the Create use case mapping form in the contract obligation extraction skill to map the use case to specific tables and conditions.
{#cmpro-na-use-case-map-form-obe__table_lxd_sm1_wcc__entry__2}

| 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 ServiceNow Otto for Contract Management Pro 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 ServiceNow Otto for Contract Management Pro (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](https://www.servicenow.com/docs/access?context=create-cond-state-using-cond-build&version=australia&pubname=australia-platform-user-interface&ft:locale=en-US). 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](https://www.servicenow.com/docs/access?context=create-cond-state-using-cond-build&version=australia&pubname=australia-platform-user-interface&ft:locale=en-US). |
[Table 1. Create use case mapping form]

{#cmpro-na-use-case-map-form-obe__table_lxd_sm1_wcc}