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 Page Sections

Discovery Administration

Activating and Accessing Discovery

Follow these steps to activate a Conga Discovery instance and access it once it is established.

A one-time activation procedure requires Conga to have entered a license code for your tenant. Once you have activated your instance, access the Admin Dashboard from Conga Start.

Discovery Setup

Before you or any of your users can access Discovery, you must set it up.

Once you have set up the Discovery application to work with Contracts for Salesforce or Conga CLM, you must establish a connection to the AI engine that will extract your documents. Then, you must identify the types of agreement you expect to receive, and map for extraction the clauses you expect them to contain.

  1. Set up the app.
  2. Set up the AI provider.
  3. Establish the Provision Library.
  4. Map agreement types to extractions.

To set up the Discovery application, you must activate your instance. establish a connection to the AI engine that will extract your documents. Then, you must integrate the data sources you intend to use, identify the types of agreement you expect to receive, and map for extraction the fields, clauses, tables, obligations, and insights you expect them to contain. Some of these operations have been automated, but both automated and manual setup tasks are described.

You can also configure forward and reverse data sync with Salesforce, and create your own custom provision models.

Automated Configuration Assistance

Discovery offers extensive AI assistance to help you build the infrastructure it needs.

Configuring Discovery Automatically

While it is important to understand the components that make Discovery work, Discovery's AI can help with much of the configuration work.These steps describe using AI to configure your Discovery instance.
  1. Open the Discovery administrative home page as described in Accessing the Administrative Home Page.
  2. Click Agent Setup.
    This raises the Agent Setup window to the Upload stage.
    1. Inspect the available record type rules. Conga includes a starter set that you can edit here with natural language to make your extractions more specific.You can introduce new mappings as described in Manually Configuring a New Data Extraction Mapping.
    2. Drag and drop a sample file or click the Browse files button and open it wih your operating system's file manager.
      PDF or DOCX files no larger than 25 MB each are accepted. Files upload as soon as they are dropped into the frame.
    3. Discovery automatically detects and assigns the document type. If it cannot detect the document type, the field is left open for you to assign a document type mapping manually. A document type is required for each uploaded file.
    4. Click Analyze Documents.
      Discovery runs the documents past the mappings you selected, analyzing their contents, comparing them to available fields in CLM, and updating you of its progress.
  3. The Provisions step shows the results: provisions found in the document are ranked by the AI's findings and confidence scores into "Ready to Configure", "Requires Review", and "Missing from CLM". Discovery also suggests provision models available in the library or, where it finds a meaningful provision for which there is no model, it suggests making a new one. You can also click Create Custom Provision to build a new provision as described in Adding a Custom Provision Model (a pop-up gathers the new custom provision model information). When you are satisfied with the listed provisions, click Continue.

    Ready to Configure: Pre-trained field or clause provisions found in the uploaded document with a corresponding field or clause provision model already defined in CLM.

    Requires Review: Provision models that must be created. For clause-type provisions, the corresponding clause may not yet exist in the CLM clause library. For field-type provisions, a corresponding field must already be defined on the Agreement object in CLM.

    Missing from CLM: Pre-trained provision models for clauses found in the document but not yet defined in the CLM clause library.

    Suggested Existing Provisions: Pre-trained field or clause provision models that were not found in the uploaded document.

    Suggested New Provisions: Provision models Discovery recommends you create for fields or clauses that were not found in the uploaded document but are defined as fields or clauses in the CLM agreement or the clause library.

    Discovery synchronizes the provisions and generates contract risks and questions.
  4. Select risks and questions to review. You can edit or delete each risk or question.
    1. To edit a risk, click the edit () icon and amend the risk as you see fit. All fields are editable, and clearly written natural language describing is best. Select the worksheet mapping or mappings this risk applies to under Contract Type, and select any related provisions, and describe mitigation for this risk.
    2. To edit a question, click the edit () icon and amend the question and its context. The question appears above the AiMe user interface to save user input effort and provide consistent questions to return consistent results. As with risks, select the worksheet mapping and related provision, if any. The Context field ensures that this question will appear when this mapping is used for similar documents.
    3. When you are satisfied with the risk and question entries, click Continue.
    Discovery prepares the worksheet mappings and opens the Mapping step window.
  5. Select a record type from the Record Type pull-down. The default worksheet for the chosen record type displays initially, but you may select a better worksheet by selecting it from the Worksheet pull-down. If there is no default worksheet for the given record type, Discovery will create one. If you don't think any of the existing worksheets is appropriate, scroll to the bottom of this pull-down and select Create New Worksheet... to add your own custom worksheet.
    Note: You can map fields, clauses, risks, and questions by this method. To map specialty provision models like tables, picklists, or multi-picklists, you must manually configure them as described in Adding a Custom Provision Model and Adding a Custom Table Extraction Provision Model.
    1. When you have configured this worksheet, click Save Worksheet. .
    2. On success, click Complete setup.
The setup is complete.