To help you learn and configure Discovery custom flows faster, Discovery includes default data extraction mappings in the base package.

1. From Conga Start, click Admin Console > Discovery Agent > Admin Dashboard.
2. Click Data Extraction Setup in the left navigation bar.
   This raises the Data Extraction Setup page.

   

3. Clicking the hypertext names of any of the mappings exposes pre-configured fields and clauses. Study these to discern the structure of well-formed data extraction mappings.

1. Click the Data Extraction Setup tab in the left navigation bar to raise the Data Extraction Setup window.
2. Click the New button.
   This raises the New Document Extraction Mapping pop-up.

   

3. Give the new mapping a name, enter a brief description, and choose a record type from the Choose database record pull-down menu.
   The database record value corresponds to a particular contract or document type (such as MSA or SOW) to be imported by Discovery. For example, in a CLM deployment, this shows agreement records.

   CAUTION:

   Once a data extraction setup is created, you cannot modify the Database Record field to change from one record type to another, nor is the clone feature available. A mapping error may result in a complete rework with a new data extraction setup.

   In the Advantage Platform, database records, also called record types, are used to categorize contracts by type and to define which fields, clauses, and extraction logic to apply. Because each contract type has unique clauses and data fields, mapping each extraction to one record type ensures that extractions are performed based on the contract type selected.

   You can create only one data extraction setup for each database record type. To support different extractions of the same database record type (for example, “NDA-America” vs. “NDA-EMEA”), use multiple worksheets under the same data extraction mapping.

   CAUTION:

   Do not map a provision model to more than one field or clause. If a reviewer modifies a provision model mapped to multiple fields or clauses, there will be conflicts that affect the provision model’s performance.

4. Select review levels in the Choose review level pull-down menu.
   • To deactivate the requirement to review, select 0: Skip Review. Document review will be skipped and no contract summary will be generated or saved to CLM.
     Note:

     When a skipped document is successfully extracted, the Reviewed By field remains blank and the file is assigned a Completed status. If any field’s extracted value cannot be normalized to match its data type, the file is assigned a Ready for Review status and must be reviewed. On review, the document’s Reviewed By field is populated by the document reviewer’s user name.

   • To use a single-stage review process, select 1: One level - Review and Complete from the Review Level pull-down menu. You must then select a reviewer from the resulting Reviewer pull-down.
   • For a more formal process, select 2: Two levels - Review and Approve from the Review Level pull-down menu. You must then select a reviewer from the Reviewer pull-down menu and an approver from the Approvers menu.
5. To let users to check out batches of documents for review, slide the Allow reviewers to get next batch toggle on and then set the batch size. This enables users to check out a block of records of the designated number with a single “get batch” action. Users cannot request a new batch until they review or reassign all documents currently assigned to them.
6. Under Import Options, select extraction options to make available to your users. These are:
   • OCR to import the document as searchable text
   • Automated Extraction to submit the document for AI-only extraction, or
   • Verified Extraction to submit the document for AI extraction with attorney review.
   These choices are not mutually exclusive.
7. Depending on whether this is a purchase or vendor agreement, set the Organization Role? toggle to either Buyer or Seller.

   This setting contextualizes the generative AI prompt for Insights. Depending on this setting, the customer or user is presented to the AI engine as a buyer or seller. The default position is Seller. This setting doesn’t change which provisions are extracted but changes how the AI interprets the company’s position: with Organization Role set to Buyer, a one-sided limitation-of-liability clause protecting the counterparty can be flagged as a risk, rather than being read as routine boilerplate protecting the (incorrectly assumed) selling party. Contract types where the company’s role varies by deal, such as licensing agreements it both buys and sells, may need one mapping for each role.

8. If you want reviewers to be able to extend the worksheet with additional detected provisions as described in Adding Unmapped Fields and Clauses, slide the Allow Worksheet Extension toggle on.
   Note: Adding an unmapped value links the identified passage to the appropriate provision map, associating it with the corresponding fields, clauses, or values defined in the CLM schema. Future document imports will recognize and extract these new provisions, but this update does not retroactively apply to previously imported documents.
9. Click SAVE.

1. Click the Data Extraction Setup tab in the left navigation bar to raise the Data Extraction Setup window.
2. Click the hypertext name of the map that you will edit in the Name column.
   This raises the worksheet mapping window.

   

3. Click the WORKSHEETS tab.
4. Select the worksheet you will edit from the Choose Worksheet pull-down menu.
5. Select the Fields, Clauses, Tables, Insights, or Obligations tab, then click MANAGE PROVISIONS or NEW to raise the corresponding mapping pop-up.
   • For fields, click MANAGE PROVISIONS and continue to the next step.
   • For clauses, an Automatic Clause Comparison toggle appears. Activating this enables automatic clause comparison for all documents during import as described in Reviewing Imported Clauses and Fields. If this is turned off, the reviewer does not see the comparison summary, but it remains available on reviewer request. Click MANAGE PROVISIONS and skip to step 7.
   • For obligations, click NEW and skip to step 8.
   • For tables, a Default Orientation pull-down appears. Configure the anticipated table orientation as described in Horizontal and Vertical Tables. Click NEW and skip to step 9.
   • For insights, click NEW and follow the process described in Insights Setup.
