Setting Up Salesforce

You have logged in to Salesforce.
You have created an integration user (as described in Adding a User) with the Apttus__ComplySystemProperties__c custom property and with these object permissions:
- Apttus__APTS_Agreement__c: Read, Create, Update
- Account: Read
- Contact: Read
- Apttus__Agreement_Clause__c: Read, Create, Update
- Apttus__AgreementLineItem__c: Read, Create, Update
- Apttus__DocumentVersion__c: Read, Create, Update
- Apttus__DocumentVersionDetail__c: Read, Create, Update
- Template__c: Read

Create an External Client App

Go to Setup () > PLATFORM TOOLS > Apps > External Client Apps > External Client App Manager and click the New External Client App button.
Basic Information:
1. Enter the company name in the External Client App Name field.
  This automatically populates a compatible name value in the API Name field.
2. Enter the administrator’s email address in the Contact Email field.
3. Accept the default value, Local, in the Distribution State field.
Open API Enable (OAuth Settings) and check (enable) the Enable OAuth checkbox, opening the App Settings, Flow Enablement and Security configuration panels.
In App Settings:
1. Enter your domain (URL) in the Callback URL field.
2. Under OAuth Scopes, select Full Access (full), and Manage user data via APIs (api) and click the right-arrow icon () to move them into the Selected OAuth Scopes column.
3. Select Introspect all Tokens.
In Flow Enablement, select Enable Client Credentials Flow, Enable Authorization Code and Credentials Flow, and Enable Device Flow.
In Security, let the default-on security settings, Require secret for Web Server Flow, Require secret for Refresh Token Flow, and Require Proof Key for Code Exchange (PKCE) extension for Supported Authorization Flows stand. If they are not activated, click the adjacent checkboxes to enable them.
All other settings are optional and not required for this task. Accepting the default values is a good idea for most setups.
Click Create.
The app is created and more configuration options are presented.
Open Settings > OAuth Settings > App Settings and click Consumer Key and Secret. You may be challenged to authenticate. Copy these and store them safely.

Note:
The consumer key and consumer secret are required for Conga Platform data sync setup.
Open the Policies tab.
1. Click Edit.
2. Move system administrator and API-only profiles to Selected Profiles.
3. Under OAuth Flows and External Client App Enhancements, select Enable Client Credentials Flow, and enter the integration user’s name in the Run As (Username) field.
Click Save.

Enable OAuth Flows

Go to Setup > Identity > OAuth and OpenID Connect Settings.
Enable OAuth Username-Password Flows.

Create Remote Site Settings

Go to Setup > Security > Remote Site Settings.
Click New Remote Site.
1. Enter CongaRLS_CLM in the Remote Site Name field.
2. In the Remote Site URL field, enter https://login-rlspreview.congacloud.com in the Sandbox field and https://login-rls.congacloud.com in the Production field
3. Click Save & New.
4. Set Remote Site Name to RLSCloud.
5. In the Remote Site URL field, enter https://preview-rls09.congacloud.com in the Sandbox field and https://lprod-rls10.congacloud.com in the Production field.
6. Click Save.

Add Trusted URLs

Go to Setup > Security > Trusted URLs.
Click New Trusted URL.
Enter Company Name_CCI in the API name field, https://preview-rls09.congacloud.com in the Sandbox field, and https://prod-rls10.congacloud.com in the Production field.

Add CORS URLs

Go to Setup > CORS > Add New > Add Platform URL.
Enter https://login-rlspreview.congacloud.com in the Sandbox field and https://login-rls.congacloud.com in the Production field.

Add an Authentication Provider

Go to Setup > Settings > Identity > Auth. Providers.
Click New.
Select Open ID Connect from the Provider Type drop-down list.
This opens the Auth Provider Edit window for Open ID Connect.
In the Auth Provider Edit window:
1. Enter APTS_RLPInstanceSettings in the Name field.
  
  Note:
  The Auth Provider and Admin Entry names must be the same.
2. Enter Auto Populated in the URL Suffix field.
3. Enter the client ID and secret you generated in Add an API-to-API Connection in the Consumer Key and Consumer Secret fields.
4. In Authorize Endpoint URL, enter https://login-rlspreview.congacloud.com/api/v1/auth/connect/token in the Sandbox field and https://login-rls.congacloud.com/api/v1/auth in the Production field.
5. In Token Endpoint URL, enter https://login-rlspreview.congacloud.com/api/v1/auth/connect/token in the Sandbox field and https://login-rls.congacloud.com/api/v1/auth/connect/token in the Production field.
Click Save.

For region-specific URLs and additional details, see Configuring a New Authentication Provider.

Create an Admin Entry

From the Lightning Experience:

Go to App Launcher > Admin.
Click New.
Create an admin entry.
Name: APTS_RLPInstanceSettings
Note:
This name must match the Auth Provider name created in Add an Authentication Provider above.

Value: Leave this field blank.
Enter this code:
```
{ 
  "fwd_sync_url":"forward-sync-url",
  "organization-id":"organization-id",
  "organization-fid":"organization-fid", 
  "user-id":"user-id" 
}
```
where:
- fwd_sync_url is https://preview-rls09.congacloud.com or https://prod-rls10.congacloud.com.
- organization-id is the Organization Id value you copied from Admin Console > Organization.
- organization-fid is the Organization Display Name, a hyphen, and organization-id. For example, acme-preview-organization-id.
- user-id is the id value you can copy from Admin Console > Users > Your User .
Create an admin entry named APTS_Additional_DualWriteObjects. leave Value blank and enter a comma-separated list of objects to sync to Advantage Platform in the Code field .

For example: Account, Opportunity, Apttus__Template__c

For more on Salesforce admin entries, see Enabling Discovery Access from the Contract Details Page.

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.

Setting Up Salesforce

Footer Section

Explore