Simple Sign is an effortless component that allows community portal users to sign self-service agreements. You can easily add Simple Sign into any Salesforce Experience Cloud portal (such as customer, partner, or employee) or seamlessly embed it into other Lightning components.
The 'Simple Sign' feature is available for access from the following portals of a few different editions of the Salesforce community cloud:
Because community users are external users, their access to organizational data is restricted. By default, they are unable to access data generated by internal users.
To use Simple Sign for signing agreements on community portals, you must implement the following steps:
To access and use the Simple Sign functionality, you must verify the following:
To enable Chatter in your SFDC organization:
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:
Learn 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:
Navigate to Setup > Platform Tools > Feature Settings > Digital Experiences > All Sites.
Select New.
Select the Customer Service experience.
The Customer Service experience is required for the Self-Service components.
When the Customer Service page loads, select Get Started.
On the page that opens:
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).
Navigate to Setup > Platform Tools > Feature Settings > Digital Experiences > All Sites.
For your community, select Workspaces.
On the My Workspaces page that opens, select Administration.
On the Administration page for your community:
Open the Contact page for the user you are using to send on behalf of and then select Log in to Experience as User.
From the top-right corner of the portal interface that opens, select the user name and then select My Settings from the drop-down menu.
On the My Settings page that opens:
Navigate to Setup > Platform Tools > Feature Settings > Digital Experiences > All Sites.
For your community, select Workspaces.
In the My Workspaces section of the page, select Builder.
From the top-left of the page, select the Components icon, scroll to the bottom of the menu, and drag-n-drop the Adobe Simple Sign option on the page layout.
Drop the component where ever you want the Adobe Sign agreements to be exposed
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.
From the management panel, select Agreement Template and then select Publish to make the portal available.
After every change to the portal or settings, you must republish the portal.
You can embed the Simple Sign component in another lightning component using the following example code:
<echosign_dev1:SimpleSign templateId="a0L190000019xUrEAI" />
When embedding the component programmatically in another component, you can specify additional parameters:
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}"/>
The following table lists the available events:
|
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}" |
You must configure the templates in the Simple Sign environment to assign the recipient based on a lookup to a Master Object, and that object must be a Contact.
Under the Template Details tab:
Under the Recipients tab:
To use Simple Sign, you need to attach a file to the template. Unlike an active sending process, the sender cannot attach the document later. To attach a file to the template:
Go to the Attachment tab and then upload a document from your device.
Alternatively, choose the location of your document in the "Select to add documents" section.
Select the lookup field to view all available documents in that section.
Attach them to the template one by one by selecting them.
Once all your documents are attached, select Save.
Any file that you upload is stored in Salesforce under the Salesforce CRM & Files section.
If some of your portal users lack Adobe Sign licenses, you can enable the "Send on Behalf of" feature to work around licensing limitations. This lets a community user create an agreement using another user's license.
To set this up, follow these three steps:
Navigate to Setup > Platform Tools > Custom Code > Custom Settings.
It loads the Custom Settings page.
For Adobe Sign Settings listing, select Manage.
Select New (or Edit, if you have configured settings before).
It loads the Adobe Sign Settings page.
Locate and select the Allow Sending on Behalf of Others checkbox.
Select Save.
To enable a User to support the Send on Behalf of functionality, two fields have to be added to the User record layout:
Navigate to Setup > Platform Tools > Objects and Fields > Object Manager.
On the Object Manager page, select the User label.
From the left panel on the User page, select User Page Layouts and then select a user's layout.
Under User Layout, select the Fields option and then drag and drop the following two fields to the Additional Information (Header visible on edit only) section of the layout:
Once you've set up the fields, follow these steps to enable the specific user:
You'll find the UserID within the URL of the page (highlighted in yellow below):
From the URL (highlighted above), copy and keep the UserID (in bold) for the next step. Make sure to exclude the %2F at the start and the %3 at the end. Once done, select Save.
URL: https://adobedocwinter18test-dev-ed.lightning.force.com/one/one.app?source=aloha#/setup/page?nodeId=ManageUsers&address=%2F0051I000000TA5N%3F
Navigate to App Launcher > Adobe Acrobat Sign > Agreement Templates.
Select the Agreement Template name that you want to edit.
Under the Recipients tab, select the Send On Behalf Of field and then paste the Salesforce UserID into the field.
You can safely delete the placeholder ID without any concerns.
Select Save.
Our package's custom objects are initially set as "private" for external users by default. Community user permission sets provide access to custom objects and their fields, but not to records created by other users (both internal and external).
Within community portals, administrators have the following two options for setting up eSign flows:
In both cases, admins often use agreement templates to enable community users to initiate or participate in eSign flows. For this to work, community users need read-only access to agreement templates and related resources, such as merge and data mapping objects, which are typically created by internal users.
The type of community user license determines how access can be granted:
For community users to create agreements using agreement templates, they must be given "ViewAll" access to the Agreement templates and the associated Objects.
Data Mapping (echosign_dev1__SIGN_Data_Mapping__c)
If Acrobat Sign Document Builder templates are used with Agreement template as a file attachment, the objects below need to be granted access to community users:
Document Builder Template (adobesign__Document_Template__c)
Object Field Mapping (adobesign__Object_Field_Mapping__c)
If the Template isn't set up with Only Sender Signs enabled, Community users will encounter an error stating no signing URL is available for them.
If the Template lacks the Enable Preview and Position Fields option, the agreement remains in a pre-send state, and no signing URL will load.
If the Template doesn't have the Enable hosted signature option, Hosted signatures won't be supported.
Simple Sign doesn't support delegation. Other recipients won't access the signing URL.
Simple Sign doesn't support Replace Signer (a form of delegation). New signers won't access the signing URL.
To access Notes and Attachments of a Salesforce object, admins must enable "Let customer users access notes and attachments" in Communities Settings.
