--- title: Create a contract configuration description: Define the contract repository where the contracts will be stored and map the data to be added to the contract, amendment, or renewal document. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/employee-service-management/contract-management-pro/cncore-contract-config.html release: australia product: Contract Management Pro classification: contract-management-pro topic_type: task last_updated: "2026-03-12" reading_time_minutes: 4 breadcrumb: [Configure, Contract Management Pro, Legal and Contract Operations, Employee Service Management] --- # Create a contract configuration Define the contract repository where the contracts will be stored and map the data to be added to the contract, amendment, or renewal document. ## Before you begin A contract template and a template rule that will pick the template when the user submits a contract, amendment, or renewal request must exist. For more information, see [Configure templates for a contract requests](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/employee-service-management/contract-management-pro/cncore-document-templates.md) and [Configure contract template rules](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/employee-service-management/contract-management-pro/cncore-config-template-rules.md). You can distinguish configurations for a new contract, amendment and renewal requests from the **Request type** selection. You can add multiple request types, so a single configuration is applicable to more than one request type, such as New Contract and Renewal together. If you want the variables related to the contract request to be available in condition builder, add the contract request reference to your application table. For more information, see [Enable contract request fields in condition builders](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/employee-service-management/contract-management-pro/cncore-add-cmr-condtion-build.md) For a request: - The fields mapped in the contract configuration determine which values will be updated in the contract repository. - For a new contract and renewal request, a new contract repository record is created. According to field and variables mapping, the values are populated into the contract repository. - For an amendment request, a new contract repository record isn’t created. Instead, the existing record is updated by overriding values for fields and variables that have a defined mapping. If a mapping doesn’t exist for a specific field, its value remains unchanged. For example, to update the contract end date through an amendment, the mapping for the end date field must exist. If you want to copy fields with empty values and override existing values in the contract document, select the **Allow empty value flag** when configuring the mappings.\[Omitted image "cncore-amend-allow-empty-value.png"\] Alt text: Set the flag Allow empty value for copying empty values Role required: sn\_cm\_core.contract\_config ## About this task To add data to the contract repository, you have to map request table fields to repository fields. **Note:** Third party contracts already have a default contract configuration in the base system. ## Procedure 1. Navigate to **All** > **Contracts Core** > **Contract Administration** > **Contract Configuration**. 2. Select **New**. 3. On the Contract Configuration form, fill in the fields. For more information, see [Contract Configuration form](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/employee-service-management/contract-management-pro/cncore-contract-config-form.md). 4. Select **Save**. 5. In the Contract Repository Mappings related list, select **New**. \[Omitted image "cmpro-contract-conf.png"\] Alt text: Contract configuration with repository mapping 6. In the **Mapping type**, select the type of mapping you want to do. The fields on the form change depending on the selection.
Mapping type Fields available
**Field mapping - Map fields from the request table to the fields in the contract repository table.** - **Request table**- Table to which you want to associate the contract configuration. - **Map from field**- Field of the request table that you want to map to the **Map to field**, a field in the contract repository. - **Active** - Option to indicate that contract repository mapping is active. - **Contract repository** - This field is automatically set to the configuration repository set in the **Contract repository** field. - **Allow empty value** - Option to enable copying of empty values to contract repository and override the existing value. **Note:** This option is available only when the **Request type** is set to Amendment in the contract configuration and it isn’t selected by default.
**Template mapping- Map the template mappings of a contract template to the fields in the contract repository.** - **Template** - This field is automatically set to the template for which you’re creating the repository mapping. - **Template mapping** - The field from the template that you want to map to the **Map to field** value, a field in the contract repository. - **Active** - Option to indicate that the contract repository mapping is active. - **Allow empty value** - Option to enable copying of empty values to contract repository and override the existing value. **Note:** This option is available only when the **Request type** is set to Amendment in the contract configuration and it isn’t selected by default.
**Template mapping- Map variables of record producer to the fields in the contract repository table.** - **Record producer**- The record producer from which you want to copy the variable. For example, If you want to copy a variable from a contract request for Non-disclosure Agreement, select record producer for a Non-disclosure Agreement. - **Variable**- The variable of the record producer that you want to map to a field in the contract repository. - **Active**- Option to indicate that the contract repository mapping is active. - **Map to field**- The field to which you want to map the variable from the record producer. - **Allow empty value** - Option to enable copying of empty values to contract repository and override the existing value. **Note:** This option is available only when the **Request type** is set to Amendment in the contract configuration and it isn’t selected by default.
7. Select **Submit** to save the repository mapping. 8. Select **Update** to save the contract configuration.