home

Sign for Advantage Platform

Adobe Sign ServicesAdvantage 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)Conga CopilotCPQ for Advantage PlatformCPQ for SalesforceDeal MaximizerDigital Commerce for Advantage PlatformDigital Commerce for SalesforceDiscovery AI 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 ExcelX-Author for Migration Manager for Advantage PlatformX-Author for Migration ManagerRelease NotesGeneralDocs by Release
Adobe Sign ServicesAdvantage 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)Conga CopilotCPQ for Advantage PlatformCPQ for SalesforceDeal MaximizerDigital Commerce for Advantage PlatformDigital Commerce for SalesforceDiscovery AI 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 ExcelX-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

Sign for Advantage Platform

Setting Up Conga Sign

Connecting Salesforce to Sign for Advantage Platform

Connection Prerequisites

To properly connect your Salesforce organization to Conga Sign on Advantage Platform, you must meet the following prerequisite conditions:

  1. Your Salesforce organization must be on-boarded with the Conga Advantage Platform.
  2. The authorizing user for Conga Advantage Platform must be created under the Salesforce IDP and log into the Conga Advantage Platform using their Salesforce login credentials.
  3. The authorizing Salesforce administrator must also be an active user that was created under Conga Sign Settings in the Conga Platform.
  4. Conga Platform must be connected to your Salesforce organization under Data Sync Connections in Conga Sign Settings.

Data Sync Connection

  1. Navigate to Conga Sign Settings under the Document Management application.
  2. Select Data Sync Connections.
  3. Among the list of available providers to connect to, you will see the following values:
    1. Provider - Name of the provider that can be connected to.
    2. User Name - Once connected, displays the user name of the individual who has connected to said provider.
    3. Status - Displays connection status.
    4. Actions - Displays the option to either Disconnect or Connect, depending on the Status.
  4. To connect to the provider, select the Connect action and follow the prompts in the pop-up window.
  5. To disconnect to the provider, select the Disconnect action.

Configuring Data Mapping Tags

The Data Mapping feature in Conga Sign allows you to link data fields from connected environments (like Salesforce) to signing tags in your transactions. This enables values to be automatically inserted into signing tags during transaction creation and written back to the source upon completion.
  1. Navigate to Conga Sign Settings under the Document Management application.
  2. Select Data Mapping.
  3. The data mapping page displays the following attributes:
    1. Data Mapping Table
      1. Active - Indicates whether the mapping is currently enabled. Active tags appear in the list of available tags in the Data Mapping helper.
      2. Target Source - The connected environment (e.g., Salesforce) from which the data is pulled.
      3. Target Object - The object within the target source associated with the data tag (e.g., Opportunity).
      4. Target Field - The specific field within the object linked to the tag (e.g., Billing Address).
      5. Tag Used With - The type of signing tag the data tag is used with (e.g., Text field).
    2. Creating a Data Mapping Field
      1. Follow these steps to create a new data mapping:

      2. Navigate to Conga Sign Settings under the Document Management application, and select Data Mapping under the left-hand navigation options.

      3. Click New Data Mapping. Enter the following details:

      4. Target Source - Choose the environment connected via the Data Sync Connections setup (e.g., Salesforce).
      5. Target Object - Select the object from the chosen target source (e.g., Opportunity).
      6. Target Field - Select a field from the chosen object.
        1. The following supported Salesforce field types will be displayed in the Target Field list:
          1. Checkbox
          2. Email
          3. Number
          4. Phone
          5. Text
          6. Text Area
          7. Text Area (Long)
          8. Text Area (Rich)
          9. URL
        2. Unsupported field types are not displayed in the list.

      7. Insert Field Value from Source - Enable this option if you want the current value from the source field to automatically populate in the signing tag when the transaction is created.

      8. Write Back to Source Field - Enable this option if you want the value entered in the signing tag by the recipient to sync back to the source field once the transaction is completed.

      9. Add Another - allows you to add multiple writeback fields at once, up to 5 writeback fields at a time.
    3. Click Save.
    4. Created tags are Active by default and are available for selection in the Data Mapping table.

