---
sourceDocument: Australia Employee Service Management
sourceDocumentLink: https://www.servicenow.com/docs/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 a contract configuration

# Create a contract configuration {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read

Define the contract repository where the contracts will be stored and map the data to be added to the contract or amendment document.

## Before you begin

A contract template and a template rule that will pick the template when the user submits a contract or amendment request must exist. For more information, see [Configure templates for a contract and amendment request in Contract Management Pro](https://www.servicenow.com/docs/zTazjE0~AUlVLuxbbUzP6Q "Create contract templates to easily generate Microsoft Word contract documents based on request types in Contract Management Pro.") and [Configure contract template rules](https://www.servicenow.com/docs/cyWJlG1tPoGhWp0hT2sORA "Configure a rule to identify the contract document template used for generating the contract document for a request.").

You can distinguish configurations for an amendment request from those for a new contract by using the Request type selection.

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://www.servicenow.com/docs/xLBJ8z3_exa8_CRKNJOGUA "As an administrator, provide access to contract request fields so they can be selected in condition builders.")  
For a request:

* The fields mapped in the contract configuration determine which values will be updated in the contract document.
* For a contract request, a new contract repository record is created. According to field and variables mapping, the values are populated into the contract document.
* 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.

{#cncore-contract-config__ul_zt4_3gn_ghc}

Role required: sn_cm_core.contract_config

## About this task

To add data to the contract documents, 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 AllContracts CoreContract AdministrationContract Configuration.
2. Select New.
3. On the Contract Configuration form, fill in the fields.  
   For more information, see [Contract Configuration form](https://www.servicenow.com/docs/u1t3HrYPiEDosw0f5Rg6FA "Use the Contract Configuration New Record form to create or modify a contract configurations.").
4. Select Save.
5. In the Contract Repository Mappings related list, select New.  
   Figure 1. Contract configuration
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. {#cncore-contract-config__ul_sr1_jw5_yxb} |
   | 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. {#cncore-contract-config__ul_sxj_kw5_yxb} |
   | 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. {#cncore-contract-config__ul_i1f_lw5_yxb} |
   |-|-|

   {#cncore-contract-config__choicetable_grz_dw5_yxb}
7. Select Submit to save the repository mapping.
8. Select Update to save the contract configuration.

*[\>]: and then