home

CLM for Salesforce

Adobe Sign ServicesAiMeAdvantage 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 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 SearchTest AuthorTurboEnginesX-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 Excel for SalesforceX-Author for Migration Manager for Advantage PlatformX-Author for Migration ManagerRelease NotesGeneralDocs by Release
Adobe Sign ServicesAiMeAdvantage 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 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 SearchTest AuthorTurboEnginesX-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 Excel for SalesforceX-Author for Migration Manager for Advantage PlatformX-Author for Migration ManagerRelease NotesGeneralDocs by Release

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 Management

Merge Documents in Salesforce Lightning

This feature allows you to combine the latest versions of different agreement documents along with the documents uploaded to the version aware agreement in Salesforce Lightning. You can merge the documents in different formats (DOCX, DOC, and PDF formats) into one DOCX or PDF document.

You can set the following preconditions before generating the merged document:

  • Document type
  • Document permission
  • Watermark
  • Redlines
  • Order of the documents

If all the documents you are merging are in DOC or DOCX format, you can select the output format (DOCX or PDF). If the documents you are merging contains at least one PDF, the PDF output format is selected by default and the DOCX output format is disabled.

If you have selected DOCX as the output format, you can select any protection type. The protection type is only applicable to DOCX documents.

If a DOCX document contains the draft watermark among the DOCX documents you need to merge and you select the Remove Draft Watermark option, the merged document will not retain the watermark from the original document. The Remove and Apply Draft Watermark option is only applicable to DOCX documents but not for PDF documents.

If you have redlines in the documents you need to merge, you can use the Preserve Redlines option to retain the redlines in the merged documents.

You can select any document type except for the Executed Document. By default, the Agreement Document option is selected.

Restrictions
  • The Merge button is disabled if the agreement is in the following Status | Status Category:
    • In Signatures | Other Party Signature
    • In Signatures | Fully Signed
    • In Effect | Activated
  • The Document Permission field is not visible when you select PDF as the output format.
Limitations
  • The merge document name must not exceed 250 characters.
  • The document size of the combined documents must not exceed 25 MB.

Merging Documents

  • You need to set up new agreement protection for merge documents. For more information, see the topic Configuring Agreement Document Protection.
  • You can merge the documents in DOC, DOCX, and PDF format in version-aware agreements.
  • Ensure that you have at least two different documents (documents generated using different templates) available in your agreement.
  • You can use the APTS_AppendVersionNumberToMergedDocs admin entry to suffix the name of the merged documents with a version number. For more information, see Admin Entries.
  1. On the Agreement Detail page, click Merge Documents.
    This displays the Merge Documents page.
  2. Enter a name for the merged document in the Document Name field.
  3. Select DOCX or PDF as the merged document output type.
  4. Select Retain Header and Footer to retain the header and footer of the original documents in the merged documents. (Or)Select Custom Header and Footer to see Header and Footer fields and add custom header and footer.
    Note:

    If no custom header or footer is selected in the UI and auto header/footer is not configured in comply system properties, the Merge Engine's JoinDocuments action prints the default footer by default. The left half shows the attachment file name, and the right half shows the cumulative page number. This is the standard behavior only when merging PDF or PDFs with other formats (at least one PDF is selected for joining). However, if all input documents are DOC, DOCX, or RTF, no default header or footer is populated.

    When the APTS_DefaultHeaderFooterOptionForMerge admin entry is configured, you can see either the Retain Header and Footer or Custom Header and Footer checkbox selected by default. For more information, see Admin Entries.

  5. Select a document type for the merged document.
  6. Select document permission for the merged document.
  7. Select a watermark option per your requirement either to apply or remove watermark in the merged document.
  8. Select the Preserve Redlines checkbox to retain the redlines in the merged document.
  9. Drag and rearrange the documents in the order you need to merge documents.
  10. Select the documents that you need to merge.
  11. Click the Merge button on the top of the page.
    You are navigated to the Agreement Detail page.
  12. Navigate to the Related tab.
  13. In the Document Versions section, click the Merge Documents hyperlink.
    This displays the Document Versions Detail page.
  14. Click the View hyperlink.

    If you had selected DOCX as the output format, then a new tab and the merged document is downloaded to your system. If you had selected PDF as the output format, then the document opens in the document viewer online.

    The merged document is now available when you send for review, send for eSignature using EchoSign, send for manual signature, and activate an agreement.

Use Case: Merging Agreement Documents within CLM Salesforce

This use case describes merging multiple agreement documents into a single consolidated document for easier review, sharing, and processing.

  • The agreement record contains two or more documents available for merging.

  • Documents are in supported formats (DOC, DOCX, PDF).

  • User has permission to access and merge documents.

  • Agreement is not in a restricted status (for example, Fully Signed or Activated).

Business Context

Agreements often include multiple documents such as agreement documents, supporting files and/ or Appendixes. Managing them individually can slow down contract review and collaboration. This feature enables users to combine selected documents into a single output document, improving efficiency and ensuring a consistent, unified contract deliverable.
Stakeholders
  • Primary:

    • CLM User

  • Secondary:
    • Conga CLM System

Trigger

The user selects Merge Documents from the Agreement record.

  1. User navigates to the Agreement record in Salesforce.
  2. User clicks Merge Documents.
  3. System displays the merge configuration page.
  4. User enters a name for the merged document.
  5. User selects the documents to merge.
  6. User defines the order of the documents.
  7. User selects the output format (DOCX or PDF).
    Note: Merge fails if document size exceeds limits or unsupported formats are used.
  8. User configures merge options such as retaining headers and footers, preserving redlines, and applying or removing watermarks.
  9. User clicks Merge.
  10. System generates a single merged document.
  11. System saves the merged document to the Agreement record.
A merged document is created and attached to the Agreement record. The output reflects selected order and configuration.The document is available for further processing and audit tracking.
User Guide
CLM

October 12, 2026