Writeback Tags in Templates and Transactions

When creating a template or a new transaction, Administrators can utilize the Write Back Helper menu. Configuring writeback tags within templates can only be configured by Administrators, however the Write Back Helper is available for both Administrator and Users.

  1. Click Write Back Helper. The following elements are displayed:
    1. Target Source - shows which environments your organization is connected to which can have writeback tags created for it. Environments are connected via the Data Sync Connections instructions above.
    2. Target Object - shows which objects within the target source that have been configured for writeback tags.
      Note:

      Writeback only supports fields from the object your solution is being launched from. Ensure the source object you're selecting from is the same as the target button. Example, if your solution is launched from an Opportunity object, only use Opportunity writeback tags in your template and/or transaction.

    3. Field Table - shows the list of fields configured as writeback fields. This table only displays fields after the target source and object have been selected and displays the following elements:
      1. Target Field - the name of the field which will have recipient inputs written back to it.
      2. Target Field - the type of field which will have recipient inputs written back to it.
      3. Actions - allows you to copy a writeback tag value onto your computer clipboard.
        Note:

        When using multiple writeback tags for your template and/or transaction, it is recommended that all tags are copied into a text editor first for a cleaner and faster transfer of tags.

  2. Once a value has been copied to the clipboard, you can close the Write Back Helper window and select the tag used to collect writeback information.
  3. Click on the desired tag to open the Field Settings menu.
  4. Under Field Settings, paste the writeback tag into the Field Name input.
    Note:

    When using text fields, ensure that the Max Length field is set to 255 to maintain compatibility with Salesforce's text field character limit. If the Max Length field is not defined and a value longer than 255 characters is entered during signing, an error will occur and the input will not be saved back to Salesforce.

    If you are using the Text Tag Extraction feature rather than setting the name in the tag on the template, there are some limitations to keep in mind:

    • A tag can only have a maximum of 59 characters.

    • Any periods in the API Name must be replaced with a DOT in the text tag syntax.

      Example: Opportunity.PO_Number__c would need to be updated to Opportunity_DOT_PO_Number__c as the text tag syntax.

Creating Buttons for Salesforce

Once Conga Sign for Web has been connected to your Salesforce organization, you may create a button to send transactions from Salesforce objects.

Note:

The buttons created will only function if you have purchased and setup the Conga Sign for Web Connector.

Create a Send Transaction button:

  1. Navigate to Salesforce Setup.
  2. Select the Object Manager tab.
  3. Choose the Object for your Sign button. For instance, for sending transactions from an Opportunity record, select the Opportunity object.
  4. Select Buttons, Links, and Actions.
  5. Click on New Button or Link.
  6. Input a label. Example, "Send with Conga Sign." The Name field is automatically populated.
  7. Set Display Type to Detail Page Button.
  8. Copy and paste the following URL for your environment type into the markup area:
  9. Update the URL with specific values for your object and organization:
    1. RecordId: Update with the merge field for your object record ID.
    2. ObjectName: Update with the API name of your object.
    3. SalesforceOrganizationId: Update with your Salesforce Organization ID. For information on how to find your organization ID, refer to the Salesforce Help And Training Community.
    4. RecordName: Update with the merge field for your object record name.
  10. Click Save.
  11. Add the button to your object’s page layout. For information on how to modify a Salesforce page layout, refer to the Salesforce Help And Training Community.

Optional Parameters:

