Create a contract configuration
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 and Configure contract template rules.
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
- 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.
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.
Third party contracts already have a default contract configuration in the base system.