This document is aimed at Salesforce administrators and Salesforce integration partners and details the process of installing and configuring the Signicat Sign for Salesforce app.
Introduction to Signicat Sign for Salesforce
- Signicat Sign for Salesforce is an application for signing contracts and quotes as part of Salesforce CRM.
- Salesforce administrators can download the app from AppExchange, which is the app store for Salesforce.
- Signicat provides the Sign engine which the app communicates with.
- Signicat acts as a pure data processor and does not store user data.
- This document describes how to configure the app to interact with the Sign engine.
- This document is intended for Salesforce administrators or customers’ integration partners.
Install and configure Signicat Sign for Salesforce
- In AppExchange, search for «Signicat» and click on the listing for «Signicat Sign». Click ‘Get It Now’ to install.
- If available, it is recommended to install the app in a Salesforce test environment.
- After setup, you will be able to configure the app for Signicat’s pre-production environment.
- The default signing method will be InkSign + SMS.
- Signicat provides a set of signing methods for multiple countries. Contact Signicat for more information.
Choose «Install for All Users»
Grant access to the remote site settings included in the package:
Click «Done» on the final screen. You will receive an email on completion.
When clicking “Done”, you will be guided to ‘Installed Packages’, where you should see ‘Signicat Sign’.
Now you are ready to establish a connection to the Signicat Sign API.
Create email notification service
To enable Signicat to alert Salesforce when events happen, an email service for inbound email notifications is necessary.
Go to Setup – Custom Code (in Lightning) -> Email service. Type «Email Service» in «Quick find»
Set up email feedback channel
Set up a new Email Service (Apex) in Salesforce
- Apex Class: signicatsign.SignicatEmailNotificationService
- Accept Email From: noreply@Signicat.com
Add a new email address using the same address as above.
Create a new Email Service
Give it a name and find the SignicatEmailNotificationService apex-class.
Accept email from email@example.com.
Click «Save and New» and add firstname.lastname@example.org as an accepted recipient.
Signicat Sign for Salesforce app settings
Set up Signicat Sign for Salesforce app settings – open the app.
Edit Environment settings
Environment settings must correspond with the name you just added to the Named Credential for pre-production and production respectively
Open ‘Preprod Admin’ settings
- Input the name of the preprod named credentials in the field ‘Environment’.
- Save record.
Open ‘Prod Admin’ settings
- Input the name of the prod named credentials in the field ‘Environment’.
- Save record.
Adjust Admin settings – make sure they are as below.
Scroll down and make sure ‘Feedback channel’ is set to “email”
Go to ‘New signing request’ and test using the following steps:
- Find a user or contact to register a new task
- Click “Add Signer”
- Add a PDF document
- Click “Upload Document”
- Click “Send”
- Click “Finish”
If anything goes wrong or you receive errors, an error message should be displayed as a red “toast” on the screen.
New Signing request
Open App Launcher and find Signicat Sign.
Add a title for the request.
Add recipients that should sign the document (signers).
The signer will be added to the list on the right.
Select the PDF to be signed and click “Upload File”.
Verify that request is correctly set up with signers and documents. Click “Send”.
Click “Finish” to open the ‘Details’ page.
The signing parties will be able to sign when you distribute the link to them. Click on the task name to open the details.
On the task’s ‘Details’ page, compose an email and send it to an existing or new contact.
When all signers have completed their signing tasks, Salesforce is updated and the signed document saved as a file.
Click “Finish” and then click the “Perform signature” link on the task.
Sign with the selected method.
Input the SMS OTP you received and click continue. This step varies depending on the method, e.g.:
- BankID Se
- Email otp
See sign result in Salesforce
Salesforce will be alerted using the Email Service created in an earlier step, and the signed document will be saved in Salesforce. The request’s status will have been set to ‘Completed’.
Check the ‘Signature order’ tab in the app to verify this.
Change landing page
- Go to the ‘Settings’ tab in the Signicat Sign app.
- Find the ‘API Management’ section, and find the ‘Document Service admin’ record in the list.
- Set the ‘On Task Complete URL’ field to the desired URL. If left blank, you will see a blank page when completing a signing request.
Enabling the solution for production
- Contact Signicat sales for a contract.
- Discuss with Signicat which Sign methods are to be used.
Import the Signicat Sign certificate keystore
- You will have received an email from Signicat with a link to download a Java keystore file (.jks) containing the certificate for the service. This file should be stored in a secure place.
- You should be in possession of the encryption password for the keystore file (.jks). Signicat will have provided this by SMS. Import this keystore into Salesforce.
Go to ‘Setup’ -> ‘Certificate and Key Managment’.
Upload the file downloaded from Signicat Vault and type in the encryption password.
You should have a successful import with a keystore label. Remember and copy this label.
Open the ‘Settings’ tab and find the ‘Prod Admin’ settings under ‘Environments’.
Open and click «Edit» on this admin record.
Check the ‘Default settings’ checkbox and click «Save».
Test the previous signing request from pre-production again. Check that everything still works. You are now in production.
If you have your own service with Signicat
This will be the normal case for production.
Establish a connection to the API
Create Named Credentials for Preprod and Prod. You will need two named credentials for each environment.
- Same name for both, but the second needs the prefix ‘SDS’.
- Both are ‘Password Authentication’ with ‘Named Principal’ (User name and password are provided by Signicat – the endpoint is specific for each environment).
- The first should have all three checkboxes checked.
- The second should only have the ‘Generate Authorization Header’ checkbox checked.
Named Credentials overview
Named Credential, first version: all three checkboxes. Endpoint according to environment (preprod here)
Named Credential, second version: prefix ‘SDS’ – only first checkbox checked – else identical to first version
Repeat for production: new endpoint and password – add also the certificate imported from Signicat
Production second version