SpringCM

SpringCM is an online SaaS platform that helps generate, automate, manage, and store documents and contracts in a secure cloud. They help organizations simplify their business processes and help the document flow.

In order to integrate SpringCM with Relyance AI you will need a Client ID, Client Secret, Folder Path/s, and Data Center in the base URL of the API.

In SpringCM:

1. Login to your SpringCM account.
2. The Data Center in the base URL of the API can be obtained by looking at the subdomain of the API URL. The convention is: https://api[datacenter].springcm.com The API endpoints typically look something like this: a) https://api na11.springcm.com b) https://api na12 .springcm.com The examples above, the data centers for a and b would be na11 and na12 respectively. You can find your API BASE URLs by going to the SpringCM CLM page and navigating to Help>SpringCM Resources.
3. The Client ID (aka API Key) and Client Secret (aka API Secret) must obtained through SpringCM support. Directions are here: https://support.docusign.com/s/document-item?language=en_US&bundleId=dvk1585754716674&topicId=sly1576610025484.html&_LANG=enus
4. The documents to be processed are identified by the Folder Path/s.
   • If all documents in the inbox and folders should be processed, enter “ / ” for the folder path.
   • If only documents in a specific folder and their subfolders should be processed, enter the full folder path. For example, if there is a folder called Contracts with a subfolder DPA you wish to process, Contracts*/*DPA should be entered as the folder path.
   • Use semicolons(' ;') as a delimiter between paths (e.g. folder1/DPAs ; folder2/DPAs).

In the Relyance AI application:

1. Login to your Relyance account.
2. Navigate to the Settings Menu in the bottom left-hand side.
3. Select Integrations.
4. Click on the Contract Integration tab.
5. Find the SpringCM integration card and click it to open its connections.
6. Under Authentication Method, choose API Key Auth for the Legacy CLM.CM API.
7. Paste the Client ID, Client Secret, Folder Path/s, and Data Center in the base URL of the API into their respective fields.

The Authentication step asks for:

• Path of the folders containing contracts delimited by; (Eg: folder1; folder2): required.

9. Click Authenticate.
10. At this point, you should see the following result on the Contract Integrations page:

11. Congratulations, you are now connected to SpringCM.

Authentication methods and fields

Pick one of these under Authentication Method on the connection wizard's Authentication step. This table is generated from the integration catalog, so it always matches what the form actually asks for.

Manage this integration with Terraform

Connections for this integration can be managed as code with the Relyance Terraform provider. Non-secret fields go in auth.params; secret fields go in auth.secrets_wo, which is write-only — never stored in Terraform state. Rotate secrets by bumping auth.secrets_wo_version.

OAuth (browser authorization) — OAuth 2.0 Auth for the Docusign CLM API

The OAuth (browser authorization) — OAuth 2.0 Auth for the Docusign CLM API method uses a browser authorization flow, so the connection is created in the Relyance app. Manage it in Terraform afterwards by importing it (terraform import relyance_integration_connection.example springcm/<connection_id>) or reading it with the relyance_integration_connection data source.

OAuth (browser authorization) — OAuth 2.0 Auth for the Docusign CLM API (UAT)

The OAuth (browser authorization) — OAuth 2.0 Auth for the Docusign CLM API (UAT) method uses a browser authorization flow, so the connection is created in the Relyance app. Manage it in Terraform afterwards by importing it (terraform import relyance_integration_connection.example springcm/<connection_id>) or reading it with the relyance_integration_connection data source.