home

CLM for Salesforce

Adobe Sign ServicesAdvantage Platform AdministrationApprovals for Advantage PlatformApprovals for SalesforceBilling for Advantage PlatformBilling for SalesforceCLM for Advantage PlatformCLM for SalesforceContracts for SalesforceCollaborateComposer for Advantage PlatformComposer for SalesforceContractsConga for Google DocsConga Upgrade ProgramContract Intelligence (Standalone)CPQ for Advantage PlatformCPQ for SalesforceDeal MaximizerDigital Commerce for Advantage PlatformDigital Commerce for SalesforceDiscovery AI for Advantage PlatformDiscovery AI for SalesforceDocusign ServiceseSignature Integration with Advantage PlatformGridInvoice GenerationMix FormsOrchestrateOrder Management for Advantage PlatformOrder Management for SalesforcePartner Commerce for Advantage PlatformPartner Commerce for SalesforceQuote GenerationSign for Advantage PlatformSign for SalesforceSmart SearchTurboEnginesX-Author for Contracts 1.0 (Classic)X-Author for ContractsX-Author for Contracts Advanced for Advantage PlatformX-Author for Contracts Advanced for SalesforceX-Author for ExcelX-Author for Migration ManagerRelease NotesGeneral

Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

Show Contents

Show Page Sections

CLM for Salesforce

Agreement Lifecycle Management

download

Managing Offline Agreements

If you have a third-party paper that you want to use as a basis for your contract, Conga CLM provides you with the ability to create or import it as an offline agreement document. After an offline document is uploaded, Conga CLM tags it with metadata so that it can be checked out with X-Author for Contracts.

Conga CLM along with intelligent data extraction software enables you to run intelligent discovery on a third-party paper. The intelligently imported third-party paper is scanned by the optical character recognition method and converts the document to a searchable PDF.

Tip:

This documentation is created considering Kira and Conga AI as intelligent data discovery software.

Intelligent Discovery features need add-on licenses. Please get in touch with Conga Support for more information.

For information on creating an offline document using intelligent discovery, see Working with Offline Agreements.

Prerequisites

Kira is an intelligent data extraction software that enables you to intelligently import a third-party paper into Conga CLM. Before configuring Kira with Conga CLM, review the following topics:

Tip: Ensure you delete previously scheduled jobs related to Intelligent Discovery. If you do not delete previously scheduled jobs, duplicate extractions are visible.

To process a document using intelligent data extraction, users or user profiles must have access to the following objects in Conga CLM:

  • IDE Job
  • IDE Job Clause Extraction
  • IDE Job Field Extraction
  • IDE Map Clause Provision
  • IDE Map Field Provision
  • IDE Map Project Record Type
  • IDE Map Provision Record Type
  • IDE Provision

You can edit the following email templates that are available in Conga CLM to notify a user about intelligent discovery:

  • Intelligent Discovery Processing Error Notification
  • Intelligent Discovery Processing Status Update
Tip: Intelligent Discovery features need add-on licenses. Please contact Conga Sales Team for more information.

Configuring Intelligent Discovery Settings

Intelligent discovery settings must be configured to process documents using Intelligent Data Discovery (IDD). You must first configure remote site settings and then configure intelligent discovery settings.

Prerequisite

Please get in touch with Conga Support for the Remote Site URL, IDE Service URL, Logo URL, Tenant, Token, API URL, and API Token.

To configure intelligent discovery remote site settings

  1. Go to Setup > Security > Remote Site Settings.
  2. Click New Remote Site.
  3. Enter the Remote Site Name as IDD.
  4. Provide the Remote Site URL for IDD.
  5. Leave the Disable Protocol Security checkbox unselected.
  6. (Optional) Enter a description for the remote site setting.
  7. Select the Active checkbox.
  8. Click Save.

To configure XAJS and Merge Service remote site settings

  1. Ensure that you have configured XAJS End Point and Merge Webservice Endpoint comply system properties. For more information, see Comply System Properties.
  2. (Optional) Navigate to the Remote Site Settings page and ensure that XAJS and Merge Webservice endpoints are available.

