Skip to main content
Conga Support

Configuring Contracts for Salesforce and Conga Contracts

You can enable the Conga Suite to integrate Conga Contracts for Salesforce (CCFS) and Conga Contracts. You must enable the suite common file storage system. You can create documents in Contracts for Salesforce and store the documents in Conga Contracts. Data is synched between systems. You must map objects and fields located in Conga Contracts for Salesforce to Conga Contracts objects. All fields, field values, the direction you want to sync data, and the primary system that wins conflicts.

Before you begin

Before you configure CCFS to communicate with Conga Contracts, you must enable the Conga Suite.

To ensure the suite is enabled: 

  1. In Salesforce, locate a Managed User -> Profiles -> System Administrator -> Apex classes -> profiles -> Edit. Select and move all Apex classes related to Platform. Click Save.
  2. Enable Visual Force page access. Select Edit -> All Apex classes.
  3. Add Remote site settings. Go to Conga Platform -> Active Platform file service -> Active.
  4. Add the Boolean field (for your customer, add customer fields). Add all Custom, Accounts and New Custom fields.
  5. Go to Contracts Setup tab, Select Platform and refresh to see the buttons enabled.
  6. Set up an external system. Go to Contracts Setup tab -> Platform -> Connect to Contracts. For example: quote-> opportunity-> opportunity name.

Enable the platform to store contract files

You must establish a connection between the platform, CCFS and Conga Contracts.

To set up connections in Conga Contracts:

  1. Click Connection in the tree. This creates a flag on the file object that denotes which one is going to be integrated with a field name.
    • In Composer, you'd look for field name. The following instructions assume you are using Composer to create a document.
  2. Go create a field. Name it IsCongafile and set the field to True. This integrates the field with Conga Contracts. If the field is set to False, it integrates it with CCFS.
  3. Link the Content Custom field and field value you used in in your Composer solution to create the document. Until the flag is set to True, nothing gets sent to repository. Everything stays in Salesforce. Files cannot be in both locations. 
  4. Establish a connection between systems.
    • In Contracts for Salesforce, go to the Platforms > Connect to the platform. The authorization component establishes the user access and authorizes all transactions between systems. 
    • Click Connect to access your files and enable transactions between CCFS a nd Conga Contracts.
  5. Give your system a new alias and Click Generate New Code. Copy the code to your clipboard. The code is redeemable for 48 hours only.
  6. In Conga Contracts, go to Admin > System Setting > Conga Platform. In Conga Contracts, select an alias. You are calling the other system so use a unique name that dictates what system you want to use, for example: SFprod or SFDev.

The external file repository logic connects CCFS to Conga Contracts. The Suite syncs the data of mapped fields and objects.

To disable the connection, you must turn off all the connections so that files are not lost. You see an error that you cannot disable the connection unless you delete all the connections.

Best practices and recommendations: 
  • Friendly name is no more than 30 alpha numeric characters
  • Copy code into the clipboards


  • Was this article helpful?