Learn to configure a Composer button that generates an agreement in Contracts for Salesforce. Once created, the agreement can be sent for negotiation with Contracts for Salesforce or sent for signature with Conga Sign (or your integrated e-signature solution).

Key components 

  • DataTagEnable parameter to ensure changes can be tracked and synced back to Salesforce
  • RM parameter to ensure that any merge fields in clauses will also be merged with their corresponding Salesforce values
  • Conga Queries to gather Managed Clauses
  • Microsoft Word document generation that attaches to Salesforce Files on the Master Object
  • (Optional) WPD parameter and Textboxspecial merge field to ensure only certain fields are editable


This topic assumes a basic understanding of Conga functionality, including how to create:

Building the Button

Once you are comfortable with the components mentioned above and have configured your Clause Library (or part of it), follow the steps below to build a solution that generates a Contracts for Salesforce agreement.

  1. Create a Composer Button
    1. Using a Solution record, build a base Composer button for Contracts for Salesforce on the object you have configured to use with Contracts for Salesforce (we will use the managed package Contract Agreement object)
    2. Ensure that your button includes the required Contracts for Salesforce parameters, &RM=1 and &DataTagEnable=1 At this point the button will look something like this: /apex/APXTConga4__Conga_Composer?serverURL={!$Api.Partner_Server_URL_370}&Id={!APXT_Redlining__Contract_Agreement.Id}&DataTagEnable=1&RM=1
    3. Save the Solution record
    4. Add the button to your object’s Lightning page. We recommend using Dynamic Actions

      At this point, you will not have any queries or a Conga Template included in your button

  2. Add SOQL Queries to Retrieve Managed Clause Data
    1. On the Solution record, add your Managed Clause queries to the solution. If you have not created these or need to learn how to do so, refer to Step 2 in Configuring a CLM (Contracts for Salesforce) Word Template Solution
    2. Save the solution and update the button
  3. Add the TemplateId parameter to the solution
    1. On your Solution record, add the TemplateId parameter
    2.  Populate the parameter with the Conga Key value of your Conga Template, or if you have not created that yet then just leave it blank
    3. Save the solution and update the button
  4. Review button URL for accuracy
    1. The button should look something like this:

  5. Add additional parameters as desired. Many solutions also include the following parameter/value pairs:
    1. &SC0=1, &SC1=SalesforceFile
    2.  &DS7=11
    3. &UF0=1, &MFTS0=APXT_Redlining__Status__c, &MFTSValue0=Generated

Once you have built the button, you will need to create your Word template and test the solution. Refer to steps 4-6 in Configuring a CLM (Contracts for Salesforce) Word Template Solution for more information.