To configure intelligent discovery settings for Kira

  1. Go to App Launcher > Intelligent Discovery Admin Console > Settings.
  2. Click New.
  3. Enter the following details:
    1. Name: KIRA
      Tip: The Name field value is case-sensitive.
    2. IDE Service URL: Enter the URL provided by Kira.Sample: https://ca.app.kirasystems.com/platform-api
    3. Logo URL: Enter the URL provided by Kira.Sample: https://ca.app.kirasystems.com/images/logos/kira-dark-on-light-54.svg
      Note: The Kira logo is displayed during Intelligent Import.
    4. Additional Setting: Add Kira API-related information in JSON or XML format.:

      Sample

      {

      "Version":"v1",

      "DefaultProjectId":120,

      "retrieveHighlightedDocument":false,

      "DeleteDocumentFromKira":true,

      “useAnalytics”:false

      }

      Note:

      Project ID

      The version may vary based on the Kira API. Default Project ID in KIRA is mapped to the default record type in Conga CLM.

      retrieveHighlightedDocument

      • If retrieveHighlightedDocument is set to true (case sensitive) then both processed and highlighted documents are retrieved to Conga CLM. If retrieveHighlightedDocument is set to false (case sensitive) then only the processed document is retrieved to Conga CLM. By default, the value for retrieveHighlightedDocument is considered as true.
      • The retrieveHighlightedDocument property is applicable only for documents less than 10 MB. If the document size is greater than 10 MB, both highlighted and processed documents are not retrieved to Conga CLM.

      DeleteDocumentFromKira

      If DeleteDocumentFromKira is set to true, the processed document is deleted from Kira. If DeleteDocumentFromKira is set to false, the processed document is not deleted from Kira. By default, the value for DeleteDocumentFromKira is considered as true.

      useAnalytics

      • useAnalytics is a User Experience Analysis component that collects product usage data. No action is required on your part and there is no impact to any existing product features, system functionality, or configured workflows. No personally identifiable information (PII), nor any other proprietary, confidential, or sensitive data will be collected.
      • If useAnalytics is set to true, the product usage data is collected. If useAnalytics is set to false, the product usage data is not collected. If useAnalytics value is not set, the value is considered false.
    5. Quick Study URL: Provide URL to launch Kira Quick Study when a user clicks Custom Provisions on the Intelligent Import Admin Console page.
    6. Active: Select the checkbox.
    7. Token: Add the Kira token.
    8. Show Token: Select the checkbox to view the token.
    9. API URL: Add the IDD URL.
    10. API Token: Add the IDD token.
    11. Show API Token: Select the checkbox to view the API token.
    12. Tenant: Enter the tenant name for IDD.
    13. Use Normalization: Select the checkbox to see the extracted values in the standard format.
  4. Click Test Connection to verify the accuracy of the above details that you have provided. If any details provided for a particular field are incorrect, you will see an error message related to that field. You can rectify the error and click Test Connection. If all the details provided are correct, you will see a message that the test was successful.
  5. Click Sync Provisions to sync IDE Provision checkbox to synchronize all provisions from the Intelligent server and save them in Conga CLM. If you click Sync Provision before clicking Test Connection, first the connection is tested and then the provisions are synced.
  6. Click Save.

