| Name |
Unique name for the contract template. |
| Table |
Table to which you want to associate the contract template.Note: 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 template on a different table. |
| Category |
Document category to which you want to associate the contract template. |
| Document |
Upload a Microsoft Word document of type .docx. This document will be replaced with an updated version containing content controls for metadata, signatory, and clauses
using Microsoft Word add-in for ServiceNow Contracts. |
| State |
The initial state is automatically set to Draft. |
| Application |
Application to which the contract template belongs. This field is automatically set to the application scope in which you’re creating the contract template. |
| Active |
Option to make the template active and available for use. |
| Signature blocks |
Option to disable signature blocks in the contract template.
Note: The check box is selected by default to enable the signature block configuration for a contract template.
When this option is selected:
- You can’t upload a participant-based template.
- The Participants related list isn’t available.
For more information, see Add and configure signature blocks using Microsoft Word add-in for ServiceNow Contracts. |
| Start date |
Date on which the Word document template becomes valid. Providing a start date helps when maintaining multiple versions of same template. |
| End date |
Date until which the Word document template is valid. Providing an end date helps when maintaining multiple versions of same template.
If the values in the Start date and End date fields are empty the template will be always valid.
Note:
If you specify an end date, you must also specify a start date.
|