You can use the following optional parameters to enhance your Salesforce buttons:

  • templateid: Sets the template to be used when sending out a transaction. Retrieve the template ID from the Conga Platform by navigating to the desired template and copying the string after "/templates/" in the URL. Example: &templateid=d88tPOJgcT175aJCDZ5dkvFZ2IQ=
    Note:

    The templateid parameter must always be placed last in the parameter lineup. The = sign causes errors if placed it elsewhere in the lineup.

  • transactionname: Sets the name of the transaction. Example: &transactionname={!Opportunity.Name}+-+Quote
    Note:

    The transactionname parameter can be used in place of idprecordname but one of these parameters must be present for the solution to work.

  • recipient[1-20]: The 18 digit ID of a transaction recipient set via a User ID, Lead or Contact. You can designate up to 20 separate recipients, defined by incrementing numbers. Example: &recipient1=00Q3C000006U****,&recipient2=0053C000005yn****, etc.
    • As recipient IDs need to be 18 digits, you can use the CASESAFEID function in your Salesforce button to assure the value is accurate. Example: &recipient1={!CASESAFEID(Opportunity.Primary_ContactID__c)}
      Note:

      Based on the ID given, the First Name, Last Name, and Email must be taken from the record and populated into the respective fields of the recipient.

  • documentIds: Allows documents from your Salesforce org to be attached to the outgoing transaction. You can designate up to a maximum of 10 separate documents, defined by a comma delimited list. Example: &documentIds=0693C0000****,0678C0000****,etc.
    Note:

    The documentIds parameter must adhere to the following limitations:

    • Of the 10 documents, the consent document must be excluded from the list.
    • Templates added via the templateId parameter count toward the 10 document limitation.
    • If the OneSpan email delivery setting is enabled, an uploaded document may not exceed 5MB in size.
    • If the OneSpan email delivery setting is disabled, an uploaded document may be a maximum of 16MB in size.
  • isbackgroundmode: When set to True, this allows the Transaction to be sent without interacting with the Create Transaction UI. When enabled, the launching user is redirected to a loading screen and notifies the user of the success.
    • isbackgroundmode=true: Sends the transaction without directing the user to the Create Transaction UI after the button is clicked.
    • isbackgroundmode=false: Creates a transaction and redirects the user to the Create Transaction UI after the button is clicked.
      Note:

      The following prerequisite parameters are required for this parameter: &templateID, &recipient

Setting Template ID Dynamically

NOTE:

Warning: Conga Technical Support does not provide assistance with building nested IF statement formulas in Salesforce. It is recommended that you thoroughly test and validate any nested formulas before using them in a solution.

The templateid parameter allows you to identify a single Template ID when creating a new transaction. If a template needs to be selected dynamically based on the values of each individual record, you can use a Salesforce formula to accomplish this. For example, if you want to select a template based on the “Type” field when running your solution from an Opportunity, you can create a new formula field with the following details:

Data Type: Formula

Field Label: SignTemplateSelection

Field Name: SignTemplateSelection

Formula Return Type: Text

Formula Body: IF( ISPICKVAL( Type , 'Existing Business') , 'HnHJRtWnmgjUkeNDiRDu7-zWfeA=', 'VPlJwVw2qDJZonetQsHZvwLGmBc=')

Once the formula is created, use a merge tag to populate the templateid parameter. Following the example above, the parameter would be set as: &templateid={!Opportunity.SignTemplateSelection__c}

Create a View Transaction button

  1. Navigate to Salesforce Setup.
  2. Select the Object Manager tab.
  3. Choose the Object for your Sign button. For instance, for sending transactions from an Opportunity record, select the Opportunity object.
  4. Select Buttons, Links, and Actions.
  5. Click on New Button or Link.
  6. Input a Label. Example, "View Sign Transactions." The Name field is automatically populated by Salesforce.
  7. Set Display Type to Detail Page Button.
  8. Copy and paste the URL for your environment type into the button markup area:
  9. Update the URL with specific values for your object and organization:
    1. RecordId: Update with the merge field for your object record ID.
    2. ObjectName: Update with the API name of your object.
  10. Click Save.
  11. Add the button to your object’s page layout. For information on how to modify a Salesforce page layout, refer to the Salesforce Help And Training Community.

October 24, 2025