integration

How to integrate Adobe Sign into Salesforce CPQ in 3 easy steps

by Peter Averbukh

Business analysts and software consultants are often asked to integrate new applications with your customer’s existing applications These requests frequently result in heavy software customization and development or advising a better application that will do the same job.

Salesforce CPQ (formerly known as SteelBrick) is one of the leading CPQ tools and can integrate well with many applications. In this post, we will review how to Adobe Sign, an e-signatures solutions, with your Salesforce CPQ platform in 3 easy steps.

Note: This step-by-step guide assumes that you are doing a clean install and integration of the two applications.

1. First, you’ll have to install the two packages:

a. Install the AdobeSign package from AppExchange

b. Install the Salesforce CPQ package from the AppExchange

2. Go to Configure on Steelbrick CPQ package

a. GO to plugins tab

b. Put in this specific text into Electronic Signature Plugin field: SBES.EchoSignElectronicSignaturePluginpicture 1c. Sign into SteelBrick Community and go to https://steelbrick2.force.com/apex/installPremium – Here you will find the integration package you need for AdobeSign

 

3. Go to AdobeSign app, and eSign Services Admin tab.

a. Account Setup tabpicture 2

i. Update Salesforce User Name or Password to Enable Automatic Status Update

1. This will get us the API master login

ii. Authenticate Document eSign Services Account

1. Login will take you to Adobe Sign page and you will need to sign in.

2. Echosign administration document is in the community: EchoSign Administration: Adobe EchoSign for Salesforce Setup Wizard

iii. Once these steps are done – we can start sending documents

 

At this point we are done with our integration; that was easy right? Below is a 4th step, but it’s more of a post integration best practices note.

Post-integration best practices:

4. Each Template Bottom content record has embedded tags. The tags are visible if you highlight them on the Template Content record. They are white so that they don’t show if the document isn’t signed. Adobe uses all black, and these fields will show in Adobe PDF but not on the HTML screen.

picture 3

b. Adobe Sign tags: https://helpx.adobe.com/content/dam/help/en/sign/adobesign_text_tags_guide.pdf

c. Inspect the html code for each template content record and modify the tag names if changes are to be made.

d. Look at the last item on the Sections related list and you will get into the bottom template, where Adobe tags are for different signers. BE EXTREMELY CAREFUL AND ALWAYS CLONE! If you have a single error the entire document may not work. CLONE working templates and operate that way.

e. When sending the Adobe sign document, the send to is already populated. You will need to check “I also need to sign the document,” otherwise the contract will go out and only need 1 signature to execute. You need to check the checkbox otherwise one signature will finalize the doc.picture 4

f. Signature status is automatically updated when Adobe document is completely signed.

 

That’s it! With Adobe Sign integrated into SteelBrick you now have powerful e-signature within your CPQ system and you can start signing right away.

No Comments

Post A Comment