Simple Sign is an easy out of the box component to allow community portal users to sign self service agreements. Add this component to any Salesforce Experience Cloud portal (customer, partner, employee, etc.), or embed the component into other Lightning components.
To gain access to the Simple Sign functionality, you must have version 21.0 or later of the Adobe Sign for Salesforce package installed.
New installations should be mindful to Generate Sample Agreement Templates when linking Salesforce to Adobe Sign
If the templates were not generated during install, or if you have upgraded from a previous version of the package to v19, you can generate the templates on the Adobe Sign Admin tab.
Verify that the Agreement Templates tab has the Test Community Agreement template:
Lightning must be enabled within your Salesforce organization for the portal to work.
To enable Lightning interface:
Chatter must be enabled in your SFDC organization. To do so:
To enable Digital Experiences:
You must configure two CSP (Content Security Policy) Trusted Sites to allow the base URLs for your Adobe Acrobat Sign account. To do so:
Get your Acrobat Sign account shard value as follows:
See how to identify the Adobe Acrobat Sign account environment.
In the new Site Definition page that opens, fill in the required fields as follows:
In the new Site Definition page that opens, fill in the required fields as follows:
To configure your user profiles to use the Adobe Acrobat Sign self-service portal, you must clone and edit one of the standard profiles. To do so:
You must create an Account, a Contact, and a User for the Community.
An account owner must be associated with a Role to enable portal users. To associate a role with your Salesforce user, go to Setup > Administration > Users > Users. Then, from the list of users, select Edit for a user and then in the page that opens, open the Role drop-down menu > select a role > select Save.
To create an Account:
A delightful graphics show runs while the Community is created. Once done, the Community page is displayed.
►The name of the Community is displayed at the top of the window, highlighted in yellow
►The site-specific string in the URL can be seen in the address bar, highlighted in teal
The My Workspaces page loads:
The Administration page opens for your community.
With Settings selected on the left rail:
Select Members from the left rail
The email address in the Profile Visibility section of the community must be set to Public:
The portal interface opens:
The My Settings page for the user opens:
The page refreshes to show the added component on the page layout, and exposes the management panel for the component in the top right corner.
The management panel in the upper-right of the window has only one configurable option:
Agreement Template - What is the template that governs the agreements listed in the component
Select the template, and then click the Publish button to make the portal available.
The Simple Sign component can be embedded in another lightning component.
Example code of the component:
<echosign_dev1:SimpleSign templateId="a0L190000019xUrEAI" />
When the component is embedded programmatically in another component, the following additional parameters can be specified:
Parameters follow these rules:
The component can also publish events to consumers. Here's an example of the event handler:
<aura:handler name="notifyError" event="echosign_dev1:ErrorEvent" action="{!c.onError}"/>
Available events are:
|
Agreement Sent |
name="notifyAgreementSent" event="echosign_dev1:AgreementSentEvent" action="{!c.onAgreementSent}" |
|
Agreement loaded from template |
name="notifyAgreementLoaded" event="echosign_dev1:AgreementLoadedEvent" action="{!c.onAgreementLoaded}" |
|
Signing page opened |
name="notifySigningLoaded" event="echosign_dev1:SigningLoadedEvent" action="{!c.onSigningLoaded}" |
|
Signed |
name="notifyRecipientCompleted" event="echosign_dev1:RecipientCompletedEvent" action="{!c.onRecipientCompleted}" |
|
No Signed |
name="notifyRecipientNotCompleted" event="echosign_dev1:RecipientNotCompletedEvent" action="{!c.onRecipientNotCompleted}" |
|
Error During any action |
name="notifyError" event="echosign_dev1:ErrorEvent" action="{!c.onError}" |
Templates in the Simple Sign environment must be configured to assign the recipient based on a lookup to a Master Object, and that object must be a Contact.
On the Template Details tab:
A file of some type must be attached to the template for Simple Sign to work. There is no chance for "the sender to attach the document" like an active send process.
Click Save when all of your documents are attached
Any file you upload is stored in Salesforce (in the Salesforce CRM & Files option)
If you have portal users that aren't licensed in Adobe Sign, you will need to circumvent the user licensing by exploiting the "Send on Behalf of" feature built in to the package. This allows a community user to generate an agreement using the licensing of another user.
This setup requires three configurations:
3. Click the Manage button
4. Click New (or Edit, if you have configured settings before)
5. Search for Allow Sending on Behalf of Others
To enable a User to support the Send on Behalf of functionality, two fields have to be added to the User record layout:
With the fields in place, enable the specific User:
With the User Edit page still open, copy the UserID from the URL in your browser bar.
The UserID is found in the URL of the page (highlighted in yellow below):
The above URL reads (with the ID in bold):
https://adobedocwinter18test-dev-ed.lightning.force.com/one/one.app?source=aloha#/setup/page?nodeId=ManageUsers&address=%2F0051I000000TA5N%3F
Be careful not to include the %2F at the beginning, and the %3 at the end
Click the Save button when you are done to save the configuration.
Click the Recipients tab and edit the Send On Behalf Of field
There are some limitations for the Simple Sign component that you need to be aware of:
1. The Template may not be configured with Only Sender Signs enabled
○ In this case, community user will see the error that the there is no signing URL for the current user
2. The Template may not have the Enable Preview and Position Fields option checked
○ In this case, the agreement remains in pre-send state, and no signing URL will be loaded
3. The Template may not have the Enable hosted signature option checked
4. Simple Sign does not support delegation
○ In this case, the other recipient will not be able to access the signing URL
5. Simple Sign does not support Replace Signer (which is a form of delegation)
○ In this case, the new signer will not be able to access the signing URL
6. To access the Notes and Attachments of any Salesforce object, admins must enable Lets customer users access notes and attachments in Communities Settings
Sign in to your account
