Classify and map imported clauses

  • Release version: Yokohama
  • Updated January 30, 2025
  • 1 minute to read

    • Classify and map imported clauses to use the content from the clauses in a contract template.

    Before you begin

    A Microsoft Word document must have been uploaded and parsed to provide clauses for the contract template. For more information, see Create a contract template.

    Role required: sn_cm_core.contract_config

    About this task

    The imported clauses contain content that have been extracted from the Microsoft Word document that are marked by the content controls. Classifying and mapping the imported clauses builds a clause library of clause variations containing the content available in the imported clauses.

    For more information on clause variations, see Create a clause variation.

    Procedure

    1. Navigate to All > Contracts Core > Contract Administration > Contract Templates.
    2. Open a contract template.
    3. Navigate to the Imported clauses related list.
    4. Either update an existing clause variation with the content available in the imported clause or create a new clause or clause variation with that content.
      Usage of the imported clause dataSteps
      Do not update any of the existing clause or clause variation
      1. In the Classification field, select the drop down arrow.
      2. Select No change from the list.
      3. In the Mapping clause field, select an active clause from the clause library.
      Create a new clause and its clause variation
      1. In the Classification field, select the drop down arrow.
      2. Select New Clause from the list.
      3. In the Mapping clause field, do not take any action.
      Create a new clause variation
      1. In the Classification field, select the drop down arrow.
      2. Select Existing Clause from the list.
      3. In the Mapping clause field, select an active clause from the clause library.
    5. Select Complete Clause Mapping.
      • If the mapping is successful, the Clause Mappings related list displays the details of mapped clauses with their contract type.
      • If the mapping is not successful, an error message appears. Possible causes could include:
        • No contract type was selected.
        • All the clauses were not assigned a classification.
        • Clauses with the classification of New clause were mapped to a clause instead of being empty.
        • Clauses with the classifications of Existing clause or No change don’t have a clause mapped to them.
    6. Optional: View the clause variations associated with a clause by selecting the Display/hide hierarchical lists icon (Display/hide hierarchical lists for a clause.