Contract Lifecycle Management System Administration

These topics are primarily for contract administrators, product administrators, and others who are setting up Vlocity CLM for an org.

Vlocity CLM generates a contract document by merging the contract data with the document template. Variables, also known as tokens, are replaced. When you check in a contract document, you can automatically generate a Microsoft Word or PDF file and attach it to the contract document version.

You can ensure that users can edit only the appropriate contract sections or information. You can import contract documents that were modified in Microsoft Word and reconcile them with the online version in CLM. Restricted data is not changed.

• CLM and DocGen Permission Set Licenses and Permission Sets
  Permission set licenses incrementally provide user-level functionality for individual users. Permission sets are a collection of settings and permissions that give users access to various tools and functions.
• Contract Objects
  Vlocity CLM is native and additive to Salesforce. Vlocity CLM uses the standard Contract objectContractLineItem__c and extends it to integrate with the Opportunity, Order, Quote, Product, and Account objects.
• Vlocity CLM Custom Settings
  There are two types of custom settings—those you set for the entire org and those you set at the Contract Type level. This table summarizes the Vlocity CLM Custom Settings.
• Setting Up Multi-Language Support for Contract Life Cycle Management
  When you enable multi-language support, translated values are displayed in the generated Contract Documents. To set up multi-language support for CLM, perform the steps in the following procedures:
• Clauses
  Clauses specify a contract’s legal language and provisions, such as payment and warranty information. A clause typically contains one or more paragraphs of text, which is the clause content. For example, a payment clause may contain text that describes the terms of payment.
• Contract Types
  Contract Type is a custom object that specifies the type of the contract document. Using the Contract Type object, you can manage different types of contracts within one org. You can configure each contract type to provide access to the appropriate users, define stages and approvals for contracts, define clauses and templates specific to each contract type, and specify other parameters, such as DocuSign reminders. You can have different types of contracts with different state models, templates, clauses, DocuSign, such as nondisclosure agreements, sales contracts, and so on.
• Setting Up Custom File Name Formats
  For Microsoft Word and PDF documents generated in CLM, you can specify a custom file name format for the generated files. For example, you could define the format for your file names as follows:
• Frame Agreements
  You can use frame agreements to set up product-level, category-level, and account-level discounts and use them to drive pricing of future sales. Frame agreements can also hold general terms (non-pricing terms such as payment period, warranty duration, and so on).
• Setting Up DocuSign Integration
  Vlocity CLM uses DocuSign to support eSignatures. Using DocuSign, you can:
• Replacing Action Toolbars with the Vlocity Action Toolbar
  You can replace your existing action toolbars (a Visualforce page) with the Vlocity Action toolbar (a Lightning component) so that you no longer need to manually refresh the page.
• Setting Up Community Guest Users for Document Generation
  To enable community guest users for document generation, complete this series of setup tasks.
• Contract Administration Example
  In the example in the procedure, you want to create a new contract type named Nondisclosure Agreement that allows the Salesperson profile to create Nondisclosure Agreements and allows the Legal Analyst profile to create clauses and document templates that are applicable only to the Nondisclosure Agreement Contract Type.
• Fonts for Client-Side Document Generation in CLM
  Client-Side document generation supports default fonts, extended fonts, and additional extended fonts for Asian languages.
• Fonts for Server-Side Document Generation
  Server-Side document generation supports a specific set of fonts for Document Templates. Custom fonts aren't supported.
• Partner Communities Overview
  You can set up your partner community user to access the same CLM functionality as your internal end users. For server-side document generation to work, the execution mode for Integration Procedure must be set to Synchronous. Otherwise, document generation will fail for digital experience users.
• Set Up Customer Community User for Salesforce Industries
  Perform these tasks to set up the customer community (digital experience) user in Salesforce Industries for document generation. For server-side document generation to work, the execution mode for Integration Procedure must be set to Synchronous. Otherwise, document generation will fail for digital experience users.
• Set Up Customer Community Plus User for Salesforce Industries
  Perform these tasks to set up the customer community plus (digital experience) user in Salesforce Industries for document generation. For server-side document generation to work, the execution mode for Integration Procedure must be set to Synchronous. Otherwise, document generation will fail for digital experience users.
• Document Generation for Community Guest Users Overview
  Guest users can only use the docGenerationSample/singleDocxLwcGuestUser Omniscript to generate documents for opportunities, quotes, orders, or contracts. You must complete additional setup tasks and configuration to use the Omniscript.