To configure intelligent discovery settings for Conga AI

  1. Go to App Launcher > Intelligent Discovery Admin Console > Settings.
  2. Click New.
  3. Enter the following details:
    1. Name: CONGAAI
      Tip: The Name field value is case-sensitive.
    2. IDE Service URL: Enter the URL provided by Conga.Sample: https://cw-api-public-docusign-decp.services.cwacloud.net/auth/congaclm/api
    3. Logo URL: Enter the URL provided by Conga.Sample: https://conga.com/themes/custom/themeskit/images/branding/logo-conga.svg
      Note: The Conga logo is displayed during Intelligent Import.
    4. Additional Setting: Add Conga API-related information in JSON or XML format.} Sample:

      {

      "Version":"v1",

      "retrieveHighlightedDocument":false,

      "DeleteDocumentFromKira":false,

      }

      Tip: Conga recommends the values of retrieveHighlightedDocument and DeleteDocumentFromKira must be false.
    5. Quick Study URL: Provide URL to launch Conga AI Quick Study when a user clicks Custom Provisions on the Intelligent Import Admin Console page.
    6. Active: Select the checkbox.
    7. Token: Add the Conga AI token.
    8. Show Token: Select the checkbox to view the token.
    9. API URL: Add the IDD URL.
    10. API Token: Add the IDD token.
    11. Show API Token: Select the checkbox to view the API token.
    12. Tenant: Enter the tenant name for IDD.
    13. Use Normalization: Select the checkbox to see the extracted values in the standard format.
  4. Click Test Connection to verify the accuracy of the above details that you have provided. If any details provided for a particular field are incorrect, you will see an error message related to that field. You can rectify the error and click Test Connection. If all the details provided are correct, you will see a message that the test was successful.
  5. Click Sync Provisions to sync IDE Provision checkbox to synchronize all provisions from the Intelligent server and save them in Conga CLM. If you click Sync Provision before clicking Test Connection, first the connection is tested and then the provisions are synced.
  6. Click Save.

To delete intelligent discovery settings

  1. Go to App Launcher > Intelligent Discovery Admin Console > Settings.
  2. Click Delete.
    A confirmation is displayed.
  3. Click OK.
    The IDD setting is deleted from the IDD database.

Mapping Provisions to Project-Record Type

This section provides you with information about how to map provisions to the project-record type in Lightning.

Prerequisites

  • Ensure that you create project-record type mappings only in Lightning.
  • Ensure that the clause and field type IDE provisions are created.
  • Ensure that record types are available in Contract Management.

Restriction

You must not create project-record type mappings in Classic.

To add a project

  1. Go to Intelligent Discovery Settings > Intelligent Discovery Data Mapping > Map Project-Record Type.
    This displays the IDE Map Project Record Types page.
  2. Click New.
    This displays the Map Provisions page.
  3. Enter the Project Name and Record Type Name.The Clauses tab is highlighted by default.
  4. (Optional) Enter the Project ID if you have already created a project in Kira or Conga AI.If you leave the Project ID field blank, CLM creates a project in Kira or Conga AI, obtains the Project ID, and populates the Project ID field.
  5. Click Add.
    This displays the Add Provision Clauses popup that contains a list of clause type provisions and also the provisions which are neither clause nor field type provisions.
  6. Use the search box to search for a particular clause or select multiple clauses and click Add.
    Tip: If the value of the Template Reference field is blank, you need to enter the appropriate value before saving the clause provision or you will encounter an error.
  7. Scroll to the end of the page and click Save.
  8. Select the Fields tab.
  9. Click Add.
    This displays the Add Provision Fields popup that contains a list of field type provisions and also the provisions which are neither clause nor field type provisions.
  10. Use the search box to search for a particular field or select multiple fields and click Add.
    Tip: If the values of the Meta Data Field and Base Object field are blank, you need to enter the appropriate value before saving the field provision or you will encounter an error.
  11. Scroll to the end of the page and click Save.
  12. Select the Sync IDE Provision checkbox to update the provision details (base object, template reference, and metadata) in the default provisions list. All the clause and field provisions are selected by default. You can unselect the clause and field provisions that you do not want to sync to the default provisions list. If you do not select the Sync IDE Provision checkbox before saving the mapping, the changes to the provisions are not updated in the default provision mapping.
    Tip: When you select the Sync IDE Provision checkbox, clauses and fields are mapped to provisions.
  13. Click Save on the top-right corner of the page.