6. Click Select Field(s) to Map in the Map Fields window.
   1. Select one or more fields by clicking the adjacent checkbox in the Select Field(s) to Map pop-up.
   2. For each field you select, choose either Auto Extraction or Manual Extraction.

      • Provisions marked for auto-extraction are automatically extracted by the system and available for review.

      • Provisions marked for manual extraction require the end user to map and approve the field value manually on the review screen. Manual extractions require no further provision configuration.

      CAUTION:

      If you select Manual Extraction, you will lose any configuration information for this mapping.

   3. Some field types offer a Permit New Record Addition option. Check this box to enable reviewers to add new records. If you pick this, you must add the types of records a reviewer can add.
   4. Click Add/Edit Provision Mapping to select the provision model or models to associate with the field you are defining.
      Tip:

      If you choose multiple similar provision models, your mapping will be more likely to find a field, but also more likely to find an incorrect one. Your reviewers must assign the result to one provision model or another, so a more selective approach is usually indicated.

   5. For fields associated with lookup values (values already defined in CLM), an additional control, Allow to add new record appears. Select this to enable reviewers who encounter lookup values to add lookup values to CLM from the extraction. If this is selected, you must select the associated lookup fields from the object’s Account Values drop-down menu. The reviewer will have to enter these fields manually to generate a new record.
      Note:

      • You can configure at most 70 fields and clauses in one mapping.
      • You can configure no more than ten insight questions in one mapping.
      • You can configure no more than five criteria in an insight.
   6. Click DONE. You are returned to the WORKSHEETS tab view.
7. Click Select Clause(s) to Map or Create a Clause to Map.
   You will add clauses to your mapping either by selecting existing ones or by creating your own.
   1. If you choose to select clauses, choose the pertinent clause from the Add Clauses from Library pop-up. If you elect to create a clause to map, you are taken directly to the Map Clauses window to configure your clause mapping.
   2. If you are creating a clause, you must name it. If you have selected one, it already has a name, which you cannot edit.
   3. Select the Make this a Required Field checkbox to make the extraction required.
      When an extraction is required, the reviewer cannot complete the review without a value for the provision.
   4. For each clause you select, choose either Auto Extraction or Manual Extraction.

      • Provisions marked for auto-extraction are automatically extracted by the system and available for review.

      • Provisions marked for manual extraction require the end user to map and approve the field value manually on the review screen. Manual extractions require no further provision configuration.

      CAUTION:

      If you select Manual Extraction, you will lose any configuration information for this mapping.

   5. Enter the default value. If there is no extraction, this value is assigned to the provision.
      For workflows set to Skip Review (review level 0), this field must have a value.

      Note:

      When a default value is assigned to a provision, it appears in the reviewer’s Provisions Found section, clearly marked as a default value. A default value does not fail validation checks for required fields.

      • If the reviewer modifies the default value or marks it as reviewed, the updated value is saved to the agreement record.
      • If the user does not modify the default value or mark it as reviewed, the default value is saved to the agreement record.

      Default values are not sent to the AI engine for training.
   6. Select the provision models to apply from the Available Provisions list and click the right-arrow icon to move them to the “Mapped Provisions:” list.

      
      
      

      Tip:

      • You can narrow your provision model choices dramatically by entering one or more words in the search bar.
      • Hovering over a provision model type in the Available Provisions column raises explanatory text describing the model.
   7. For clause extractions, you must also choose whether to extract the complete paragraph in which the clause is found. If this is unchecked, the AI extracts only the matched text.
   8. Click Add/Edit Provision Mapping to select the provision model or models to associate with the clause you are defining.
      Tip: If you choose multiple similar provision models, your mapping will be more likely to find a clause, but also more likely to find an incorrect one. Your reviewers must assign the result to one provision model or another, so a more selective approach is usually indicated.
   9. Click DONE. You are returned to the WORKSHEETS tab view.
8. For obligation extractions, clicking the Obligations tab raises a grid view of existing obligations. Click the obligation you will edit, then the More icon (), then select Edit to raise the obligation edit pop-up.

   

   You can choose either Auto-Extraction or Manual Extraction.

   Note:

   • Obligations are fully defined in CLM. This setting controls the one feature that Discovery introduces. For more on configuring obligation objects from CLM, see Obligations in the CLM user guide, which contains sections on Creating an Obligation and Obligation Fulfillment in the Classic UI.
   • You can configure at most ten obligations in one mapping.
   • You can introduce at most five fields per obligation.
9. Select the table provision and choose either the automatic or manual extraction method. Click SAVE to commit the table provision to the mapping.
   Selecting Manual Extraction ends the configuration. Reviewers must extract the table manually, and no further configuration is possible.
   Note: You can only map one CLM object per table mapping. You cannot map two tables with a common agreement line item in one mapping. You can configure at most ten tables in one mapping. You can configure at most ten columns per table.
10. Click DONE to save the mapping.

1. Click the Data Extraction Setup tab in the left navigation bar to raise the Data Extraction Setup window.
2. Click the name of the map with the worksheet you want to clone.
3. Click the Worksheets tab.
4. Select the worksheet you want to clone from the Choose Worksheet drop-down menu.
5. Click WORKSHEET ACTIONS > Clone.
6. Enter a name for the worksheet, select the target record type, and check the component you want to clone.
   You can clone any or all of the clause, table, field, insight, and obligation components.
7. Click SAVE.

1. Click the Data Extraction Setup tab in the left navigation bar to raise the Data Extraction Setup window.
2. Click the hypertext name of the map that you will edit in the Name column.
   This raises the worksheet mapping window.

   

3. Click the WORKSHEETS tab.
4. Click WORKSHEET ACTIONS and select NEW from the drop-down menu or select CLONE and edit the cloned mapping.
   Tip:

   If you are starting from scratch, look for an existing worksheet to clone. Many orgs are deployed with pre-configured sample worksheets that you can use as a starting point.

5. In the New Worksheet pop-up window, enter the new worksheet’s name and a brief description. Click the Default Worksheet checkbox to make this worksheet the default when a document of this type is imported.
6. Click the tab for the type of worksheet you will create: Fields, Clauses, Tables, Insights, or Obligations, and follow the linked documentation to complete your worksheet.