To edit a project or provision details

  1. Go to the IDE Map Project Record Types page.
  2. Next to the project name, click and select Edit.
    This displays the Map Provisions page.
  3. Hover on any field and click the edit icon () beside any editable field.This makes the field editable.
  4. Update the field and press Enter or click anywhere on the page.
    This updates the field.
  5. Perform one of the following tasks according to your requirement:
    1. Click Save on the top-right corner of the page.This saves the mapping but does not sync the provisions to the default provisions list.
    2. Select the Sync IDE Provision checkbox and click Save on the top-right corner of the page.This syncs all the provision details in the default provisions list and saves the mapping.
      Tip: When you select the Sync IDE Provision checkbox, clauses and fields are mapped to provisions.

To clone the provisions to project-record type mapping

  1. Go to the Map Provisions page.
  2. Click Clone.
    This displays a confirmation message.
  3. Click Ok.
    This clones the provisions to the project-record type mapping. The Record Type is not cloned.

To delete provisions

  1. Go to the Map Provisions page.
  2. Select the checkboxes beside the field provisions or clause provisions you need to delete.
  3. Click Delete.
    This displays a confirmation message.
  4. Click Delete.
  5. Scroll to the end of the page and click Save.

To delete the provisions from project-record type mapping

  1. Go to the IDE Map Project Record Types page.
  2. Next to the project name, click and select Delete.This displays the Delete IDE Map Project Record Type popup.
  3. (Optional) Select the Delete mapping from the AI Engine checkbox to delete mappings from Kira or Conga AI/Conga AI.If you leave the Delete mapping from the AI Engine checkbox unselected and click Delete, the mappings are deleted only from IDD.
  4. Click Delete.

Provisions Supported by Conga AI

Conga AI supports 41 provisions. The following table lists the supported provisions.

Fundamental Terms

Standard Terms - Fields

Standard Terms - Clauses
  • Agreement Title
  • Parties
  • Effective Date
  • Commencement Date
  • Original Expiration Date
  • Termination Notice
  • Renewal Type
  • Renewal Period
  • Renewal Notice
  • Renewal Limit
  • Signatures
  • Notice
  • Notice Address
  • Related Master Agreement Name
  • Total Contract Value
  • Audit Rights
  • pricing/Billing Frequency
  • Data Security Breach Notification
  • Dispute Resolution
  • Exclusivity/Not granted
  • Exclusivity/Required
  • Governing Law
  • Indemnification Provision
  • Non-Solicitation Period
  • Pricing/Payment Model
  • Pricing/Payment Terms
  • Confidentiality
  • Assignment
  • Contract Rate
  • Compensation
  • Indemnification
  • Insurance
  • Intellectual Property
  • Licenses
  • Productivity
  • Publicity
  • Reps and Warranties
  • Force Majeure
  • Integration
  • Notice Section Clause
  • Dispute Resolution Clause

Setting Up Salesforce and Kira Single Sign-on

You can set up single sign-on to authorize users to access Salesforce and Kira with one login.

Prerequisite

You must have a Kira Enterprise Edition license.

To set up single sign-on

  1. Set up Salesforce as an Identity Provider. For more information, see Salesforce documentation .
  2. Set up Kira as a Service Provider. For more information, contact Kira Support.

Configuring Intelligent Discovery Status Panel in Lightning

You must configure the intelligent discovery status panel in lightning to view intelligent discovery processing status.

Prerequisite

You must configure Intelligent Discovery settings. For more information, see Configuring Intelligent Discovery Settings.

To configure the Intelligent Discovery Status panel

  1. Navigate to the Agreement Detail page.
  2. Click the Setup icon and select the Edit Page option.
  3. In the left panel, search for Intelligent Discovery Status.
  4. Drag Intelligent Discovery Status from the left panel and drop on top of the Agreement Actions panel.


  5. (Optional) If you add the Intelligent Discovery Status panel other than top, select the Intelligent Discovery Status panel and unselect the Intelligent Discovery Status Panel on Top checkbox in the Pages section on the right-side.
  6. Click Save.

Migrating Mappings from Salesforce to Intelligent Data Discovery

Tip: This topic is applicable only for Kira users. You cannot migrate mappings from Kira to Conga AI.

You can migrate existing mappings and settings from Salesforce to Intelligent Data Discovery (IDD). After you have migrated the existing mappings, you can perform any of the following tasks according to your requirement:

  • You can leave Project ID in the mapping as it is.
  • If you need to use a different project that you have created in Kira, you must edit the mapping and manually enter the project ID from Kira in the Project ID field in CLM. The Project ID field cannot be left blank after you edit a mapping.
  • If you create a new mapping in CLM, CLM creates a project in Kira, obtains the Project ID from Kira, and populates the Project ID field in CLM automatically. For information regarding editing mappings, see Mapping Provisions to Project-Record Type.

To migrate mappings

  1. Go to App Launcher > Intelligent Import Admin Console > Settings.
  2. Click the Edit hyperlink of an existing configuration.
  3. Update the following details:
    1. API URL: Add the IDD URL.
    2. API Token: Add the IDD token.
    3. Tenant: Enter the tenant name for IDD.
  4. Click Test Connection.
  5. Click Sync Provisions.
  6. Click Save.
  7. Go to Intelligent Discovery Settings > Intelligent Discovery Data Mapping > Map Project-Record Type.
  8. Select a mapping.
  9. Click the Edit button.
  10. Click Save.

Configuring Intelligent Discovery Fields

You can configure fields displayed on the Agreement Detail tab when you review a third-party agreement document imported through Intelligent discovery.

To configure fields on the Agreement Detail tab

  1. Go to Setup > Object Manager > Agreement > Field Sets > Update Fields Intelligent Import Field Set.
  2. Drag the fields from the object palette and drop them into the In the Field Set container.
  3. To make a field as required, double click the field or click the wrench icon () next to the field.
  4. Select the Required checkbox and click OK.
  5. Click Save.

Setting Up Conga Contract Intelligence

You must configure the Conga Contract Intelligence widgets on the Home page and the Agreement Detail page in CLM to use Contract Intelligence for importing documents. After you set up the contract intelligence components in CLM, you must set up the Contract Intelligence application. For more information, see Setting Up Contract Intelligence for CLM.

Prerequisites

  • You have a Conga Contract Intelligence license.
  • You have used the APTS_CCIImportAgreementStatusCategory admin entry to configure the visibility of the Intelligent Document Import button on the agreement detail page. For more information, see Admin Entries.
  • You have enabled the Enable Document Versioning and Enable Version Control comply system properties or the agreement is version-aware. For more information, see Comply System Properties.
  • You have configured the integration setting. For more information, see Configuring Integration Settings.
  • You have activated remote site settings (IntegrationSettingProd and IntegrationSettingSandbox), and CSP trusted sites (IntegrationSettingsProdURL and IntegrationSettingsSandboxURL). For more information, see Connecting to External APIs.
  • You have configured the Salesforce CORS configuration allowlist with the API URL as the origin URL pattern for the CCI host. For more information, see Configure Salesforce CORS Allowlist.

Limitation

You can only use DOC, DOCX, and PDF file types to import documents.

To configure CCI widgets on the Home page

  1. Navigate to the Home page.
  2. Click the Setup icon and select the Edit Page option.
  3. In the Components search box, enter CCIAdminContainer.
  4. Drag and drop the CCIAdminContainer component at any position on the Home page.
    Note:

    You must set component visibility for the CCIAdminContainer component only for administrators.

  5. In the Components search box, enter CCIUserContainer.
  6. Drag and drop the CCIUserContainer component to any position on the Home page.
  7. Click Save.
    The following screenshot displays the CCI widgets (Conga Contract Intelligence - Admin Actions and Conga Contract Intelligence - Intelligent Document Import) on the Home page.


To configure Contract Intelligence widgets on the Agreement Detail page

  1. Navigate to the Agreement Detail page.
  2. Click the Setup icon and select the Edit Page option.
  3. In the Components search box, enter CCIUserContainer.
  4. Drag and drop the CCIUserContainer component at any position on the Agreement Detail page.
  5. Click Save.

    The following screenshot shows the CCI widget (Conga Contract Intelligence - Document Actions) on the Agreement Detail page.



Administrator Guide
CLM

January 29, 2025